
From ietf-secretariat-reply@ietf.org  Tue Oct  1 06:48:59 2013
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 124C621E82E5 for <ipv6@ietfa.amsl.com>; Tue,  1 Oct 2013 06:48:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.403
X-Spam-Level: 
X-Spam-Status: No, score=-101.403 tagged_above=-999 required=5 tests=[AWL=-1.022, BAYES_00=-2.599, NO_RELAYS=-0.001, TVD_SPACE_RATIO=2.219, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yhEkiVvEAsgH; Tue,  1 Oct 2013 06:48:58 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CDD4C11E8196; Tue,  1 Oct 2013 06:45:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
To: 6man-chairs@tools.ietf.org, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org
Subject: ID Tracker State Update Notice: <draft-ietf-6man-ext-transmit-04.txt>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.72.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131001134545.21382.91842.idtracker@ietfa.amsl.com>
Date: Tue, 01 Oct 2013 06:45:45 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Oct 2013 13:48:59 -0000

State changed to IESG Evaluation from Waiting for Writeup
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-6man-ext-transmi=
t/


From ietf-secretariat-reply@ietf.org  Tue Oct  1 11:09:05 2013
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0425521E822B for <ipv6@ietfa.amsl.com>; Tue,  1 Oct 2013 11:09:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.512
X-Spam-Level: 
X-Spam-Status: No, score=-102.512 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fflUTO7OAA3G; Tue,  1 Oct 2013 11:09:03 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4197E21E81EF; Tue,  1 Oct 2013 11:08:59 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
To: 6man-chairs@tools.ietf.org, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org
Subject: ID Tracker State Update Notice: <draft-ietf-6man-ext-transmit-04.txt>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.72.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131001180859.19504.24256.idtracker@ietfa.amsl.com>
Date: Tue, 01 Oct 2013 11:08:59 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Oct 2013 18:09:05 -0000

IANA review state changed to IANA OK - Actions Needed
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-6man-ext-transmi=
t/


From brian@innovationslab.net  Tue Oct  1 12:16:48 2013
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D88021E8225 for <ipv6@ietfa.amsl.com>; Tue,  1 Oct 2013 12:16:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.552
X-Spam-Level: 
X-Spam-Status: No, score=-102.552 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gWg1ViPykwmO for <ipv6@ietfa.amsl.com>; Tue,  1 Oct 2013 12:16:37 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 619CD21E80C5 for <ipv6@ietf.org>; Tue,  1 Oct 2013 12:16:32 -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 12557880F5; Tue,  1 Oct 2013 12:16:32 -0700 (PDT)
Received: from clemson.local (c-69-140-213-249.hsd1.md.comcast.net [69.140.213.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id AFC96130003; Tue,  1 Oct 2013 12:16:31 -0700 (PDT)
Message-ID: <524B1F88.9010800@innovationslab.net>
Date: Tue, 01 Oct 2013 15:16:24 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: draft-ietf-6man-oversized-header-chain.all@tools.ietf.org,  6man WG <ipv6@ietf.org>
Subject: AD Evaluation: draft-ietf-6man-oversized-header-chain
X-Enigmail-Version: 1.5.2
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="oo0o8cJqiXBspqOqhwfgFDQO0gO04XERR"
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Oct 2013 19:16:49 -0000

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

All,
     I have completed my AD evaluation for
draft-ietf-6man-oversized-header-chain.  I found the document to be
concise and well-written.  Thank you.

     I only have a few things I would like to see addressed prior to
starting an IETF Last Call on this document.

1. The 2nd paragraph of Section 4 (Motivation) could be made more clear.
 For example, you could indicate if the example first fragment does or
does not match the stateless firewall rule.  It is inferred that the
first fragment does not match the target TCP port since it was dropped,
but I like to err on the explicit side.  As an aside, wouldn't the
subsequent fragments be dropped as well or does the IP destination match
the forward rule?

2. I would like to get some clarification on the rule in section 5 that
says "A host that receives a first-fragment that does not satisfy the
above-stated requirement SHOULD discard that packet".  Can you provide
some justification for the SHOULD when you made it a MUST for a sending
node to ensure the upper-layer header is in the first fragment?  Are you
assuming some flexibility to support compatibility with older stacks?
If so, it would be good to have some guidance on what those stack
vendors should do.

3. Why is sending an ICMP error message a MAY?

4. It would be better to be explicit that a host sending an ICMP error
message is sending the same ICMP error specified for routers/middleboxes.=


5. I would suggest adding a reference to 2460 for the 1280 minimum MTU
value.

Regards,
Brian


--oo0o8cJqiXBspqOqhwfgFDQO0gO04XERR
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

iQEcBAEBCgAGBQJSSx+OAAoJEBOZRqCi7goqp5oH+wTLlmKnmbR2BphHC8qC+IUT
I+JnwTJ7iNEVKGRAABTi7ZV61FtGEubyaCpeSUX9ONePz+30GHuzdL5TwCHeSKka
D2CjLO01RD9IXGBTAjtSCZTlMaNwDVwQIQZ6FUq1UrmyPwkZsEtK/gFv5GVIZ1+m
VU0Mm+iPMuf9ThAfIsV8r4XUaltgiczl1LSqqhRbNzFxGQ+Pe5atJ23Z5hXQWUan
L2WqJTUL2CxbVVBH4/Y/In4/IsNyHQVEx+AAEwvMpEi6cTh4M6lCPct8EM2WputH
8x/r6jBhVjJoOh7SRKRvyDZIgT9EBnaTDE3PaH01yn8PuvH7GIX6Uw10ei9GLwc=
=56dP
-----END PGP SIGNATURE-----

--oo0o8cJqiXBspqOqhwfgFDQO0gO04XERR--

From ietf-secretariat-reply@ietf.org  Tue Oct  1 12:17:12 2013
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37BDF21E81BA for <ipv6@ietfa.amsl.com>; Tue,  1 Oct 2013 12:17:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.403
X-Spam-Level: 
X-Spam-Status: No, score=-101.403 tagged_above=-999 required=5 tests=[AWL=-1.022, BAYES_00=-2.599, NO_RELAYS=-0.001, TVD_SPACE_RATIO=2.219, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q-OAZ3OHb4Rl; Tue,  1 Oct 2013 12:17:11 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 52C4021E822B; Tue,  1 Oct 2013 12:17:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
To: 6man-chairs@tools.ietf.org, draft-ietf-6man-oversized-header-chain@tools.ietf.org, ipv6@ietf.org
Subject: ID Tracker State Update Notice: <draft-ietf-6man-oversized-header-chain-07.txt>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.72.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131001191706.21382.38973.idtracker@ietfa.amsl.com>
Date: Tue, 01 Oct 2013 12:17:06 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Oct 2013 19:17:12 -0000

State changed to AD Evaluation::Revised I-D Needed from AD Evaluation
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-6man-oversized-h=
eader-chain/


From internet-drafts@ietf.org  Tue Oct  1 14:04:23 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A38BE11E8252; Tue,  1 Oct 2013 14:04:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.001
X-Spam-Level: 
X-Spam-Status: No, score=-100.001 tagged_above=-999 required=5 tests=[NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id od5h5gNe+err; Tue,  1 Oct 2013 14:04:17 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A375611E8211; Tue,  1 Oct 2013 14:04:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-ug-04.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.72.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131001210402.3218.30575.idtracker@ietfa.amsl.com>
Date: Tue, 01 Oct 2013 14:04:02 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Oct 2013 21:04:23 -0000

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           : Significance of IPv6 Interface Identifiers
	Author(s)       : Brian Carpenter
                          Sheng Jiang
	Filename        : draft-ietf-6man-ug-04.txt
	Pages           : 11
	Date            : 2013-10-01

Abstract:
   The IPv6 addressing architecture includes a unicast interface
   identifier that is used in the creation of many IPv6 addresses.
   Interface identifiers are formed by a variety of methods.  This
   document clarifies that the bits in an interface identifier have no
   generic meaning and that the identifier should be treated as an
   opaque value.  In particular, RFC 4291 defines a method by which the
   Universal and Group bits of an IEEE link-layer address are mapped
   into an IPv6 unicast interface identifier.  This document clarifies
   that those two bits are significant only in interface identifiers
   that are derived from an IEEE link-layer address, and updates RFC
   4291 accordingly.


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

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

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-ug-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 brian.e.carpenter@gmail.com  Tue Oct  1 14:19:24 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C533A21F9F8F for <ipv6@ietfa.amsl.com>; Tue,  1 Oct 2013 14:19:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100
X-Spam-Level: 
X-Spam-Status: No, score=-100 tagged_above=-999 required=5 tests=[USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tzcTjTqxZFcK for <ipv6@ietfa.amsl.com>; Tue,  1 Oct 2013 14:19:18 -0700 (PDT)
Received: from mail-pd0-x236.google.com (mail-pd0-x236.google.com [IPv6:2607:f8b0:400e:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id E3B5121F9F9D for <ipv6@ietf.org>; Tue,  1 Oct 2013 14:19:05 -0700 (PDT)
Received: by mail-pd0-f182.google.com with SMTP id r10so7796807pdi.13 for <ipv6@ietf.org>; Tue, 01 Oct 2013 14:19:05 -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=b8PNI65U9mtUVLwrsK3pHaanLEKKoQ665mR1Bz12Adc=; b=SfR7pZndTbZeHRSpAWZHcgRRwbC4Q3gZLC876v4bImXkBzsLR7DMgtii16Qy/dkFUy wwTJk8ScFlBWI0QqZdd1FD7kW3sqc6xsekXboJsfUf6S9qcqzTaAidnA5ZeCga8pgErk r63A3V8tDkFj9J8QY2TeOCcuRqfDS86Bxv7nPwVLyC+q20PMxLv/JcrePcq5FV1oi/L0 MlEKSiaQ6Kbv2GLCUHLhlbJNKO4wXbx7Kf2y204AHz5vcj8Gxqgjd9slM5eq7EI7TI5r Njx/TZD39Op2zcU+XabH9svB5gkF/Isrs66a80lEs8iLgvUfOLWBOQcOvWtqCdjK22Tl Yt8g==
X-Received: by 10.68.101.3 with SMTP id fc3mr4135913pbb.107.1380662345710; Tue, 01 Oct 2013 14:19:05 -0700 (PDT)
Received: from [172.24.31.170] (wireless-nat-1.auckland.ac.nz. [130.216.30.112]) by mx.google.com with ESMTPSA id gh2sm8717861pbc.40.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 01 Oct 2013 14:19:04 -0700 (PDT)
Message-ID: <524B3C49.3060803@gmail.com>
Date: Wed, 02 Oct 2013 10:19:05 +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-ug-04.txt
References: <20131001210402.3218.30575.idtracker@ietfa.amsl.com>
In-Reply-To: <20131001210402.3218.30575.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Oct 2013 21:19:24 -0000

Dear 6man,

This version has two main changes:

1. Updated the discussion of IEEE 802.1 slightly, following review
by Eric Gray, the IETF's liaison to 802.1. The wording in 802.1 is
quite subtle, but quoting Eric, '"universal scope" means that a MAC
address MUST be globally unique within the scope of a (V)LAN.'
Therefore, it is not considered a violation of 802.1 for a MAC address
to be replicated on completely independent (V)LANs.

This surprised me, but only strengthens the underlying argument for
our draft.

2. Deleted a paragraph that the WG Chairs pointed out was a no-op.

I apologise that my co-author hasn't seen this version, since it is
a vacation week in China.

Regards
   Brian Carpenter

On 02/10/2013 10:04, 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           : Significance of IPv6 Interface Identifiers
> 	Author(s)       : Brian Carpenter
>                           Sheng Jiang
> 	Filename        : draft-ietf-6man-ug-04.txt
> 	Pages           : 11
> 	Date            : 2013-10-01
> 
> Abstract:
>    The IPv6 addressing architecture includes a unicast interface
>    identifier that is used in the creation of many IPv6 addresses.
>    Interface identifiers are formed by a variety of methods.  This
>    document clarifies that the bits in an interface identifier have no
>    generic meaning and that the identifier should be treated as an
>    opaque value.  In particular, RFC 4291 defines a method by which the
>    Universal and Group bits of an IEEE link-layer address are mapped
>    into an IPv6 unicast interface identifier.  This document clarifies
>    that those two bits are significant only in interface identifiers
>    that are derived from an IEEE link-layer address, and updates RFC
>    4291 accordingly.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6man-ug
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-6man-ug-04
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-ug-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
> 

From brian.e.carpenter@gmail.com  Tue Oct  1 14:48:33 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B2A121E80C7 for <ipv6@ietfa.amsl.com>; Tue,  1 Oct 2013 14:48:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.3
X-Spam-Level: 
X-Spam-Status: No, score=-101.3 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BUqx8DPE7Bpf for <ipv6@ietfa.amsl.com>; Tue,  1 Oct 2013 14:48:27 -0700 (PDT)
Received: from mail-pb0-x229.google.com (mail-pb0-x229.google.com [IPv6:2607:f8b0:400e:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 44DA021E81FA for <6man@ietf.org>; Tue,  1 Oct 2013 14:48:19 -0700 (PDT)
Received: by mail-pb0-f41.google.com with SMTP id rp2so7791682pbb.28 for <6man@ietf.org>; Tue, 01 Oct 2013 14:48:19 -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=mvFqETJQTDVCKD6aUrE0T1jtQvNGH4ZomlKZbP5VfLA=; b=wuEjxboUYuWqai8x16pb0KHU3HOQZMHlt7PIM4Yv7VhBYv75InwNVVTq0zj7l+Qei7 PYGqiaaTBAG4lO1ylzPIZXlrBK+FDsMnYyQrWrOQ9WLSbJbL26Z4q6KYRseDkoQhCVsj qgE841p3EgkkbD2mFaN3F03yuPDYOLQLz/DlKnfuLY7uumJMBxll9Z2gL1oUP9ogy/SM iZKX5KMZ0NY41/kMKHPC1B5oGHvXfXiK/u/HmMMB3y5NP2BXSl1uCRkz0gwLW9ofzSW0 GqyHvxyCOS36NGA9jlQm4wROM/dFI84G4TUTOx3+JyUkvNTZ/7kIXmIudbCqk5T7bVPP OKXA==
X-Received: by 10.68.143.104 with SMTP id sd8mr31976343pbb.10.1380664099077; Tue, 01 Oct 2013 14:48:19 -0700 (PDT)
Received: from [172.24.31.170] (wireless-nat-1.auckland.ac.nz. [130.216.30.112]) by mx.google.com with ESMTPSA id zq10sm10599531pab.6.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 01 Oct 2013 14:48:17 -0700 (PDT)
Message-ID: <524B4321.30309@gmail.com>
Date: Wed, 02 Oct 2013 10:48: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: Ray Hunter <v6ops@globis.net>
Subject: Re: Detailed review of Significance of IPv6 Interface Identifiers
References: <520B3529.80802@si6networks.com> <520BF653.8060603@gmail.com> <522309E1.7050806@globis.net> <5223EC0B.8080607@gmail.com> <5224284E.6020604@globis.net> <5224F28E.3040306@gmail.com> <5225D81F.6020009@globis.net>
In-Reply-To: <5225D81F.6020009@globis.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@ietf.org>, draft-ietf-6man-ug@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Oct 2013 21:48:33 -0000

I know that a couple of people wanted the extra details suggested by Ray
below. However, the explanation that I got from the 802.1 liaison
(see my previous message) seems to me to make the details unimportant.

Regards
   Brian

On 04/09/2013 00:37, Ray Hunter wrote:
>> Brian E Carpenter <mailto:brian.e.carpenter@gmail.com>
>> 2 September 2013 22:18
>> On 02/09/2013 17:55, Ray Hunter wrote:
>>>> Brian E Carpenter <mailto:brian.e.carpenter@gmail.com>
>>>> 2 September 2013 03:38
>>>> Ray,
>>>>
>>>>> So AFAICS the u/l restriction and uniqueness restriction is only
>>>>> relevant when EUI64 is used in the context of specific LAN hardware, but
>>>>> perhaps not all router interface hardware.
>>>> The phrasing in the draft looks completely compatible with that to me.
>>> I'm not sure what the text is trying to say though.
>> Ray, are you asking for a change in the text? Please be specific.
>>
>> <snip>
>>
>>> So any IETF standard that assumes a 1:1 relationship between IID and
>>> IEEE LAN hardware is heading for trouble.
>> Agreed - in what way does the draft imply anything else?
> I agree on the conclusion and the meaning. But the reasoning is not
> clear to me, nor particularly correct.
>> (The words in RFC 4291 that we are obsoleting do seem to imply
>> a 1:1 relationship, but that's what the draft fixes.)
> Agreed
>>     Brian
>>
> Original text:
> 
> /However, this has not so far proved to be the case.  Also, there is
>    evidence from the field that despite the IEEE standard [IEEE802], MAC
>    addresses with universal scope are sometime incorrectly assigned to
>    multiple MAC interfaces.  Firstly, there are recurrent reports of
>    manufacturers assigning the same MAC address to multiple devices.
>    Secondly, significant re-use of the same virtual MAC address is
>    reported in virtual machine environments.  Once transformed into IID
>    format (with "u" = 1) these identifiers would purport to be
>    universally unique but would in fact be ambiguous.  This has no known
>    harmful effect as long as the replicated MAC addresses and IIDs are
>    used on different layer 2 links.  If they are used on the same link,
>    of course there will be a problem, very likely interfering with link-
>    layer transmission.  If not, the problem will be detected by
>    duplicate address detection [RFC4862] [RFC6775], but such an error
>    can usually only be resolved by human intervention./
> 
> Proposed text:
> 
> 
> /
> However, the expected advantages or application of interface identifiers
> with universal scope have not materialised.
> 
> There is also evidence from the field that MAC addresses are not as
> unique as one might expect, where for example manufacturers have
> erroneously allocated the same burned in address to multiple devices.
> 
> Furthermore, IEEE standards and operational practices have advanced
> significantly since RFC4291 was published.
> 
> There are at least three use cases in wide-spread production where a
> router or other operating system interface at layer 3 may not enjoy
> direct access to LAN hardware on a 1:1 relationship so that it can
> access a "burned in address" from the MAC layer to create a unique IID
> per interface with universal scope (which seemed to be an underlying
> assumption when RFC4291 was written):
> 
> - use of software drivers to spoof an operating system into thinking it
> is talking to hardware, when in fact no LAN hardware is present e.g. LAN
> interfaces on virtual machines. Significant re-use of the same virtual
> MAC address has been reported in virtual machine environments. 
> 
> - use of an intermediate NIC teaming layer or Link Aggregation Group
> that takes a number of underlying layer 2 links and presents them as a
> single MAC interface to the client operating systems (IEEE 802.3ad draft
> v1, IEEE 802.1ax LACP, proprietary). IEEE 802.1ax states that the MAC
> address of the LAG MAY be an address of one of the underlying links in
> the Link Aggregation Group, but this is not limited in any way in
> implementations. LACP may also add and delete links from the Link
> Aggregation Group dynamically, and it would seem counterintuitive that
> the associated IID, and thus the IPv6 address, had to change every time
> this happened, because the whole purpose of the LAG is to shield the OS
> from such low level changes.
> 
> - "Router on a stick", or "firewall on a stick", where a specialist
> device such as an inter-VLAN router or firewall is connected to a layer
> 2 switch fabric via a single high speed interface, and multiple sub
> interfaces are defined at Layer 3, all of which share a common layer 2
> MAC address. These sub interfaces may be transported as a VLAN trunk
> (e.g. 802.1Q) into the layer 2 switch fabric, where the individual VLANs
> may then be presented on different hardware interfaces, such that the
> device may appear to source traffic on multiple physical interfaces
> using the same layer 2 address.
> 
> Once transformed into IID
>    format (with "u" = 1) these identifiers would purport to be
>    universally unique but would in fact be ambiguous.  This has no known
>    harmful effect as long as the replicated MAC addresses and IIDs are
>    used on different layer 2 links.  If they are used on the same link,
>    of course there will be a problem, very likely interfering with link-
>    layer transmission.  If not, the problem will be detected by
>    duplicate address detection [RFC4862] [RFC6775], but such an error
>    can usually only be resolved by human intervention.
> /
> 
> 
> 
> 
> Does that help?
>> ------------------------------------------------------------------------
> 
> 

From fernando@gont.com.ar  Tue Oct  1 22:57:32 2013
Return-Path: <fernando@gont.com.ar>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8521D11E8259 for <ipv6@ietfa.amsl.com>; Tue,  1 Oct 2013 22:57:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EIdfyfylhNpa for <ipv6@ietfa.amsl.com>; Tue,  1 Oct 2013 22:57:24 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 0056411E821A for <ipv6@ietf.org>; Tue,  1 Oct 2013 22:57:15 -0700 (PDT)
Received: from 17-153-16-190.fibertel.com.ar ([190.16.153.17] helo=[192.168.1.101]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fernando@gont.com.ar>) id 1VRFQs-0006f0-0U; Wed, 02 Oct 2013 07:57:10 +0200
Message-ID: <524BB5B2.5090904@gont.com.ar>
Date: Wed, 02 Oct 2013 02:57:06 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Brian Haberman <brian@innovationslab.net>,  draft-ietf-6man-oversized-header-chain.all@tools.ietf.org,  6man WG <ipv6@ietf.org>
Subject: Re: AD Evaluation: draft-ietf-6man-oversized-header-chain
References: <524B1F88.9010800@innovationslab.net>
In-Reply-To: <524B1F88.9010800@innovationslab.net>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Oct 2013 05:57:32 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi, Brian,

On 10/01/2013 04:16 PM, Brian Haberman wrote:
> 1. The 2nd paragraph of Section 4 (Motivation) could be made more 
> clear. For example, you could indicate if the example first 
> fragment does or does not match the stateless firewall rule.  It
> is inferred that the first fragment does not match the target TCP
> port since it was dropped, but I like to err on the explicit side.

mmm.. no. The first fragment presents this sample scenario:

A firewall is configured to block traffic to some specific TCP port.
IN the presence of normal fragmented traffic where a packet is
destined to such port, the first fragment will be dropped, and th
others will be passed (the policy is applied only to the first
fragment, where the upper layer information is present).

In a pathological scenario (third paragraph), it is impossible to
apply the policy to the received fragments (because even the first
fragment does not contain the upper layer information).


> As an aside, wouldn't the subsequent fragments be dropped as well 
> or does the IP destination match the forward rule?

In the case of a stateless firewall, you only enforce the policy on
first-fragments, under the assumption that if you properly filter
them, the rest of the fragments won't reassemble into a complete
datagram, and hence they will be eventually dropped.



> 2. I would like to get some clarification on the rule in section 5 
> that says "A host that receives a first-fragment that does not 
> satisfy the above-stated requirement SHOULD discard that packet". 
> Can you provide some justification for the SHOULD when you made it 
> a MUST for a sending node to ensure the upper-layer header is in 
> the first fragment?  Are you assuming some flexibility to support 
> compatibility with older stacks?

We meant to allw some flexibility. Although, me, I'd make it a "MUST
discard", too.


> If so, it would be good to have some guidance on what those stack 
> vendors should do.

I think the idea is "well, if you have some weird scenario, you may
want to allow this packets" -- that's why we recommend to have a knob
to change this behavior in specific scenarios. -- me, I don't expect
this to be employed.


> 3. Why is sending an ICMP error message a MAY?

When this text was suggested, I think the idea was that since these
messages shouldn't really exist in a real network, you might want to
just drop them. Although I can see that you could argue that this
could/shuld be a "SHOULD" rather than a "MAY".

Thoughts?


> 4. It would be better to be explicit that a host sending an ICMP 
> error message is sending the same ICMP error specified for 
> routers/middleboxes.

You mean in addition to:
   If a host or intermediate system discards a first-fragment because it
   does not satisfy the above-stated requirements, and sends an ICMPv6
   error message due to the discard, then the ICMPv6 error message MUST
   be Type 4 ("Parameter Problem") and MUST use Code TBD ("First-
   fragment has incomplete IPv6 Header Chain").

?


> 5. I would suggest adding a reference to 2460 for the 1280 minimum 
> MTU value.

Will do.

Thanks!

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



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJSS7WSAAoJEJbuqe/Qdv/xX1kIALG7TGSxToeaQRejvhGlGaqh
xH1/Jl4okjqihShVpPDac1HajcVA9tHrL8g886+l9sXW2LEH+IQLKocZv3E0uXgq
uDw6Lf/27X9NfUBDMkgLE1P/+VbK0o3q+Q7YWxnyNNYcy43Ya2zsj19CfskoRBQc
K0gpbhnHBBc5e2bBZP9sm0S1bvXKb6tQ3/Ti+2Ow76Bp/CjdvbEPLAzG6nczMjER
RfskaIyFeEWFeld1qjlSYdRJlf2LoFzfWql++UIX9VNcX13EFT4AwPnuruD3XAxj
AkOe9Po0fydNScQC09wWR8DExzG3sRk8ZFAu/l9cKdh3dVhc/nOLatjnPlf9wXI=
=erpf
-----END PGP SIGNATURE-----

From v6ops@globis.net  Wed Oct  2 00:33:05 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6317021E8254 for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 00:33:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ADDrbTPGy95N for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 00:32:59 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 35C4721E829E for <6man@ietf.org>; Wed,  2 Oct 2013 00:32:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 9433487003F; Wed,  2 Oct 2013 09:32: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 KPjf8rxKgtTx; Wed,  2 Oct 2013 09:32:18 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 72694870026; Wed,  2 Oct 2013 09:32:18 +0200 (CEST)
Message-ID: <524BCBFC.30001@globis.net>
Date: Wed, 02 Oct 2013 09:32:12 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Detailed review of Significance of IPv6 Interface Identifiers
References: <520B3529.80802@si6networks.com> <520BF653.8060603@gmail.com> <522309E1.7050806@globis.net> <5223EC0B.8080607@gmail.com> <5224284E.6020604@globis.net> <5224F28E.3040306@gmail.com> <5225D81F.6020009@globis.net> <524B4321.30309@gmail.com>
In-Reply-To: <524B4321.30309@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@ietf.org>, draft-ietf-6man-ug@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Oct 2013 07:33:05 -0000

> Brian E Carpenter <mailto:brian.e.carpenter@gmail.com>
> 1 October 2013 23:48
> I know that a couple of people wanted the extra details suggested by Ray
> below. However, the explanation that I got from the 802.1 liaison
> (see my previous message) seems to me to make the details unimportant.
>
> Regards
> Brian

I see your point.

The IEEE response makes it clear to me that the examples I provided are
all perfectly valid, and it also confirms a more generic conclusion that
it is incorrect to assume uniqueness when utilising a L2 LAN-scope
address beyond its intended scope (to form an IID).

-- 
Regards,
RayH


From brian@innovationslab.net  Wed Oct  2 07:38:38 2013
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9214521F8DA3 for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 07:38:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YDBgkEgQvIYC for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 07:38:25 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 837B421F84D9 for <ipv6@ietf.org>; Wed,  2 Oct 2013 07:38:25 -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 80840880E9; Wed,  2 Oct 2013 07:38:21 -0700 (PDT)
Received: from clemson.local (c-69-140-213-249.hsd1.md.comcast.net [69.140.213.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 0F2F6130003; Wed,  2 Oct 2013 07:38:20 -0700 (PDT)
Message-ID: <524C2FDA.5050704@innovationslab.net>
Date: Wed, 02 Oct 2013 10:38:18 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: draft-ietf-6man-oversized-header-chain.all@tools.ietf.org
Subject: Re: AD Evaluation: draft-ietf-6man-oversized-header-chain
References: <524B1F88.9010800@innovationslab.net> <524BB5B2.5090904@gont.com.ar>
In-Reply-To: <524BB5B2.5090904@gont.com.ar>
X-Enigmail-Version: 1.5.2
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="hTTGVO3isFRa7NA9fgkFuQkS8X8wC6SiL"
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Oct 2013 14:38:38 -0000

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



On 10/2/13 1:57 AM, Fernando Gont wrote:
> Hi, Brian,
>=20
> On 10/01/2013 04:16 PM, Brian Haberman wrote:
>> 1. The 2nd paragraph of Section 4 (Motivation) could be made more
>> clear. For example, you could indicate if the example first
>> fragment does or does not match the stateless firewall rule.  It
>> is inferred that the first fragment does not match the target TCP
>> port since it was dropped, but I like to err on the explicit side.
>=20
> mmm.. no. The first fragment presents this sample scenario:
>=20
> A firewall is configured to block traffic to some specific TCP port.
> IN the presence of normal fragmented traffic where a packet is
> destined to such port, the first fragment will be dropped, and th
> others will be passed (the policy is applied only to the first
> fragment, where the upper layer information is present).

The example in draft specifically says "that a stateless firewall
discards all traffic received from an interface unless it destined for a
particular TCP port on a particular IPv6 address".

So, the example focuses on an ALLOW rule.  What I am saying is that the
example needs more details added to clarify why each action is taken.

>=20
> In a pathological scenario (third paragraph), it is impossible to
> apply the policy to the received fragments (because even the first
> fragment does not contain the upper layer information).
>=20
>=20
>> As an aside, wouldn't the subsequent fragments be dropped as well
>> or does the IP destination match the forward rule?
>=20
> In the case of a stateless firewall, you only enforce the policy on
> first-fragments, under the assumption that if you properly filter
> them, the rest of the fragments won't reassemble into a complete
> datagram, and hence they will be eventually dropped.
>=20

But the subsequent fragments need to match *some* part of the rule to
justify forwarding them.  As noted above, there just needs to be some
clarifications in the example.


>=20
>=20
>> 2. I would like to get some clarification on the rule in section 5
>> that says "A host that receives a first-fragment that does not
>> satisfy the above-stated requirement SHOULD discard that packet".
>> Can you provide some justification for the SHOULD when you made it
>> a MUST for a sending node to ensure the upper-layer header is in
>> the first fragment?  Are you assuming some flexibility to support
>> compatibility with older stacks?
>=20
> We meant to allw some flexibility. Although, me, I'd make it a "MUST
> discard", too.
>=20

If the WG consensus was to allow some flexibility, it should be noted in
the text that the SHOULD is to allow for interoperability with legacy
stacks.

>=20
>> If so, it would be good to have some guidance on what those stack
>> vendors should do.
>=20
> I think the idea is "well, if you have some weird scenario, you may
> want to allow this packets" -- that's why we recommend to have a knob
> to change this behavior in specific scenarios. -- me, I don't expect
> this to be employed.
>=20

Why would you say this is a weird scenario?  Especially during an early
deployment of this feature, I would suspect there to be a myriad of
stacks trying to interact.

This doesn't need explicit guidance on how to allow the flexibility, but
the text should point out that the flexibility is there for backwards
compatibility.


>=20
>> 3. Why is sending an ICMP error message a MAY?
>=20
> When this text was suggested, I think the idea was that since these
> messages shouldn't really exist in a real network, you might want to
> just drop them. Although I can see that you could argue that this
> could/shuld be a "SHOULD" rather than a "MAY".
>=20
> Thoughts?
>=20

I much prefer this type of error being reported to minimize long
timeouts.  In the end, it is up to the WG to decide.

>=20
>> 4. It would be better to be explicit that a host sending an ICMP
>> error message is sending the same ICMP error specified for
>> routers/middleboxes.
>=20
> You mean in addition to:
>    If a host or intermediate system discards a first-fragment because i=
t
>    does not satisfy the above-stated requirements, and sends an ICMPv6
>    error message due to the discard, then the ICMPv6 error message MUST=

>    be Type 4 ("Parameter Problem") and MUST use Code TBD ("First-
>    fragment has incomplete IPv6 Header Chain").
>=20
> ?

I was more concerned with the nebulous text in the 2nd paragraph in
section 5.  Upon reconsideration, the 3rd paragraph is nebulous on the
message sent by middleboxes but the details are discussed paragraph 4.
So, this comment can be ignored.

Regards,
Brian


--hTTGVO3isFRa7NA9fgkFuQkS8X8wC6SiL
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

iQEcBAEBCgAGBQJSTC/bAAoJEBOZRqCi7goqkK0IAJDhWPVoNzL7f12+YRE/+OrF
jF4pYEVFOjyqMikm9AyTM5QBryohQRCvpAKd2ub68c8h2IfwEMHoy6SWAbeyhxPa
eQ6vMPgun4/pFA6hnq7Ps9ny3i+IsYwRD/0e1nL/HJEqPkAXIzCxNAXIsB4OOzKY
wHQnRvPYEVHi4VxHKE/eiwIr1q2UNmgEpFspf60MMoVm+Cev++o0HkQf0lROha79
s+srmyO4lUdx9qz0DcIjqGDKo/7RFU41V33ftlrTxCrTICd8+qhveQ9fkQV94hbA
eq5a2FoF/Wcrjg+i4u0U7Tys0Oa7oWUmxcMeyxhDGhFkArYm8a37aJVpuDWXN5s=
=wWAi
-----END PGP SIGNATURE-----

--hTTGVO3isFRa7NA9fgkFuQkS8X8wC6SiL--

From rbonica@juniper.net  Wed Oct  2 07:58:25 2013
Return-Path: <rbonica@juniper.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4873121F9A50 for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 07:58:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GmkhV72Gqg1u for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 07:57:59 -0700 (PDT)
Received: from db8outboundpool.messaging.microsoft.com (mail-db8lp0185.outbound.messaging.microsoft.com [213.199.154.185]) by ietfa.amsl.com (Postfix) with ESMTP id 196C621F9C00 for <ipv6@ietf.org>; Wed,  2 Oct 2013 07:55:41 -0700 (PDT)
Received: from mail101-db8-R.bigfish.com (10.174.8.228) by DB8EHSOBE033.bigfish.com (10.174.4.96) with Microsoft SMTP Server id 14.1.225.22; Wed, 2 Oct 2013 14:55:40 +0000
Received: from mail101-db8 (localhost [127.0.0.1])	by mail101-db8-R.bigfish.com (Postfix) with ESMTP id 2D2692400B7; Wed,  2 Oct 2013 14:55:40 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT001.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -22
X-BigFish: VPS-22(zz9371I542I1432I1447Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h1033IL1de097h8275dhz2fh2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1fe8h1ff5h9a9j1155h)
Received-SPF: pass (mail101-db8: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rbonica@juniper.net; helo=BL2PRD0510HT001.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(13464003)(189002)(377454003)(51704005)(199002)(51914003)(74876001)(74706001)(46102001)(80022001)(74366001)(54356001)(69226001)(53806001)(51856001)(66066001)(81342001)(76786001)(4396001)(77096001)(76796001)(83072001)(65816001)(63696002)(56816003)(81542001)(76576001)(49866001)(19580395003)(81816001)(47736001)(74316001)(31966008)(47446002)(74502001)(74662001)(79102001)(33646001)(80976001)(19580405001)(83322001)(81686001)(76482001)(56776001)(54316002)(50986001)(59766001)(77982001)(47976001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:CO1PR05MB443; H:CO1PR05MB442.namprd05.prod.outlook.com; CLIP:66.129.232.2; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Received: from mail101-db8 (localhost.localdomain [127.0.0.1]) by mail101-db8 (MessageSwitch) id 1380725737962331_8667; Wed,  2 Oct 2013 14:55:37 +0000 (UTC)
Received: from DB8EHSMHS012.bigfish.com (unknown [10.174.8.247])	by mail101-db8.bigfish.com (Postfix) with ESMTP id E447D880049; Wed,  2 Oct 2013 14:55:37 +0000 (UTC)
Received: from BL2PRD0510HT001.namprd05.prod.outlook.com (157.56.240.101) by DB8EHSMHS012.bigfish.com (10.174.4.22) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 2 Oct 2013 14:55:37 +0000
Received: from CO1PR05MB443.namprd05.prod.outlook.com (10.141.73.152) by BL2PRD0510HT001.namprd05.prod.outlook.com (10.255.100.36) with Microsoft SMTP Server (TLS) id 14.16.359.1; Wed, 2 Oct 2013 14:55:37 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB443.namprd05.prod.outlook.com (10.141.73.152) with Microsoft SMTP Server (TLS) id 15.0.775.9; Wed, 2 Oct 2013 14:55:33 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.55]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.125]) with mapi id 15.00.0775.005; Wed, 2 Oct 2013 14:55:33 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Brian Haberman <brian@innovationslab.net>, "draft-ietf-6man-oversized-header-chain.all@tools.ietf.org" <draft-ietf-6man-oversized-header-chain.all@tools.ietf.org>, 6man WG <ipv6@ietf.org>
Subject: RE: AD Evaluation: draft-ietf-6man-oversized-header-chain
Thread-Topic: AD Evaluation: draft-ietf-6man-oversized-header-chain
Thread-Index: AQHOvtrxcaZzep95Vkyn7lm8qGouf5nheUEA
Date: Wed, 2 Oct 2013 14:55:33 +0000
Message-ID: <935781b65bdb463ab975b9000a4593f3@CO1PR05MB442.namprd05.prod.outlook.com>
References: <524B1F88.9010800@innovationslab.net>
In-Reply-To: <524B1F88.9010800@innovationslab.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
x-forefront-prvs: 0987ACA2E2
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Oct 2013 14:58:26 -0000

Brian,

Thanks for the review. Please see responses, inline.....

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> Brian Haberman
> Sent: Tuesday, October 01, 2013 3:16 PM
> To: draft-ietf-6man-oversized-header-chain.all@tools.ietf.org; 6man WG
> Subject: AD Evaluation: draft-ietf-6man-oversized-header-chain
>=20
> All,
>      I have completed my AD evaluation for draft-ietf-6man-oversized-
> header-chain.  I found the document to be concise and well-written.
> Thank you.
>=20
>      I only have a few things I would like to see addressed prior to
> starting an IETF Last Call on this document.
>=20
> 1. The 2nd paragraph of Section 4 (Motivation) could be made more
> clear.
>  For example, you could indicate if the example first fragment does or
> does not match the stateless firewall rule.  It is inferred that the
> first fragment does not match the target TCP port since it was dropped,
> but I like to err on the explicit side. =20

Does the following edit address your concern?

OLD>=20
   For example, assume that a stateless firewall discards all traffic
   received from an interface unless it destined for a particular TCP
   port on a particular IPv6 address.  When this firewall is presented
   with a fragmented packet, and the entire header chain is contained
   within the first fragment, the firewall discards the first fragment
   and allows subsequent fragments to pass.  Because the first fragment
   was discarded, the packet cannot be reassembled at the destination.
   Insomuch as the packet cannot be reassembled, the forwarding policy
   is enforced.
<OLD

NEW>
   For example, assume that a stateless firewall discards all traffic
   received from an interface unless it destined for a particular TCP
   port on a particular IPv6 address.  When this firewall is presented
   with a fragmented packet that is destined for a different TCP port,=20
   and the entire header chain is contained within the first fragment,=20
   the firewall discards the first fragment and allows subsequent=20
   fragments to pass.  Because the first fragment was discarded,=20
   the packet cannot be reassembled at the destination. Insomuch as=20
   the packet cannot be reassembled, the forwarding policy is enforced.
<NEW

> As an aside, wouldn't the
> subsequent fragments be dropped as well or does the IP destination
> match the forward rule?

They won't be dropped by the firewall filter because the firewall filter ha=
s no way of knowing the TCP port to which they are directed. (Remember, we =
are talking about a stateless firewall.)

However, they will be dropped by the destination IP stack because they cann=
ot be reassembled.

>=20
> 2. I would like to get some clarification on the rule in section 5 that
> says "A host that receives a first-fragment that does not satisfy the
> above-stated requirement SHOULD discard that packet".  Can you provide
> some justification for the SHOULD when you made it a MUST for a sending
> node to ensure the upper-layer header is in the first fragment?  Are
> you assuming some flexibility to support compatibility with older
> stacks?
> If so, it would be good to have some guidance on what those stack
> vendors should do.

I agree. This should be a MUST.=20

>=20
> 3. Why is sending an ICMP error message a MAY?

On second thought, this should be a SHOULD. So, we have the following chang=
e, addressing your second and third points:

OLD>
   A host that receives a first-fragment that does not satisfy the
   above-stated requirement SHOULD discard that packet, and also MAY
   send an ICMPv6 error message to the source address of the offending
   packet (subject to the rules for ICMPv6 errors specified in
   [RFC4443]).
<OLD

NEW>
   A host that receives a first-fragment that does not satisfy the
   above-stated requirement MUST discard that packet, and also SHOULD
   send an ICMPv6 error message to the source address of the offending
   packet (subject to the rules for ICMPv6 errors specified in
   [RFC4443]).
<NEW


>=20
> 4. It would be better to be explicit that a host sending an ICMP error
> message is sending the same ICMP error specified for
> routers/middleboxes.

Does the following change address your comment:

OLD>
   If a host or intermediate system discards a first-fragment because it
   does not satisfy the above-stated requirements, and sends an ICMPv6
   error message due to the discard, then the ICMPv6 error message MUST
   be Type 4 ("Parameter Problem") and MUST use Code TBD ("First-
   fragment has incomplete IPv6 Header Chain").  The Pointer field
   contained by the ICMPv6 Parameter Problem message MUST be set to
   zero.
<OLD

NEW>
   If a host or intermediate system discards a first-fragment because it
   does not satisfy the above-stated requirements, and sends an ICMPv6
   error message due to the discard, then the ICMPv6 error message MUST
   be Type 4 ("Parameter Problem") and MUST use Code TBD ("First-
   fragment has incomplete IPv6 Header Chain").  The Pointer field
   contained by the ICMPv6 Parameter Problem message MUST be set to
   zero. Whether a host or intermediate system originates this ICMP message=
,
   its format is identical.
<NEW

>=20
> 5. I would suggest adding a reference to 2460 for the 1280 minimum MTU
> value.

Does the following change address your comment:

OLD>
   As a result of the above mentioned requirements, a packet's header
   chain length cannot exceed the Path MTU associated with its
   destination.  Hosts MAY discover the Path MTU, using procedures such
   as those defined in [RFC1981] and [RFC4821].  However, if a host does
   not discover the Path MTU, it MUST limit the header chain length to
   1280 bytes.  Limiting the header chain length to 1280 bytes ensures
   that the header chain length does not exceed the IPv6 minimum MTU.
<OLD

NEW>
As a result of the above mentioned requirements, a packet's header
   chain length cannot exceed the Path MTU associated with its
   destination.  Hosts MAY discover the Path MTU, using procedures such
   as those defined in [RFC1981] and [RFC4821].  However, if a host does
   not discover the Path MTU, it MUST limit the header chain length to
   1280 bytes.  Limiting the header chain length to 1280 bytes ensures
   that the header chain length does not exceed the IPv6 minimum MTU [RFC 2=
460].
<NEW
>=20
> Regards,
> Brian



From brian@innovationslab.net  Wed Oct  2 08:23:43 2013
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F89721F9385 for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 08:23:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rcw61izw9WIw for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 08:23:30 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 1C78421F9B6A for <ipv6@ietf.org>; Wed,  2 Oct 2013 08:23:05 -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 F2871880E9; Wed,  2 Oct 2013 08:23:04 -0700 (PDT)
Received: from clemson.local (c-69-140-213-249.hsd1.md.comcast.net [69.140.213.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 79EC3130003; Wed,  2 Oct 2013 08:23:04 -0700 (PDT)
Message-ID: <524C3A4E.8010901@innovationslab.net>
Date: Wed, 02 Oct 2013 11:22:54 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "draft-ietf-6man-oversized-header-chain.all@tools.ietf.org" <draft-ietf-6man-oversized-header-chain.all@tools.ietf.org>
Subject: Re: AD Evaluation: draft-ietf-6man-oversized-header-chain
References: <524B1F88.9010800@innovationslab.net> <935781b65bdb463ab975b9000a4593f3@CO1PR05MB442.namprd05.prod.outlook.com>
In-Reply-To: <935781b65bdb463ab975b9000a4593f3@CO1PR05MB442.namprd05.prod.outlook.com>
X-Enigmail-Version: 1.5.2
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="acobtdRbAjHX9oKJQhX7oIxCdmlOgM1qh"
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Oct 2013 15:23:43 -0000

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

Hi Ron,

On 10/2/13 10:55 AM, Ronald Bonica wrote:
> Brian,
>=20
> Thanks for the review. Please see responses, inline.....
>=20
>> -----Original Message-----
>> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf O=
f
>> Brian Haberman
>> Sent: Tuesday, October 01, 2013 3:16 PM
>> To: draft-ietf-6man-oversized-header-chain.all@tools.ietf.org; 6man WG=

>> Subject: AD Evaluation: draft-ietf-6man-oversized-header-chain
>>
>> All,
>>      I have completed my AD evaluation for draft-ietf-6man-oversized-
>> header-chain.  I found the document to be concise and well-written.
>> Thank you.
>>
>>      I only have a few things I would like to see addressed prior to
>> starting an IETF Last Call on this document.
>>
>> 1. The 2nd paragraph of Section 4 (Motivation) could be made more
>> clear.
>>  For example, you could indicate if the example first fragment does or=

>> does not match the stateless firewall rule.  It is inferred that the
>> first fragment does not match the target TCP port since it was dropped=
,
>> but I like to err on the explicit side. =20
>=20
> Does the following edit address your concern?
>=20
> OLD>=20
>    For example, assume that a stateless firewall discards all traffic
>    received from an interface unless it destined for a particular TCP
>    port on a particular IPv6 address.  When this firewall is presented
>    with a fragmented packet, and the entire header chain is contained
>    within the first fragment, the firewall discards the first fragment
>    and allows subsequent fragments to pass.  Because the first fragment=

>    was discarded, the packet cannot be reassembled at the destination.
>    Insomuch as the packet cannot be reassembled, the forwarding policy
>    is enforced.
> <OLD
>=20
> NEW>
>    For example, assume that a stateless firewall discards all traffic
>    received from an interface unless it destined for a particular TCP
>    port on a particular IPv6 address.  When this firewall is presented
>    with a fragmented packet that is destined for a different TCP port, =

>    and the entire header chain is contained within the first fragment, =

>    the firewall discards the first fragment and allows subsequent=20
>    fragments to pass.  Because the first fragment was discarded,=20
>    the packet cannot be reassembled at the destination. Insomuch as=20
>    the packet cannot be reassembled, the forwarding policy is enforced.=

> <NEW
>=20

This works for me.

>> As an aside, wouldn't the
>> subsequent fragments be dropped as well or does the IP destination
>> match the forward rule?
>=20
> They won't be dropped by the firewall filter because the firewall filte=
r has no way of knowing the TCP port to which they are directed. (Remembe=
r, we are talking about a stateless firewall.)
>=20

In order to pass part of the rule, the destination IPv6 address would
have to match the filter, correct?  No changes needed in the text, just
making sure I understand the nuances.

> However, they will be dropped by the destination IP stack because they =
cannot be reassembled.
>=20

Agreed.

>>
>> 2. I would like to get some clarification on the rule in section 5 tha=
t
>> says "A host that receives a first-fragment that does not satisfy the
>> above-stated requirement SHOULD discard that packet".  Can you provide=

>> some justification for the SHOULD when you made it a MUST for a sendin=
g
>> node to ensure the upper-layer header is in the first fragment?  Are
>> you assuming some flexibility to support compatibility with older
>> stacks?
>> If so, it would be good to have some guidance on what those stack
>> vendors should do.
>=20
> I agree. This should be a MUST.=20
>=20

If that is the WG consensus, that is fine.  The exchange with Fernando
indicated some interest in providing some flexibility to interact with
legacy stacks that don't support this spec yet.

I would suggest keeping it a SHOULD and adding a sentence or two that
about allowing flexibility for backwards compatibility.

>>
>> 3. Why is sending an ICMP error message a MAY?
>=20
> On second thought, this should be a SHOULD. So, we have the following c=
hange, addressing your second and third points:
>=20
> OLD>
>    A host that receives a first-fragment that does not satisfy the
>    above-stated requirement SHOULD discard that packet, and also MAY
>    send an ICMPv6 error message to the source address of the offending
>    packet (subject to the rules for ICMPv6 errors specified in
>    [RFC4443]).
> <OLD
>=20
> NEW>
>    A host that receives a first-fragment that does not satisfy the
>    above-stated requirement MUST discard that packet, and also SHOULD
>    send an ICMPv6 error message to the source address of the offending
>    packet (subject to the rules for ICMPv6 errors specified in
>    [RFC4443]).
> <NEW
>=20

Works for me.

>=20
>>
>> 4. It would be better to be explicit that a host sending an ICMP error=

>> message is sending the same ICMP error specified for
>> routers/middleboxes.
>=20
> Does the following change address your comment:
>=20
> OLD>
>    If a host or intermediate system discards a first-fragment because i=
t
>    does not satisfy the above-stated requirements, and sends an ICMPv6
>    error message due to the discard, then the ICMPv6 error message MUST=

>    be Type 4 ("Parameter Problem") and MUST use Code TBD ("First-
>    fragment has incomplete IPv6 Header Chain").  The Pointer field
>    contained by the ICMPv6 Parameter Problem message MUST be set to
>    zero.
> <OLD
>=20
> NEW>
>    If a host or intermediate system discards a first-fragment because i=
t
>    does not satisfy the above-stated requirements, and sends an ICMPv6
>    error message due to the discard, then the ICMPv6 error message MUST=

>    be Type 4 ("Parameter Problem") and MUST use Code TBD ("First-
>    fragment has incomplete IPv6 Header Chain").  The Pointer field
>    contained by the ICMPv6 Parameter Problem message MUST be set to
>    zero. Whether a host or intermediate system originates this ICMP mes=
sage,
>    its format is identical.
> <NEW
>=20

As I noted to Fernando, my confusion was with the text in the 2nd
paragraph.  No changes are needed, but I would not object to the above
change if the WG/authors thought it is useful.

>>
>> 5. I would suggest adding a reference to 2460 for the 1280 minimum MTU=

>> value.
>=20
> Does the following change address your comment:
>=20
> OLD>
>    As a result of the above mentioned requirements, a packet's header
>    chain length cannot exceed the Path MTU associated with its
>    destination.  Hosts MAY discover the Path MTU, using procedures such=

>    as those defined in [RFC1981] and [RFC4821].  However, if a host doe=
s
>    not discover the Path MTU, it MUST limit the header chain length to
>    1280 bytes.  Limiting the header chain length to 1280 bytes ensures
>    that the header chain length does not exceed the IPv6 minimum MTU.
> <OLD
>=20
> NEW>
> As a result of the above mentioned requirements, a packet's header
>    chain length cannot exceed the Path MTU associated with its
>    destination.  Hosts MAY discover the Path MTU, using procedures such=

>    as those defined in [RFC1981] and [RFC4821].  However, if a host doe=
s
>    not discover the Path MTU, it MUST limit the header chain length to
>    1280 bytes.  Limiting the header chain length to 1280 bytes ensures
>    that the header chain length does not exceed the IPv6 minimum MTU [R=
FC 2460].
> <NEW

That works.

Brian


--acobtdRbAjHX9oKJQhX7oIxCdmlOgM1qh
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

iQEcBAEBCgAGBQJSTDpUAAoJEBOZRqCi7goq4BEIAIecVwn094RWubOL3nC3BsRJ
8dC+cFMG7isuSBku+b5E+7Yi2IC3L7aKqZP9BAv93KiBDRZc+Olu94fp3b1fpwso
nkIrwE0S0RXeE61htx5DgLIznwS1uCGNxJ5PfF8F8B89W2Tj/wj/LtWISL02Kloe
t/7zjLFxAS8nV8goagUPoV2aTxkck1LrwjKM/74taxpsYA3iu4xgEwhaozYrm4yc
lUPanGEGvj3pHDGYUv0NN828r+DcLVMQiMmkBjBdEp6hYPWPzjFxw4/1LDaqLH+P
4r8/ZA4xWTjgS65gxk/4G6IB2xU01F6xXpFzYG7qtQuLor67nWTvDDyXRLW6jXs=
=/yU2
-----END PGP SIGNATURE-----

--acobtdRbAjHX9oKJQhX7oIxCdmlOgM1qh--

From rbonica@juniper.net  Wed Oct  2 09:24:28 2013
Return-Path: <rbonica@juniper.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CD0721F9D12 for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 09:24:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q5QYxU8DOUVD for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 09:24:16 -0700 (PDT)
Received: from db8outboundpool.messaging.microsoft.com (mail-db8lp0185.outbound.messaging.microsoft.com [213.199.154.185]) by ietfa.amsl.com (Postfix) with ESMTP id 4125D21F9D46 for <ipv6@ietf.org>; Wed,  2 Oct 2013 09:23:24 -0700 (PDT)
Received: from mail74-db8-R.bigfish.com (10.174.8.244) by DB8EHSOBE027.bigfish.com (10.174.4.90) with Microsoft SMTP Server id 14.1.225.22; Wed, 2 Oct 2013 16:23:23 +0000
Received: from mail74-db8 (localhost [127.0.0.1])	by mail74-db8-R.bigfish.com (Postfix) with ESMTP id 43ED8DC01E2; Wed,  2 Oct 2013 16:23:23 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT005.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -24
X-BigFish: VPS-24(zzbb2dI98dI9371I542I1432I1447Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h1033IL1de097h8275dhz2fh2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1fe8h1ff5h9a9j1155h)
Received-SPF: pass (mail74-db8: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rbonica@juniper.net; helo=BL2PRD0510HT005.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(13464003)(24454002)(189002)(377454003)(479174003)(51704005)(199002)(51914003)(74876001)(74706001)(46102001)(80022001)(74366001)(54356001)(69226001)(53806001)(51856001)(81342001)(66066001)(85306001)(76786001)(76796001)(4396001)(77096001)(65816001)(83072001)(63696002)(56816003)(81542001)(76576001)(49866001)(19580395003)(81816001)(47736001)(74316001)(31966008)(47446002)(74502001)(74662001)(79102001)(19580405001)(80976001)(33646001)(81686001)(83322001)(76482001)(56776001)(50986001)(54316002)(59766001)(47976001)(77982001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:CO1PR05MB443; H:CO1PR05MB442.namprd05.prod.outlook.com; CLIP:66.129.232.2; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Received: from mail74-db8 (localhost.localdomain [127.0.0.1]) by mail74-db8 (MessageSwitch) id 1380731001264988_26024; Wed,  2 Oct 2013 16:23:21 +0000 (UTC)
Received: from DB8EHSMHS020.bigfish.com (unknown [10.174.8.246])	by mail74-db8.bigfish.com (Postfix) with ESMTP id 32130A40041; Wed,  2 Oct 2013 16:23:21 +0000 (UTC)
Received: from BL2PRD0510HT005.namprd05.prod.outlook.com (157.56.240.101) by DB8EHSMHS020.bigfish.com (10.174.4.30) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 2 Oct 2013 16:23:21 +0000
Received: from CO1PR05MB443.namprd05.prod.outlook.com (10.141.73.152) by BL2PRD0510HT005.namprd05.prod.outlook.com (10.255.100.40) with Microsoft SMTP Server (TLS) id 14.16.359.1; Wed, 2 Oct 2013 16:23:19 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB443.namprd05.prod.outlook.com (10.141.73.152) with Microsoft SMTP Server (TLS) id 15.0.775.9; Wed, 2 Oct 2013 16:23:16 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.55]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.125]) with mapi id 15.00.0775.005; Wed, 2 Oct 2013 16:23:16 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Brian Haberman <brian@innovationslab.net>, "draft-ietf-6man-oversized-header-chain.all@tools.ietf.org" <draft-ietf-6man-oversized-header-chain.all@tools.ietf.org>
Subject: RE: AD Evaluation: draft-ietf-6man-oversized-header-chain
Thread-Topic: AD Evaluation: draft-ietf-6man-oversized-header-chain
Thread-Index: AQHOvtrxcaZzep95Vkyn7lm8qGouf5nheUEAgAAPkACAAAa5YA==
Date: Wed, 2 Oct 2013 16:23:15 +0000
Message-ID: <17cd3fd88dc54d72895e9443c4b1d426@CO1PR05MB442.namprd05.prod.outlook.com>
References: <524B1F88.9010800@innovationslab.net> <935781b65bdb463ab975b9000a4593f3@CO1PR05MB442.namprd05.prod.outlook.com> <524C3A4E.8010901@innovationslab.net>
In-Reply-To: <524C3A4E.8010901@innovationslab.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
x-forefront-prvs: 0987ACA2E2
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Oct 2013 16:24:28 -0000

Hi Brian,

So, merging in you last set of comments, the next draft version will includ=
e the changes listed below. Please tell me if these work for you.

                                    Ron

OLD>=20
   For example, assume that a stateless firewall discards all traffic
   received from an interface unless it destined for a particular TCP
   port on a particular IPv6 address.  When this firewall is presented
   with a fragmented packet, and the entire header chain is contained
   within the first fragment, the firewall discards the first fragment
   and allows subsequent fragments to pass.  Because the first fragment
   was discarded, the packet cannot be reassembled at the destination.
   Insomuch as the packet cannot be reassembled, the forwarding policy
   is enforced.
<OLD

NEW>
   For example, assume that a stateless firewall discards all traffic
   received from an interface unless it destined for a particular TCP
   port on a particular IPv6 address.  When this firewall is presented
   with a fragmented packet that is destined for a different TCP port,=20
   and the entire header chain is contained within the first fragment,=20
   the firewall discards the first fragment and allows subsequent=20
   fragments to pass.  Because the first fragment was discarded,=20
   the packet cannot be reassembled at the destination. Insomuch as=20
   the packet cannot be reassembled, the forwarding policy is enforced.
<NEW

OLD>
   A host that receives a first-fragment that does not satisfy the
   above-stated requirement SHOULD discard that packet, and also MAY
   send an ICMPv6 error message to the source address of the offending
   packet (subject to the rules for ICMPv6 errors specified in
   [RFC4443]).
<OLD

NEW>
   By default, a host that receives a first-fragment that does not satisfy =
the
   above-stated requirement MUST discard that packet. However, host impleme=
ntations
   may include a configuration option that allows them to accept such fragm=
ents.

   Furthermore, a host that receives a first-fragment that does not satisfy=
 the
   above-stated requirement SHOULD send an ICMPv6 error message to the sour=
ce=20
   address of the offending packet (subject to the rules for ICMPv6 errors =
specified in
   [RFC4443]).
<NEW

OLD>
   If a host or intermediate system discards a first-fragment because it
   does not satisfy the above-stated requirements, and sends an ICMPv6
   error message due to the discard, then the ICMPv6 error message MUST
   be Type 4 ("Parameter Problem") and MUST use Code TBD ("First-
   fragment has incomplete IPv6 Header Chain").  The Pointer field
   contained by the ICMPv6 Parameter Problem message MUST be set to
   zero.
<OLD

NEW>
   If a host or intermediate system discards a first-fragment because it
   does not satisfy the above-stated requirements, and sends an ICMPv6
   error message due to the discard, then the ICMPv6 error message MUST
   be Type 4 ("Parameter Problem") and MUST use Code TBD ("First-
   fragment has incomplete IPv6 Header Chain").  The Pointer field
   contained by the ICMPv6 Parameter Problem message MUST be set to
   zero. Whether a host or intermediate system originates this ICMP message=
,
   its format is identical.
<NEW

OLD>
   As a result of the above mentioned requirements, a packet's header
   chain length cannot exceed the Path MTU associated with its
   destination.  Hosts MAY discover the Path MTU, using procedures such
   as those defined in [RFC1981] and [RFC4821].  However, if a host does
   not discover the Path MTU, it MUST limit the header chain length to
   1280 bytes.  Limiting the header chain length to 1280 bytes ensures
   that the header chain length does not exceed the IPv6 minimum MTU.
<OLD

NEW>
   As a result of the above mentioned requirements, a packet's header
   chain length cannot exceed the Path MTU associated with its
   destination.  Hosts MAY discover the Path MTU, using procedures such
   as those defined in [RFC1981] and [RFC4821].  However, if a host does
   not discover the Path MTU, it MUST limit the header chain length to
   1280 bytes.  Limiting the header chain length to 1280 bytes ensures
   that the header chain length does not exceed the IPv6 minimum MTU [RFC 2=
460].
<NEW


> -----Original Message-----
> From: Brian Haberman [mailto:brian@innovationslab.net]
> Sent: Wednesday, October 02, 2013 11:23 AM
> To: draft-ietf-6man-oversized-header-chain.all@tools.ietf.org
> Cc: 6man WG
> Subject: Re: AD Evaluation: draft-ietf-6man-oversized-header-chain
>=20
> Hi Ron,
>=20
> On 10/2/13 10:55 AM, Ronald Bonica wrote:
> > Brian,
> >
> > Thanks for the review. Please see responses, inline.....
> >
> >> -----Original Message-----
> >> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf
> >> Of Brian Haberman
> >> Sent: Tuesday, October 01, 2013 3:16 PM
> >> To: draft-ietf-6man-oversized-header-chain.all@tools.ietf.org; 6man
> >> WG
> >> Subject: AD Evaluation: draft-ietf-6man-oversized-header-chain
> >>
> >> All,
> >>      I have completed my AD evaluation for draft-ietf-6man-
> oversized-
> >> header-chain.  I found the document to be concise and well-written.
> >> Thank you.
> >>
> >>      I only have a few things I would like to see addressed prior to
> >> starting an IETF Last Call on this document.
> >>
> >> 1. The 2nd paragraph of Section 4 (Motivation) could be made more
> >> clear.
> >>  For example, you could indicate if the example first fragment does
> >> or does not match the stateless firewall rule.  It is inferred that
> >> the first fragment does not match the target TCP port since it was
> >> dropped, but I like to err on the explicit side.
> >
> > Does the following edit address your concern?
> >
> > OLD>
> >    For example, assume that a stateless firewall discards all traffic
> >    received from an interface unless it destined for a particular TCP
> >    port on a particular IPv6 address.  When this firewall is
> presented
> >    with a fragmented packet, and the entire header chain is contained
> >    within the first fragment, the firewall discards the first
> fragment
> >    and allows subsequent fragments to pass.  Because the first
> fragment
> >    was discarded, the packet cannot be reassembled at the
> destination.
> >    Insomuch as the packet cannot be reassembled, the forwarding
> policy
> >    is enforced.
> > <OLD
> >
> > NEW>
> >    For example, assume that a stateless firewall discards all traffic
> >    received from an interface unless it destined for a particular TCP
> >    port on a particular IPv6 address.  When this firewall is
> presented
> >    with a fragmented packet that is destined for a different TCP
> port,
> >    and the entire header chain is contained within the first
> fragment,
> >    the firewall discards the first fragment and allows subsequent
> >    fragments to pass.  Because the first fragment was discarded,
> >    the packet cannot be reassembled at the destination. Insomuch as
> >    the packet cannot be reassembled, the forwarding policy is
> enforced.
> > <NEW
> >
>=20
> This works for me.
>=20
> >> As an aside, wouldn't the
> >> subsequent fragments be dropped as well or does the IP destination
> >> match the forward rule?
> >
> > They won't be dropped by the firewall filter because the firewall
> > filter has no way of knowing the TCP port to which they are directed.
> > (Remember, we are talking about a stateless firewall.)
> >
>=20
> In order to pass part of the rule, the destination IPv6 address would
> have to match the filter, correct?  No changes needed in the text, just
> making sure I understand the nuances.
>=20
> > However, they will be dropped by the destination IP stack because
> they cannot be reassembled.
> >
>=20
> Agreed.
>=20
> >>
> >> 2. I would like to get some clarification on the rule in section 5
> >> that says "A host that receives a first-fragment that does not
> >> satisfy the above-stated requirement SHOULD discard that packet".
> >> Can you provide some justification for the SHOULD when you made it a
> >> MUST for a sending node to ensure the upper-layer header is in the
> >> first fragment?  Are you assuming some flexibility to support
> >> compatibility with older stacks?
> >> If so, it would be good to have some guidance on what those stack
> >> vendors should do.
> >
> > I agree. This should be a MUST.
> >
>=20
> If that is the WG consensus, that is fine.  The exchange with Fernando
> indicated some interest in providing some flexibility to interact with
> legacy stacks that don't support this spec yet.
>=20
> I would suggest keeping it a SHOULD and adding a sentence or two that
> about allowing flexibility for backwards compatibility.
>=20
> >>
> >> 3. Why is sending an ICMP error message a MAY?
> >
> > On second thought, this should be a SHOULD. So, we have the following
> change, addressing your second and third points:
> >
> > OLD>
> >    A host that receives a first-fragment that does not satisfy the
> >    above-stated requirement SHOULD discard that packet, and also MAY
> >    send an ICMPv6 error message to the source address of the
> offending
> >    packet (subject to the rules for ICMPv6 errors specified in
> >    [RFC4443]).
> > <OLD
> >
> > NEW>
> >    A host that receives a first-fragment that does not satisfy the
> >    above-stated requirement MUST discard that packet, and also SHOULD
> >    send an ICMPv6 error message to the source address of the
> offending
> >    packet (subject to the rules for ICMPv6 errors specified in
> >    [RFC4443]).
> > <NEW
> >
>=20
> Works for me.
>=20
> >
> >>
> >> 4. It would be better to be explicit that a host sending an ICMP
> >> error message is sending the same ICMP error specified for
> >> routers/middleboxes.
> >
> > Does the following change address your comment:
> >
> > OLD>
> >    If a host or intermediate system discards a first-fragment because
> it
> >    does not satisfy the above-stated requirements, and sends an
> ICMPv6
> >    error message due to the discard, then the ICMPv6 error message
> MUST
> >    be Type 4 ("Parameter Problem") and MUST use Code TBD ("First-
> >    fragment has incomplete IPv6 Header Chain").  The Pointer field
> >    contained by the ICMPv6 Parameter Problem message MUST be set to
> >    zero.
> > <OLD
> >
> > NEW>
> >    If a host or intermediate system discards a first-fragment because
> it
> >    does not satisfy the above-stated requirements, and sends an
> ICMPv6
> >    error message due to the discard, then the ICMPv6 error message
> MUST
> >    be Type 4 ("Parameter Problem") and MUST use Code TBD ("First-
> >    fragment has incomplete IPv6 Header Chain").  The Pointer field
> >    contained by the ICMPv6 Parameter Problem message MUST be set to
> >    zero. Whether a host or intermediate system originates this ICMP
> message,
> >    its format is identical.
> > <NEW
> >
>=20
> As I noted to Fernando, my confusion was with the text in the 2nd
> paragraph.  No changes are needed, but I would not object to the above
> change if the WG/authors thought it is useful.
>=20
> >>
> >> 5. I would suggest adding a reference to 2460 for the 1280 minimum
> >> MTU value.
> >
> > Does the following change address your comment:
> >
> > OLD>
> >    As a result of the above mentioned requirements, a packet's header
> >    chain length cannot exceed the Path MTU associated with its
> >    destination.  Hosts MAY discover the Path MTU, using procedures
> such
> >    as those defined in [RFC1981] and [RFC4821].  However, if a host
> does
> >    not discover the Path MTU, it MUST limit the header chain length
> to
> >    1280 bytes.  Limiting the header chain length to 1280 bytes
> ensures
> >    that the header chain length does not exceed the IPv6 minimum MTU.
> > <OLD
> >
> > NEW>
> > As a result of the above mentioned requirements, a packet's header
> >    chain length cannot exceed the Path MTU associated with its
> >    destination.  Hosts MAY discover the Path MTU, using procedures
> such
> >    as those defined in [RFC1981] and [RFC4821].  However, if a host
> does
> >    not discover the Path MTU, it MUST limit the header chain length
> to
> >    1280 bytes.  Limiting the header chain length to 1280 bytes
> ensures
> >    that the header chain length does not exceed the IPv6 minimum MTU
> [RFC 2460].
> > <NEW
>=20
> That works.
>=20
> Brian



From brian@innovationslab.net  Wed Oct  2 09:37:48 2013
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BE7821F9C05 for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 09:37:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_47=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fTqckZPnwuqX for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 09:37:35 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id CA1DE21F9D74 for <ipv6@ietf.org>; Wed,  2 Oct 2013 09:35:55 -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 BC543880F0; Wed,  2 Oct 2013 09:35:55 -0700 (PDT)
Received: from clemson.local (c-69-140-213-249.hsd1.md.comcast.net [69.140.213.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id E3FC5130003; Wed,  2 Oct 2013 09:35:54 -0700 (PDT)
Message-ID: <524C4B60.8020408@innovationslab.net>
Date: Wed, 02 Oct 2013 12:35:44 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "draft-ietf-6man-oversized-header-chain.all@tools.ietf.org" <draft-ietf-6man-oversized-header-chain.all@tools.ietf.org>
Subject: Re: AD Evaluation: draft-ietf-6man-oversized-header-chain
References: <524B1F88.9010800@innovationslab.net> <935781b65bdb463ab975b9000a4593f3@CO1PR05MB442.namprd05.prod.outlook.com> <524C3A4E.8010901@innovationslab.net> <17cd3fd88dc54d72895e9443c4b1d426@CO1PR05MB442.namprd05.prod.outlook.com>
In-Reply-To: <17cd3fd88dc54d72895e9443c4b1d426@CO1PR05MB442.namprd05.prod.outlook.com>
X-Enigmail-Version: 1.5.2
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Gcmsq1AHJX32l3dtT85GF3C5xo2kCUmwj"
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Oct 2013 16:37:48 -0000

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

Hi Ron,

On 10/2/13 12:23 PM, Ronald Bonica wrote:
> Hi Brian,
>=20
> So, merging in you last set of comments, the next draft version will in=
clude the changes listed below. Please tell me if these work for you.
>=20
>                                     Ron
>=20
> OLD>=20
>    For example, assume that a stateless firewall discards all traffic
>    received from an interface unless it destined for a particular TCP
>    port on a particular IPv6 address.  When this firewall is presented
>    with a fragmented packet, and the entire header chain is contained
>    within the first fragment, the firewall discards the first fragment
>    and allows subsequent fragments to pass.  Because the first fragment=

>    was discarded, the packet cannot be reassembled at the destination.
>    Insomuch as the packet cannot be reassembled, the forwarding policy
>    is enforced.
> <OLD
>=20
> NEW>
>    For example, assume that a stateless firewall discards all traffic
>    received from an interface unless it destined for a particular TCP
>    port on a particular IPv6 address.  When this firewall is presented
>    with a fragmented packet that is destined for a different TCP port, =

>    and the entire header chain is contained within the first fragment, =

>    the firewall discards the first fragment and allows subsequent=20
>    fragments to pass.  Because the first fragment was discarded,=20
>    the packet cannot be reassembled at the destination. Insomuch as=20
>    the packet cannot be reassembled, the forwarding policy is enforced.=

> <NEW
>=20

Agreed.

> OLD>
>    A host that receives a first-fragment that does not satisfy the
>    above-stated requirement SHOULD discard that packet, and also MAY
>    send an ICMPv6 error message to the source address of the offending
>    packet (subject to the rules for ICMPv6 errors specified in
>    [RFC4443]).
> <OLD
>=20
> NEW>
>    By default, a host that receives a first-fragment that does not sati=
sfy the
>    above-stated requirement MUST discard that packet. However, host imp=
lementations
>    may include a configuration option that allows them to accept such f=
ragments.
>=20
>    Furthermore, a host that receives a first-fragment that does not sat=
isfy the
>    above-stated requirement SHOULD send an ICMPv6 error message to the =
source=20
>    address of the offending packet (subject to the rules for ICMPv6 err=
ors specified in
>    [RFC4443]).
> <NEW
>=20

The MUST+however confuses me.  To me, that just reduces to a SHOULD.
How about:

A host that receives a first-fragment that does not satisfy the
above-stated requirement SHOULD discard the packet (e.g., including a
configuration option that allows such fragments to be accepted for
backwards compatibility) and SHOULD send an ICMPv6 error message to the
source address of the offending packet (subject to the rules for ICMPv6
errors specified in [RFC4443]).

?

> OLD>
>    If a host or intermediate system discards a first-fragment because i=
t
>    does not satisfy the above-stated requirements, and sends an ICMPv6
>    error message due to the discard, then the ICMPv6 error message MUST=

>    be Type 4 ("Parameter Problem") and MUST use Code TBD ("First-
>    fragment has incomplete IPv6 Header Chain").  The Pointer field
>    contained by the ICMPv6 Parameter Problem message MUST be set to
>    zero.
> <OLD
>=20
> NEW>
>    If a host or intermediate system discards a first-fragment because i=
t
>    does not satisfy the above-stated requirements, and sends an ICMPv6
>    error message due to the discard, then the ICMPv6 error message MUST=

>    be Type 4 ("Parameter Problem") and MUST use Code TBD ("First-
>    fragment has incomplete IPv6 Header Chain").  The Pointer field
>    contained by the ICMPv6 Parameter Problem message MUST be set to
>    zero. Whether a host or intermediate system originates this ICMP mes=
sage,
>    its format is identical.
> <NEW
>=20

Agreed.

> OLD>
>    As a result of the above mentioned requirements, a packet's header
>    chain length cannot exceed the Path MTU associated with its
>    destination.  Hosts MAY discover the Path MTU, using procedures such=

>    as those defined in [RFC1981] and [RFC4821].  However, if a host doe=
s
>    not discover the Path MTU, it MUST limit the header chain length to
>    1280 bytes.  Limiting the header chain length to 1280 bytes ensures
>    that the header chain length does not exceed the IPv6 minimum MTU.
> <OLD
>=20
> NEW>
>    As a result of the above mentioned requirements, a packet's header
>    chain length cannot exceed the Path MTU associated with its
>    destination.  Hosts MAY discover the Path MTU, using procedures such=

>    as those defined in [RFC1981] and [RFC4821].  However, if a host doe=
s
>    not discover the Path MTU, it MUST limit the header chain length to
>    1280 bytes.  Limiting the header chain length to 1280 bytes ensures
>    that the header chain length does not exceed the IPv6 minimum MTU [R=
FC 2460].
> <NEW
>=20

Agreed.

Regards,
Brian


--Gcmsq1AHJX32l3dtT85GF3C5xo2kCUmwj
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

iQEcBAEBCgAGBQJSTEtnAAoJEBOZRqCi7goqEkMIALkmicR/jZzRawycTY4Jr1f9
kVcfjzQ104GfCAfBnxoJ8HQQbpyli6LrP9iD2tsuF0DbtbrN/uZqcUxtiPtMa2Nq
kYr1fXsbzLKAGhjXyCH+NOep5YQ1KPWjokEsZhS1BkHiIBeoCYdG33ZEeu0IZ1Yk
In6rYU82r4mpUjwj254wzfp71BZ2FOz++xuSwXICv3aFKMhdWr4nLBHZuuZGz5yM
RDoTDf1A6eRp0aiC3fgzgBYXuUZg7Wg6T+NC7Zke26G20Is1vXojUWvMUNlzAgSL
V8ID7/tfcBwQKErk0EGWS2X/J+OLaN1FwVTe1YnXcHtXCEB2XKwbZaGG3gtBO1Q=
=lsEx
-----END PGP SIGNATURE-----

--Gcmsq1AHJX32l3dtT85GF3C5xo2kCUmwj--

From rbonica@juniper.net  Wed Oct  2 10:18:32 2013
Return-Path: <rbonica@juniper.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A93BE21F9BAD for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 10:18:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IV6DULRs4Xez for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 10:18:17 -0700 (PDT)
Received: from db9outboundpool.messaging.microsoft.com (mail-db9lp0252.outbound.messaging.microsoft.com [213.199.154.252]) by ietfa.amsl.com (Postfix) with ESMTP id 887C321F9D38 for <ipv6@ietf.org>; Wed,  2 Oct 2013 10:14:35 -0700 (PDT)
Received: from mail173-db9-R.bigfish.com (10.174.16.237) by DB9EHSOBE037.bigfish.com (10.174.14.100) with Microsoft SMTP Server id 14.1.225.22; Wed, 2 Oct 2013 17:14:34 +0000
Received: from mail173-db9 (localhost [127.0.0.1])	by mail173-db9-R.bigfish.com (Postfix) with ESMTP id 811D280189; Wed,  2 Oct 2013 17:14:34 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT003.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -23
X-BigFish: VPS-23(zzbb2dI98dI9371I542I1432Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h1033IL1de097h8275dhz2fh2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1fe8h1ff5h9a9j1155h)
Received-SPF: pass (mail173-db9: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rbonica@juniper.net; helo=BL2PRD0510HT003.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(24454002)(189002)(199002)(51704005)(479174003)(377454003)(13464003)(80976001)(79102001)(54356001)(56776001)(54316002)(76786001)(76796001)(77096001)(63696002)(83322001)(81342001)(19580395003)(85306001)(19580405001)(81816001)(47976001)(4396001)(50986001)(53806001)(81686001)(69226001)(31966008)(74876001)(47446002)(51856001)(49866001)(74366001)(74662001)(66066001)(80022001)(65816001)(74316001)(47736001)(76576001)(76482001)(83072001)(81542001)(56816003)(74706001)(33646001)(74502001)(59766001)(77982001)(46102001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:CO1PR05MB441; H:CO1PR05MB442.namprd05.prod.outlook.com; CLIP:66.129.232.2; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Received: from mail173-db9 (localhost.localdomain [127.0.0.1]) by mail173-db9 (MessageSwitch) id 1380734072239082_31006; Wed,  2 Oct 2013 17:14:32 +0000 (UTC)
Received: from DB9EHSMHS018.bigfish.com (unknown [10.174.16.246])	by mail173-db9.bigfish.com (Postfix) with ESMTP id 2BC6346008C; Wed,  2 Oct 2013 17:14:32 +0000 (UTC)
Received: from BL2PRD0510HT003.namprd05.prod.outlook.com (157.56.240.101) by DB9EHSMHS018.bigfish.com (10.174.14.28) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 2 Oct 2013 17:14:30 +0000
Received: from CO1PR05MB441.namprd05.prod.outlook.com (10.141.73.147) by BL2PRD0510HT003.namprd05.prod.outlook.com (10.255.100.38) with Microsoft SMTP Server (TLS) id 14.16.359.1; Wed, 2 Oct 2013 17:14:29 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB441.namprd05.prod.outlook.com (10.141.73.147) with Microsoft SMTP Server (TLS) id 15.0.775.9; Wed, 2 Oct 2013 17:14:26 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.55]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.125]) with mapi id 15.00.0775.005; Wed, 2 Oct 2013 17:14:26 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Brian Haberman <brian@innovationslab.net>, "draft-ietf-6man-oversized-header-chain.all@tools.ietf.org" <draft-ietf-6man-oversized-header-chain.all@tools.ietf.org>
Subject: RE: AD Evaluation: draft-ietf-6man-oversized-header-chain
Thread-Topic: AD Evaluation: draft-ietf-6man-oversized-header-chain
Thread-Index: AQHOvtrxcaZzep95Vkyn7lm8qGouf5nheUEAgAAPkACAAAa5YIAADaEAgAAJ28A=
Date: Wed, 2 Oct 2013 17:14:25 +0000
Message-ID: <993aed26211c46069aee80d331864aa7@CO1PR05MB442.namprd05.prod.outlook.com>
References: <524B1F88.9010800@innovationslab.net> <935781b65bdb463ab975b9000a4593f3@CO1PR05MB442.namprd05.prod.outlook.com> <524C3A4E.8010901@innovationslab.net> <17cd3fd88dc54d72895e9443c4b1d426@CO1PR05MB442.namprd05.prod.outlook.com> <524C4B60.8020408@innovationslab.net>
In-Reply-To: <524C4B60.8020408@innovationslab.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
x-forefront-prvs: 0987ACA2E2
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Oct 2013 17:18:32 -0000

Brian,

This works for me. So, the complete list of changes follows. Do these work =
for you?

                                  Ron

CHANGES
=3D=3D=3D=3D=3D=3D=3D
OLD>=20
   For example, assume that a stateless firewall discards all traffic
   received from an interface unless it destined for a particular TCP
   port on a particular IPv6 address.  When this firewall is presented
   with a fragmented packet, and the entire header chain is contained
   within the first fragment, the firewall discards the first fragment
   and allows subsequent fragments to pass.  Because the first fragment
   was discarded, the packet cannot be reassembled at the destination.
   Insomuch as the packet cannot be reassembled, the forwarding policy
   is enforced.
<OLD

NEW>
   For example, assume that a stateless firewall discards all traffic
   received from an interface unless it destined for a particular TCP
   port on a particular IPv6 address.  When this firewall is presented
   with a fragmented packet that is destined for a different TCP port,=20
   and the entire header chain is contained within the first fragment,=20
   the firewall discards the first fragment and allows subsequent=20
   fragments to pass.  Because the first fragment was discarded,=20
   the packet cannot be reassembled at the destination. Insomuch as=20
   the packet cannot be reassembled, the forwarding policy is enforced.
<NEW

OLD>
   A host that receives a first-fragment that does not satisfy the
   above-stated requirement SHOULD discard that packet, and also MAY
   send an ICMPv6 error message to the source address of the offending
   packet (subject to the rules for ICMPv6 errors specified in
   [RFC4443]).
<OLD

NEW>
  A host that receives a first-fragment that does not satisfy the above-
  stated requirement SHOULD discard the packet (e.g., including a
  configuration option that allows such fragments to be accepted for
  backwards compatibility) and SHOULD send an ICMPv6 error message to the
  source address of the offending packet (subject to the rules for ICMPv6
  errors specified in [RFC4443]).
<NEW

OLD>
   If a host or intermediate system discards a first-fragment because it
   does not satisfy the above-stated requirements, and sends an ICMPv6
   error message due to the discard, then the ICMPv6 error message MUST
   be Type 4 ("Parameter Problem") and MUST use Code TBD ("First-
   fragment has incomplete IPv6 Header Chain").  The Pointer field
   contained by the ICMPv6 Parameter Problem message MUST be set to
   zero.
<OLD

NEW>
   If a host or intermediate system discards a first-fragment because it
   does not satisfy the above-stated requirements, and sends an ICMPv6
   error message due to the discard, then the ICMPv6 error message MUST
   be Type 4 ("Parameter Problem") and MUST use Code TBD ("First-
   fragment has incomplete IPv6 Header Chain").  The Pointer field
   contained by the ICMPv6 Parameter Problem message MUST be set to
   zero. Whether a host or intermediate system originates this ICMP message=
,
   its format is identical.
<NEW

OLD>
   As a result of the above mentioned requirements, a packet's header
   chain length cannot exceed the Path MTU associated with its
   destination.  Hosts MAY discover the Path MTU, using procedures such
   as those defined in [RFC1981] and [RFC4821].  However, if a host does
   not discover the Path MTU, it MUST limit the header chain length to
   1280 bytes.  Limiting the header chain length to 1280 bytes ensures
   that the header chain length does not exceed the IPv6 minimum MTU.
<OLD

NEW>
   As a result of the above mentioned requirements, a packet's header
   chain length cannot exceed the Path MTU associated with its
   destination.  Hosts MAY discover the Path MTU, using procedures such
   as those defined in [RFC1981] and [RFC4821].  However, if a host does
   not discover the Path MTU, it MUST limit the header chain length to
   1280 bytes.  Limiting the header chain length to 1280 bytes ensures
   that the header chain length does not exceed the IPv6 minimum MTU [RFC 2=
460].
<NEW

> -----Original Message-----
> From: Brian Haberman [mailto:brian@innovationslab.net]
> Sent: Wednesday, October 02, 2013 12:36 PM
> To: draft-ietf-6man-oversized-header-chain.all@tools.ietf.org
> Cc: 6man WG
> Subject: Re: AD Evaluation: draft-ietf-6man-oversized-header-chain
>=20
> Hi Ron,
>=20
> On 10/2/13 12:23 PM, Ronald Bonica wrote:
> > Hi Brian,
> >
> > So, merging in you last set of comments, the next draft version will
> include the changes listed below. Please tell me if these work for you.
> >
> >                                     Ron
> >



From brian@innovationslab.net  Wed Oct  2 10:20:58 2013
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2B5B21F9BD0 for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 10:20:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.539
X-Spam-Level: 
X-Spam-Status: No, score=-102.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5mDZ048DSK8q for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 10:20:33 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 36B3421F9D7E for <ipv6@ietf.org>; Wed,  2 Oct 2013 10:17:15 -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 1B079880F0; Wed,  2 Oct 2013 10:17:15 -0700 (PDT)
Received: from clemson.local (c-69-140-213-249.hsd1.md.comcast.net [69.140.213.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id B67D9130003; Wed,  2 Oct 2013 10:17:14 -0700 (PDT)
Message-ID: <524C5510.4030209@innovationslab.net>
Date: Wed, 02 Oct 2013 13:17:04 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "draft-ietf-6man-oversized-header-chain.all@tools.ietf.org" <draft-ietf-6man-oversized-header-chain.all@tools.ietf.org>
Subject: Re: AD Evaluation: draft-ietf-6man-oversized-header-chain
References: <524B1F88.9010800@innovationslab.net> <935781b65bdb463ab975b9000a4593f3@CO1PR05MB442.namprd05.prod.outlook.com> <524C3A4E.8010901@innovationslab.net> <17cd3fd88dc54d72895e9443c4b1d426@CO1PR05MB442.namprd05.prod.outlook.com> <524C4B60.8020408@innovationslab.net> <993aed26211c46069aee80d331864aa7@CO1PR05MB442.namprd05.prod.outlook.com>
In-Reply-To: <993aed26211c46069aee80d331864aa7@CO1PR05MB442.namprd05.prod.outlook.com>
X-Enigmail-Version: 1.5.2
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="wBwHsGSA72Qo9eRf2M8aBS9wUKdVGWOHd"
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Oct 2013 17:20:58 -0000

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

Ron,

On 10/2/13 1:14 PM, Ronald Bonica wrote:
> Brian,
>=20
> This works for me. So, the complete list of changes follows. Do these w=
ork for you?
>=20

Works for me!

Brian


--wBwHsGSA72Qo9eRf2M8aBS9wUKdVGWOHd
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

iQEcBAEBCgAGBQJSTFUWAAoJEBOZRqCi7goqIoYH/ipUpdl62XsvzbXNK0urg8O8
DbGjcMn1TB6uTdoFr8Rws+NcHaMLKfm37l5vvIrE38N5H5qc/e+x3SetQ4SNDt5H
owFBxXFydG4nufpgPpgPOkpDyWIfCZXrRlkS6zp/u17ztmqwrIXn2MoSHwUbaFkr
x3V+SEUw5yW2e0vwV4GgmdGvZCgwpkmOxBen/647+H2IiVjcMPTSRlpBvRPS0jUY
zPDGOWC6rTh1aHJ9gUsq2w94u4RqXYeOiDYzEHSfqSbEzDzP441vAd5hJYTf81ln
UvDwefLkqG0oUdeFjwp3iTUl2dggEGunS1zjwKK1MweHKVU5rSKA6sw9PgWU+wE=
=eQwn
-----END PGP SIGNATURE-----

--wBwHsGSA72Qo9eRf2M8aBS9wUKdVGWOHd--

From rbonica@juniper.net  Wed Oct  2 10:23:58 2013
Return-Path: <rbonica@juniper.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3B6021F92C2 for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 10:23:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.099
X-Spam-Level: 
X-Spam-Status: No, score=-103.099 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M2M1FqKoqnXg for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 10:23:46 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe002.messaging.microsoft.com [216.32.180.12]) by ietfa.amsl.com (Postfix) with ESMTP id B844D21F8415 for <ipv6@ietf.org>; Wed,  2 Oct 2013 10:19:47 -0700 (PDT)
Received: from mail71-va3-R.bigfish.com (10.7.14.251) by VA3EHSOBE009.bigfish.com (10.7.40.29) with Microsoft SMTP Server id 14.1.225.22; Wed, 2 Oct 2013 17:19:36 +0000
Received: from mail71-va3 (localhost [127.0.0.1])	by mail71-va3-R.bigfish.com (Postfix) with ESMTP id 99EE62000C2; Wed,  2 Oct 2013 17:19:36 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT001.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -23
X-BigFish: VPS-23(zzbb2dI98dI9371I542I1432Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h1033IL1de097h8275dhz2fh2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1fe8h1ff5h9a9j1155h)
Received-SPF: pass (mail71-va3: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rbonica@juniper.net; helo=BL2PRD0510HT001.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(13464003)(24454002)(189002)(377454003)(479174003)(51704005)(199002)(74876001)(74706001)(46102001)(80022001)(74366001)(54356001)(69226001)(53806001)(66066001)(51856001)(81342001)(85306001)(76786001)(76796001)(4396001)(77096001)(65816001)(83072001)(63696002)(56816003)(81542001)(76576001)(49866001)(19580395003)(81816001)(47736001)(74316001)(31966008)(47446002)(74502001)(74662001)(79102001)(19580405001)(80976001)(33646001)(81686001)(83322001)(50986001)(56776001)(76482001)(54316002)(59766001)(47976001)(77982001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:CO1PR05MB443; H:CO1PR05MB442.namprd05.prod.outlook.com; CLIP:66.129.232.2; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Received: from mail71-va3 (localhost.localdomain [127.0.0.1]) by mail71-va3 (MessageSwitch) id 1380734374453853_25047; Wed,  2 Oct 2013 17:19:34 +0000 (UTC)
Received: from VA3EHSMHS006.bigfish.com (unknown [10.7.14.225])	by mail71-va3.bigfish.com (Postfix) with ESMTP id 5F5E3320066; Wed,  2 Oct 2013 17:19:34 +0000 (UTC)
Received: from BL2PRD0510HT001.namprd05.prod.outlook.com (157.56.240.101) by VA3EHSMHS006.bigfish.com (10.7.99.16) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 2 Oct 2013 17:19:30 +0000
Received: from CO1PR05MB443.namprd05.prod.outlook.com (10.141.73.152) by BL2PRD0510HT001.namprd05.prod.outlook.com (10.255.100.36) with Microsoft SMTP Server (TLS) id 14.16.359.1; Wed, 2 Oct 2013 17:19:29 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB443.namprd05.prod.outlook.com (10.141.73.152) with Microsoft SMTP Server (TLS) id 15.0.775.9; Wed, 2 Oct 2013 17:19:26 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.55]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.125]) with mapi id 15.00.0775.005; Wed, 2 Oct 2013 17:19:26 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Brian Haberman <brian@innovationslab.net>, "draft-ietf-6man-oversized-header-chain.all@tools.ietf.org" <draft-ietf-6man-oversized-header-chain.all@tools.ietf.org>
Subject: RE: AD Evaluation: draft-ietf-6man-oversized-header-chain
Thread-Topic: AD Evaluation: draft-ietf-6man-oversized-header-chain
Thread-Index: AQHOvtrxcaZzep95Vkyn7lm8qGouf5nheUEAgAAPkACAAAa5YIAADaEAgAAJ28CAAAGxAIAAAI1A
Date: Wed, 2 Oct 2013 17:19:26 +0000
Message-ID: <978a2e5c9d6b46c28b29c070fa516e78@CO1PR05MB442.namprd05.prod.outlook.com>
References: <524B1F88.9010800@innovationslab.net> <935781b65bdb463ab975b9000a4593f3@CO1PR05MB442.namprd05.prod.outlook.com> <524C3A4E.8010901@innovationslab.net> <17cd3fd88dc54d72895e9443c4b1d426@CO1PR05MB442.namprd05.prod.outlook.com> <524C4B60.8020408@innovationslab.net> <993aed26211c46069aee80d331864aa7@CO1PR05MB442.namprd05.prod.outlook.com> <524C5510.4030209@innovationslab.net>
In-Reply-To: <524C5510.4030209@innovationslab.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
x-forefront-prvs: 0987ACA2E2
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Oct 2013 17:23:59 -0000

Brian,

Thanks much. We will produce an updated draft version ASAP.

                               Ron


> -----Original Message-----
> From: Brian Haberman [mailto:brian@innovationslab.net]
> Sent: Wednesday, October 02, 2013 1:17 PM
> To: draft-ietf-6man-oversized-header-chain.all@tools.ietf.org
> Cc: 6man WG
> Subject: Re: AD Evaluation: draft-ietf-6man-oversized-header-chain
>=20
> Ron,
>=20
> On 10/2/13 1:14 PM, Ronald Bonica wrote:
> > Brian,
> >
> > This works for me. So, the complete list of changes follows. Do these
> work for you?
> >
>=20
> Works for me!
>=20
> Brian



From internet-drafts@ietf.org  Wed Oct  2 11:23:26 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8835E21F95D0; Wed,  2 Oct 2013 11:23:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.432
X-Spam-Level: 
X-Spam-Status: No, score=-102.432 tagged_above=-999 required=5 tests=[AWL=0.168, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U9cL51hQO6ij; Wed,  2 Oct 2013 11:23:07 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D3DB21F9BD0; Wed,  2 Oct 2013 11:19:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-oversized-header-chain-08.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.72.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131002181901.20697.99284.idtracker@ietfa.amsl.com>
Date: Wed, 02 Oct 2013 11:19:01 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Oct 2013 18:23:26 -0000

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           : Implications of Oversized IPv6 Header Chains
	Author(s)       : Fernando Gont
                          Vishwas Manral
                          Ronald P. Bonica
	Filename        : draft-ietf-6man-oversized-header-chain-08.txt
	Pages           : 13
	Date            : 2013-10-02

Abstract:
   The IPv6 specification allows IPv6 header chains of an arbitrary
   size.  The specification also allows options which can in turn extend
   each of the headers.  In those scenarios in which the IPv6 header
   chain or options are unusually long and packets are fragmented, or
   scenarios in which the fragment size is very small, the first
   fragment of a packet may fail to include the entire IPv6 header
   chain.  This document discusses the interoperability and security
   problems of such traffic, and updates RFC 2460 such that the first
   fragment of a packet is required to contain the entire IPv6 header
   chain.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-oversized-header-chain-08

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-oversized-header-chain-08


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 internet-drafts@ietf.org  Wed Oct  2 11:23:35 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2B7521F8B4E; Wed,  2 Oct 2013 11:23:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.432
X-Spam-Level: 
X-Spam-Status: No, score=-102.432 tagged_above=-999 required=5 tests=[AWL=0.168, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h+ueeZ+zfdiQ; Wed,  2 Oct 2013 11:23:34 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E14D21F9D22; Wed,  2 Oct 2013 11:19:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-oversized-header-chain-08.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.72.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131002181902.20697.35297.idtracker@ietfa.amsl.com>
Date: Wed, 02 Oct 2013 11:19:02 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Oct 2013 18:23:35 -0000

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           : Implications of Oversized IPv6 Header Chains
	Author(s)       : Fernando Gont
                          Vishwas Manral
                          Ronald P. Bonica
	Filename        : draft-ietf-6man-oversized-header-chain-08.txt
	Pages           : 13
	Date            : 2013-10-02

Abstract:
   The IPv6 specification allows IPv6 header chains of an arbitrary
   size.  The specification also allows options which can in turn extend
   each of the headers.  In those scenarios in which the IPv6 header
   chain or options are unusually long and packets are fragmented, or
   scenarios in which the fragment size is very small, the first
   fragment of a packet may fail to include the entire IPv6 header
   chain.  This document discusses the interoperability and security
   problems of such traffic, and updates RFC 2460 such that the first
   fragment of a packet is required to contain the entire IPv6 header
   chain.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-oversized-header-chain-08

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-oversized-header-chain-08


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 internet-drafts@ietf.org  Wed Oct  2 11:23:35 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2686721F8BFD for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 11:23:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.435
X-Spam-Level: 
X-Spam-Status: No, score=-102.435 tagged_above=-999 required=5 tests=[AWL=0.165, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I5znDGTVI0PM; Wed,  2 Oct 2013 11:23:26 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5006821F9D35; Wed,  2 Oct 2013 11:19:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: 6man-chairs@tools.ietf.org, draft-ietf-6man-oversized-header-chain@tools.ietf.org, ipv6@ietf.org, brian@innovationslab.net
Subject: New Version Notification - draft-ietf-6man-oversized-header-chain-08.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.72.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131002181902.20697.59391.idtracker@ietfa.amsl.com>
Date: Wed, 02 Oct 2013 11:19:02 -0700
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Oct 2013 18:23:35 -0000

A new version (-08) has been submitted for draft-ietf-6man-oversized-header=
-chain:
http://www.ietf.org/internet-drafts/draft-ietf-6man-oversized-header-chain-=
08.txt


The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-oversized-header-chain/

Diff from previous version:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-oversized-header-chain-08

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.

IETF Secretariat.


From internet-drafts@ietf.org  Wed Oct  2 11:23:50 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A80121F8FB6 for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 11:23:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.439
X-Spam-Level: 
X-Spam-Status: No, score=-102.439 tagged_above=-999 required=5 tests=[AWL=0.161, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2aeRwVCGkpC6; Wed,  2 Oct 2013 11:23:42 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C703C21F9D68; Wed,  2 Oct 2013 11:19:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: 6man-chairs@tools.ietf.org, draft-ietf-6man-oversized-header-chain@tools.ietf.org, ipv6@ietf.org, brian@innovationslab.net
Subject: New Version Notification - draft-ietf-6man-oversized-header-chain-08.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.72.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131002181902.20697.7083.idtracker@ietfa.amsl.com>
Date: Wed, 02 Oct 2013 11:19:02 -0700
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Oct 2013 18:23:50 -0000

A new version (-08) has been submitted for draft-ietf-6man-oversized-header=
-chain:
http://www.ietf.org/internet-drafts/draft-ietf-6man-oversized-header-chain-=
08.txt

Sub state has been changed to AD Followup from Revised ID Needed


The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-oversized-header-chain/

Diff from previous version:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-oversized-header-chain-08

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.

IETF Secretariat.


From ietf-secretariat-reply@ietf.org  Wed Oct  2 11:35:26 2013
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FB1021F9A50 for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 11:35:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.008
X-Spam-Level: 
X-Spam-Status: No, score=-101.008 tagged_above=-999 required=5 tests=[AWL=-0.627, BAYES_00=-2.599, NO_RELAYS=-0.001, TVD_SPACE_RATIO=2.219, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3B4JU7MJ6frf; Wed,  2 Oct 2013 11:35:19 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 707DE21F9D95; Wed,  2 Oct 2013 11:30:28 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
To: 6man-chairs@tools.ietf.org, draft-ietf-6man-oversized-header-chain@tools.ietf.org, ipv6@ietf.org
Subject: ID Tracker State Update Notice: <draft-ietf-6man-oversized-header-chain-08.txt>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.72.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131002183028.20697.35943.idtracker@ietfa.amsl.com>
Date: Wed, 02 Oct 2013 11:30:28 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Oct 2013 18:35:26 -0000

State changed to Last Call Requested from AD Evaluation::AD Followup
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-6man-oversized-h=
eader-chain/


From iesg-secretary@ietf.org  Wed Oct  2 12:07:18 2013
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E734721F9E6B; Wed,  2 Oct 2013 12:07:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.216
X-Spam-Level: 
X-Spam-Status: No, score=-102.216 tagged_above=-999 required=5 tests=[AWL=0.384, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mUGcJDlsefQA; Wed,  2 Oct 2013 12:07:07 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id ECE3221F9EA2; Wed,  2 Oct 2013 11:55:22 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 4.72.p1
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: <20131002185522.20697.96027.idtracker@ietfa.amsl.com>
Date: Wed, 02 Oct 2013 11:55:22 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: ietf@ietf.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: Wed, 02 Oct 2013 19:07:19 -0000

The IESG has received a request from the IPv6 Maintenance WG (6man) to
consider the following document:
- 'Implications of Oversized IPv6 Header Chains'
  <draft-ietf-6man-oversized-header-chain-08.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2013-10-16. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   The IPv6 specification allows IPv6 header chains of an arbitrary
   size.  The specification also allows options which can in turn extend
   each of the headers.  In those scenarios in which the IPv6 header
   chain or options are unusually long and packets are fragmented, or
   scenarios in which the fragment size is very small, the first
   fragment of a packet may fail to include the entire IPv6 header
   chain.  This document discusses the interoperability and security
   problems of such traffic, and updates RFC 2460 such that the first
   fragment of a packet is required to contain the entire IPv6 header
   chain.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-6man-oversized-header-chain/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-6man-oversized-header-chain/ballot/


No IPR declarations have been submitted directly on this I-D.



From ietf-secretariat-reply@ietf.org  Wed Oct  2 12:07:36 2013
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F219721F9EAD for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 12:07:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.15
X-Spam-Level: 
X-Spam-Status: No, score=-102.15 tagged_above=-999 required=5 tests=[AWL=0.450, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YVX3ntDT8mKZ; Wed,  2 Oct 2013 12:07:29 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EFE3521F9EAF; Wed,  2 Oct 2013 11:55:26 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
To: 6man-chairs@tools.ietf.org, draft-ietf-6man-oversized-header-chain@tools.ietf.org, ipv6@ietf.org
Subject: ID Tracker State Update Notice: <draft-ietf-6man-oversized-header-chain-08.txt>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.72.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131002185526.20697.99685.idtracker@ietfa.amsl.com>
Date: Wed, 02 Oct 2013 11:55:26 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Oct 2013 19:07:36 -0000

Last call has been made for draft-ietf-6man-oversized-header-chain and stat=
e has been changed to In Last Call
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-6man-oversized-h=
eader-chain/


From brian.e.carpenter@gmail.com  Wed Oct  2 12:44:42 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99A6F21F9FAE for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 12:44:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QU1cbsrBA13c for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 12:44:36 -0700 (PDT)
Received: from mail-pb0-x236.google.com (mail-pb0-x236.google.com [IPv6:2607:f8b0:400e:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id CD04421F8616 for <6man@ietf.org>; Wed,  2 Oct 2013 12:34:03 -0700 (PDT)
Received: by mail-pb0-f54.google.com with SMTP id ro12so1353796pbb.27 for <6man@ietf.org>; Wed, 02 Oct 2013 12:34:03 -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=U3lOMqPPt/eicSM3mHJH2zDQ1ubAWDdWFkNMi865szg=; b=PPcc4mlKfuxzRsbCvWCBzjI0l0OB3LnIAiEy01n0+66dXosSmd+dtAyRPVa/KGNSPp c9WirFVdHKKr+X0m+ytK15vDsSj9IPkdlh2mWSuTPBqGkcjYLviSGMz7fZHxWCyfmaGY MG7KQuHNKgwnK1XNT2KGgXGFKftBMRxg5g6oAZr2t3ygVrq574ozh+vKJjaVnM5bxsKz QCCi4Rysn/0306pWmVq+/tuD4dlCJsGbZfaIbpZBSYdmZDtCYXchex6rxHfxC1+kfEyk YE0dT5U3JmslkwRGKSd+Oy4purY4AnOUM1xN4bYbeMD/cuGjc3vqhMiQmR4RrqKiCH9z 0PaQ==
X-Received: by 10.66.150.69 with SMTP id ug5mr5016576pab.55.1380742443538; Wed, 02 Oct 2013 12:34:03 -0700 (PDT)
Received: from [192.168.178.20] (96.193.69.111.dynamic.snap.net.nz. [111.69.193.96]) by mx.google.com with ESMTPSA id xv2sm3556040pbb.39.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 02 Oct 2013 12:34:02 -0700 (PDT)
Message-ID: <524C752D.8090403@gmail.com>
Date: Thu, 03 Oct 2013 08:34:05 +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: Ray Hunter <v6ops@globis.net>
Subject: Re: Detailed review of Significance of IPv6 Interface Identifiers
References: <520B3529.80802@si6networks.com> <520BF653.8060603@gmail.com> <522309E1.7050806@globis.net> <5223EC0B.8080607@gmail.com> <5224284E.6020604@globis.net> <5224F28E.3040306@gmail.com> <5225D81F.6020009@globis.net> <524B4321.30309@gmail.com> <524BCBFC.30001@globis.net>
In-Reply-To: <524BCBFC.30001@globis.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@ietf.org>, draft-ietf-6man-ug@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Oct 2013 19:44:42 -0000

On 02/10/2013 20:32, Ray Hunter wrote:
>> Brian E Carpenter <mailto:brian.e.carpenter@gmail.com>
>> 1 October 2013 23:48
>> I know that a couple of people wanted the extra details suggested by Ray
>> below. However, the explanation that I got from the 802.1 liaison
>> (see my previous message) seems to me to make the details unimportant.
>>
>> Regards
>> Brian
> 
> I see your point.
> 
> The IEEE response makes it clear to me that the examples I provided are
> all perfectly valid, and it also confirms a more generic conclusion that
> it is incorrect to assume uniqueness when utilising a L2 LAN-scope
> address beyond its intended scope (to form an IID).

Agreed. I have to say this was a surprise to me. I can't speak for anyone
else, including the designers of the Modified EUI format, but I was under
the delusion that the intent of 802.1 was u=universal=unique. Quoting
the DIX Ethernet standard dated November 1982, "A station's physical address
should be distinct from the physical address of any other station on any
Ethernet." I guess it was a mistake to go by that ;-)

    Brian

From tom.taylor.stds@gmail.com  Wed Oct  2 16:51:06 2013
Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 047E221F9946 for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 16:51:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N4G0rxJmc61O for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 16:50:57 -0700 (PDT)
Received: from mail-qa0-x22e.google.com (mail-qa0-x22e.google.com [IPv6:2607:f8b0:400d:c00::22e]) by ietfa.amsl.com (Postfix) with ESMTP id B976F21F84D0 for <ipv6@ietf.org>; Wed,  2 Oct 2013 16:50:48 -0700 (PDT)
Received: by mail-qa0-f46.google.com with SMTP id j7so4909942qaq.12 for <ipv6@ietf.org>; Wed, 02 Oct 2013 16:50:47 -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=nolvoivlwOXndEi14qfEQ1en6lw1rsRyj45kVR5anyc=; b=DvzMGYk+JP1zctMNlxnGkgUQLi/F/HCIXM/6dCxFBlHClnlJOxDgpMMa42Iw/CKurB izk2bYopdlh4jKtDMqpISPKPYmJQvYQ2JFhKA3Pi2ex6LdTpCHOmSepGoeItyWLb5ll5 85vUUSHckPhX/2hF3YBuK6pvA6Do5id8eat6vxXHJ8qDh3j6N89rGTKgfA32l111zOMa YDBmdmRgE/i2CZ7XrLbTC3g8RSxkFRiOYFsMiL85v6+J7yW16pi2wLmKG9Ev5MgvF9CL yg0PpH9dI7+i1xRTz4WwF3ZrbayDeXHAlbzwihDnF2VeAEOBE1uICa0MTA3lxnAJQwMB Undw==
X-Received: by 10.224.13.207 with SMTP id d15mr4760489qaa.110.1380757846946; Wed, 02 Oct 2013 16:50:46 -0700 (PDT)
Received: from [192.168.1.65] (dsl-173-206-79-23.tor.primus.ca. [173.206.79.23]) by mx.google.com with ESMTPSA id x8sm10793588qam.2.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 02 Oct 2013 16:50:46 -0700 (PDT)
Message-ID: <524CB151.3090103@gmail.com>
Date: Wed, 02 Oct 2013 19:50:41 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Ronald Bonica <rbonica@juniper.net>
Subject: Re: AD Evaluation: draft-ietf-6man-oversized-header-chain
References: <524B1F88.9010800@innovationslab.net> <935781b65bdb463ab975b9000a4593f3@CO1PR05MB442.namprd05.prod.outlook.com> <524C3A4E.8010901@innovationslab.net> <17cd3fd88dc54d72895e9443c4b1d426@CO1PR05MB442.namprd05.prod.outlook.com> <524C4B60.8020408@innovationslab.net> <993aed26211c46069aee80d331864aa7@CO1PR05MB442.namprd05.prod.outlook.com>
In-Reply-To: <993aed26211c46069aee80d331864aa7@CO1PR05MB442.namprd05.prod.outlook.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Brian Haberman <brian@innovationslab.net>, 6man WG <ipv6@ietf.org>, "draft-ietf-6man-oversized-header-chain.all@tools.ietf.org" <draft-ietf-6man-oversized-header-chain.all@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Oct 2013 23:51:06 -0000

Just a trivial change: "including" -> "subject to"

On 02/10/2013 1:14 PM, Ronald Bonica wrote:
> Brian,
>
> This works for me. So, the complete list of changes follows. Do these work for you?
>
>                                    Ron
>
> CHANGES
> =======
...
>
> OLD>
>     A host that receives a first-fragment that does not satisfy the
>     above-stated requirement SHOULD discard that packet, and also MAY
>     send an ICMPv6 error message to the source address of the offending
>     packet (subject to the rules for ICMPv6 errors specified in
>     [RFC4443]).
> <OLD
>
> NEW>
>    A host that receives a first-fragment that does not satisfy the above-
>    stated requirement SHOULD discard the packet (e.g., including a
                                                          ^^^^^^^^^
>    configuration option that allows such fragments to be accepted for
>    backwards compatibility) and SHOULD send an ICMPv6 error message to the
>    source address of the offending packet (subject to the rules for ICMPv6
>    errors specified in [RFC4443]).
> <NEW
>
...

From randy@psg.com  Wed Oct  2 20:29:29 2013
Return-Path: <randy@psg.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7E8621F9FB4 for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 20:29:29 -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=[AWL=1.300, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Pi8Ylr6Id+y for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 20:29:23 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 2157D21F9DB8 for <ipv6@ietf.org>; Wed,  2 Oct 2013 20:29:21 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1VRZbL-0000py-8d for ipv6@ietf.org; Thu, 03 Oct 2013 03:29:19 +0000
Date: Thu, 03 Oct 2013 12:29:18 +0900
Message-ID: <m24n8zuj5d.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IPv6 Deployment Prevention <ipv6@ietf.org>
Subject: a frag measurement of interest
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
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 03 Oct 2013 03:29:30 -0000

https://labs.ripe.net/Members/emileaben/ripe-atlas-packet-size-matters

From swmike@swm.pp.se  Wed Oct  2 23:30:01 2013
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAB5C21F9E9D for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 23:30:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VOtlLhRDVeu9 for <ipv6@ietfa.amsl.com>; Wed,  2 Oct 2013 23:29:55 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id 141D621F8F61 for <ipv6@ietf.org>; Wed,  2 Oct 2013 23:29:53 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 2647B9C; Thu,  3 Oct 2013 08:29:50 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 1DEC39A; Thu,  3 Oct 2013 08:29:50 +0200 (CEST)
Date: Thu, 3 Oct 2013 08:29:50 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Randy Bush <randy@psg.com>
Subject: Re: a frag measurement of interest
In-Reply-To: <m24n8zuj5d.wl%randy@psg.com>
Message-ID: <alpine.DEB.2.02.1310030828370.20065@uplift.swm.pp.se>
References: <m24n8zuj5d.wl%randy@psg.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
Cc: IPv6 Deployment Prevention <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 03 Oct 2013 06:30:02 -0000

On Thu, 3 Oct 2013, Randy Bush wrote:

> https://labs.ripe.net/Members/emileaben/ripe-atlas-packet-size-matters

I've commented on the article that it would be interesting for them to 
test smaller packets with IPv6 fragmentation header as well.

It's been discussed before that several platforms in live networks have 
default settings that slow-path packets with fragmentation header 
regardless of size. It would be interesting to actually see data of this.

The comment part seems to be moderated so my posting hasn't made it out 
yet.

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

From fgont@si6networks.com  Thu Oct  3 22:57:08 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D68C221F9AB4 for <ipv6@ietfa.amsl.com>; Thu,  3 Oct 2013 22:57:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YYu2Z+SJbv9s for <ipv6@ietfa.amsl.com>; Thu,  3 Oct 2013 22:57:00 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 0837121F9AE3 for <ipv6@ietf.org>; Thu,  3 Oct 2013 22:56:51 -0700 (PDT)
Received: from 17-153-16-190.fibertel.com.ar ([190.16.153.17] helo=[192.168.1.101]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1VRyNQ-0001Pf-RK; Fri, 04 Oct 2013 07:56:37 +0200
Message-ID: <524E588F.1010005@si6networks.com>
Date: Fri, 04 Oct 2013 02:56:31 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Tom Taylor <tom.taylor.stds@gmail.com>,  Ronald Bonica <rbonica@juniper.net>
Subject: Re: AD Evaluation: draft-ietf-6man-oversized-header-chain
References: <524B1F88.9010800@innovationslab.net> <935781b65bdb463ab975b9000a4593f3@CO1PR05MB442.namprd05.prod.outlook.com> <524C3A4E.8010901@innovationslab.net> <17cd3fd88dc54d72895e9443c4b1d426@CO1PR05MB442.namprd05.prod.outlook.com> <524C4B60.8020408@innovationslab.net> <993aed26211c46069aee80d331864aa7@CO1PR05MB442.namprd05.prod.outlook.com> <524CB151.3090103@gmail.com>
In-Reply-To: <524CB151.3090103@gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Brian Haberman <brian@innovationslab.net>, 6man WG <ipv6@ietf.org>, "draft-ietf-6man-oversized-header-chain.all@tools.ietf.org" <draft-ietf-6man-oversized-header-chain.all@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 04 Oct 2013 05:57:08 -0000

On 10/02/2013 08:50 PM, Tom Taylor wrote:
> Just a trivial change: "including" -> "subject to"

Agreed. But I can fix it this after IETF LC or even durng AUTH48.

Thanks!

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





From nalini.elkins@insidethestack.com  Fri Oct  4 06:21:15 2013
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BC6A21F9D12 for <ipv6@ietfa.amsl.com>; Fri,  4 Oct 2013 06:21:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.298
X-Spam-Level: 
X-Spam-Status: No, score=-1.298 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2pbbcEdpX0AP for <ipv6@ietfa.amsl.com>; Fri,  4 Oct 2013 06:21:15 -0700 (PDT)
Received: from nm4-vm1.access.bullet.mail.gq1.yahoo.com (nm4-vm1.access.bullet.mail.gq1.yahoo.com [216.39.63.2]) by ietfa.amsl.com (Postfix) with ESMTP id 4046F21F9DE9 for <ipv6@ietf.org>; Fri,  4 Oct 2013 06:10:29 -0700 (PDT)
Received: from [216.39.60.168] by nm4.access.bullet.mail.gq1.yahoo.com with NNFMP; 04 Oct 2013 13:10:28 -0000
Received: from [216.39.60.240] by tm4.access.bullet.mail.gq1.yahoo.com with NNFMP; 04 Oct 2013 13:10:28 -0000
Received: from [127.0.0.1] by omp1011.access.mail.gq1.yahoo.com with NNFMP; 04 Oct 2013 13:10:28 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 16643.82293.bm@omp1011.access.mail.gq1.yahoo.com
Received: (qmail 95265 invoked by uid 60001); 4 Oct 2013 13:10:27 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1380892227; bh=fGwGyFKWNrkAC9bp4LoU06ni1pokIRQ3q2sC8GwQR2Q=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=bukK02xBhaw21ncpciCQV98nHYRJo0kzW/SG5ZcTu8dtizqn1RdgAgT9eGUJ/2FrmAUkYqE2MdEtgkItW+f91V5oGwNXBwvhHUYsRIV42Dd/Fz0Rfe3PWiT5fb0iH3j3kIPG3w77pOV5KF9XXjKayAAyzfPVUHnq5FaRvgrONWs=
X-YMail-OSG: BU4VMsYVM1l.PM9E_dXxBjdCBiUriVFJuo8ad5LfRLssNiA FoM9I2aTaZnHhizWEAcHn9mXRDr5GiP_Xz9bmp8Uw5ngnNYbd7O4Gk7clo7s ecCZrUA4a.ZIGcVjAYuVFU_e2KHX8ZZgYNNf8DXqCg_FqiyUbiRckOdlXr5w H2qOZA7Gtce3rfpWvFAEaRzAYwQJdibTqZXox6keqolHQ5VNe9TeMRogjD5M 3AlvmvlEw_n6826WVFNNYZEB5Z6IcDPe7acO_79clriLfl0g0K.qqtd1nyJv kLjPra0cj3mPJJb9_Jl8GiL7U8WSgoOSUdV3Fi_HuQnWEy7XUuc5_KCDWNMd RCHMS8bUXJHY3NvjRnOXqp00Y3iJIiXfJrlDhLeBr6SD3fHeCFM1FyyWYUCZ 1nw9uYmMkNuV.ywtEdepH3w2fQcGyF7UyzGrmUOs62TSWlDOY.iQvPyb0qij c32iP.7wS1EpbbqtUI46ktCh32oz8eEYO6vU0iemxvqBHc0UTTTL7d0nIcN3 SlTHAgV2bEnviX5Wk9tT5k8wpLyaDqvUbZ3i3tEnTiagVWA.uh9S0FLs19WP R0Vj6dIARxZiofqiKdAxsb0m6MUGYy1_zPnN4nP9g.SCirZ3obB06UoODshy jDBBGkxPQWiDHZgU.KF1_k7xbUep5nvXN0vSlk5YtzlYoZT8sAuwg22OfTi4 fFDe_dagEzAAUM07JuJk.eKCWEj_hDNVAYeeuRaSGiBXt
Received: from [24.130.37.147] by web2805.biz.mail.ne1.yahoo.com via HTTP; Fri, 04 Oct 2013 06:10:27 PDT
X-Rocket-MIMEInfo: 002.001, CgpXZSBoYXZlIHN1Ym1pdHRlZCBhIG51bWJlciBvZiBkcmFmdHMuIMKgU29tZSBhcmUgbmV3IGFuZCBzb21lIGFyZSB1cGRhdGVzIHRvIG91ciBleGlzdGluZyBQRE0gcHJvcG9zYWwuIMKgV2Ugd291bGQgYXBwcmVjaWF0ZSBhbnkgY29tbWVudHMsIHF1ZXN0aW9ucywgYW5kIGNvcnJlY3Rpb25zIGZyb20gdGhlIGxpc3RzLgoKClRoZSBuZXcgb25lcyBhcmU6CgoxLiDCoEluIElQUE06CgpodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1lbGtpbnMtaXBwbS1wZG0tbWV0cmljcy0wMC4BMAEBAQE-
X-Mailer: YahooMailWebService/0.8.160.587
References: <20131004030407.30291.83858.idtracker@ietfa.amsl.com>
Message-ID: <1380892227.93952.YahooMailNeo@web2805.biz.mail.ne1.yahoo.com>
Date: Fri, 4 Oct 2013 06:10:27 -0700 (PDT)
From: Nalini Elkins <nalini.elkins@insidethestack.com>
Subject: Fw: New Version Notification for draft-elkins-ippm-pdm-metrics-00.txt
To: "WG \(v6ops@ietf.org\)" <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>
In-Reply-To: <20131004030407.30291.83858.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="1619178251-585868665-1380892227=:93952"
Cc: Sigfrido Perdomo <sperdomo@dtcc.com>, Bill Jouris <bill.jouris@insidethestack.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Nalini Elkins <nalini.elkins@insidethestack.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: Fri, 04 Oct 2013 13:21:15 -0000

--1619178251-585868665-1380892227=:93952
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

=0A=0AWe have submitted a number of drafts. =A0Some are new and some are up=
dates to our existing PDM proposal. =A0We would appreciate any comments, qu=
estions, and corrections from the lists.=0A=0A=0AThe new ones are:=0A=0A1. =
=A0In IPPM:=0A=0Ahttp://www.ietf.org/internet-drafts/draft-elkins-ippm-pdm-=
metrics-00.txt=0A=0AThis describes the base and derived metrics which can b=
e obtained from the IPv6 PDM DO Extension Header.=0A=0A=0A2. =A0In TicToc:=
=0A=0Ahttp://www.ietf.org/internet-drafts/draft-ackermann-tictoc-pdm-ntp-us=
age-00.txt=0A=0A=0AThis describes how NTP may be implemented to support PDM=
.=0A=0A=0AThe updates are as follows=0A=0A1. =A0In=A06man:=0A=0Ahttp://www.=
ietf.org/internet-drafts/draft-elkins-ippm-pdm-metrics-00.txt=0A=0A=0AThis =
is the layout of the PDM DO header.=0A=0A=0A2. =A0In v6ops:=0A=0Ahttp://www=
.ietf.org/internet-drafts/draft-elkins-v6ops-ipv6-packet-sequence-needed-01=
.txt=0A=0A=0Ahttp://www.ietf.org/internet-drafts/draft-elkins-v6ops-ipv6-pd=
m-recommended-usage-01.txt=0A=0A=0Ahttp://www.ietf.org/internet-drafts/draf=
t-elkins-v6ops-ipv6-end-to-end-rt-needed-01.txt=0A=0A=0AThese are=A0backgro=
und for the proposal.=0A=0A=A0=0AThanks,=0A=0ANalini Elkins=0AInside Produc=
ts, Inc.=0A(831) 659-8360=0Awww.insidethestack.com=0A=0A=0A----- Forwarded =
Message -----=0AFrom: "internet-drafts@ietf.org" <internet-drafts@ietf.org>=
=0ATo: Nalini Elkins <nalini.elkins@insidethestack.com>; William Jouris <bi=
ll.jouris@insidethestack.com> =0ASent: Thursday, October 3, 2013 8:04 PM=0A=
Subject: New Version Notification for draft-elkins-ippm-pdm-metrics-00.txt=
=0A =0A=0A=0AA new version of I-D, draft-elkins-ippm-pdm-metrics-00.txt=0Ah=
as been successfully submitted by Nalini Elkins and posted to the=0AIETF re=
pository.=0A=0AFilename:=A0=A0=A0  draft-elkins-ippm-pdm-metrics=0ARevision=
:=A0=A0=A0  00=0ATitle:=A0=A0=A0 =A0=A0=A0  IPPM Considerations for the IPv=
6 PDM Extension Header=0ACreation date:=A0=A0=A0  2013-10-03=0AGroup:=A0=A0=
=A0 =A0=A0=A0  Individual Submission=0ANumber of pages: 14=0AURL:=A0 =A0 =
=A0 =A0 =A0 =A0  http://www.ietf.org/internet-drafts/draft-elkins-ippm-pdm-=
metrics-00.txt=0AStatus:=A0 =A0 =A0 =A0 =A0 http://datatracker.ietf.org/doc=
/draft-elkins-ippm-pdm-metrics=0AHtmlized:=A0 =A0 =A0 =A0 http://tools.ietf=
.org/html/draft-elkins-ippm-pdm-metrics-00=0A=0A=0AAbstract:=0A=A0  To diag=
nose performance and connectivity problems, metrics on real=0A=A0  (non-syn=
thetic) transmission are critical for timely end-to-end=0A=A0  problem reso=
lution. Such diagnostics may be real-time or after the=0A=A0  fact, but mus=
t not impact an operational production network. These=0A=A0  metrics are de=
fined in the IPv6 Performance and Diagnostic Metrics=0A=A0  Destination Opt=
ion (PDM). The base metrics are: packet sequence=0A=A0  number and packet t=
imestamp. Other metrics may be derived from these=0A=A0  for use in diagnos=
tics.=A0 This document specifies such metrics, their=0A=A0  calculation, an=
d usage.=0A=0A=0A=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =0A=0A=0APlease note that it may take a co=
uple of minutes from the time of submission=0Auntil the htmlized version an=
d diff are available at tools.ietf.org.=0A=0AThe IETF Secretariat
--1619178251-585868665-1380892227=:93952
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:ar=
ial, helvetica, sans-serif;font-size:12pt"><div style=3D"font-family: arial=
, helvetica, sans-serif; font-size: 12pt;"><span><br></span></div><div styl=
e=3D"font-family: arial, helvetica, sans-serif; font-size: 16px; color: rgb=
(0, 0, 0); background-color: transparent; font-style: normal;"><span>We hav=
e submitted a number of drafts. &nbsp;Some are new and some are updates to =
our existing PDM proposal. &nbsp;We would appreciate any comments, question=
s, and corrections from the lists.</span></div><div style=3D"font-family: a=
rial, helvetica, sans-serif; font-size: 16px; color: rgb(0, 0, 0); backgrou=
nd-color: transparent; font-style: normal;"><span><br></span></div><div sty=
le=3D"font-family: arial, helvetica, sans-serif; font-size: 16px; color: rg=
b(0, 0, 0); background-color: transparent; font-style: normal;"><span><br><=
/span></div><div style=3D"font-family: arial, helvetica, sans-serif; font-s=
ize:
 16px; color: rgb(0, 0, 0); background-color: transparent; font-style: norm=
al;"><span>The new ones are:</span></div><div style=3D"font-family: arial, =
helvetica, sans-serif; font-size: 16px; color: rgb(0, 0, 0); background-col=
or: transparent; font-style: normal;"><span><br></span></div><div style=3D"=
font-family: arial, helvetica, sans-serif; font-size: 16px; color: rgb(0, 0=
, 0); background-color: transparent; font-style: normal;"><span>1. &nbsp;In=
 IPPM:</span></div><div style=3D"font-family: arial, helvetica, sans-serif;=
 font-size: 16px; color: rgb(0, 0, 0); background-color: transparent; font-=
style: normal;"><span><br></span></div><div style=3D"font-family: arial, he=
lvetica, sans-serif; font-size: 16px; color: rgb(0, 0, 0); background-color=
: transparent; font-style: normal;"><span>http://www.ietf.org/internet-draf=
ts/draft-elkins-ippm-pdm-metrics-00.txt</span></div><div style=3D"font-fami=
ly: arial, helvetica, sans-serif; font-size: 16px; color: rgb(0, 0, 0);
 background-color: transparent; font-style: normal;"><span><br></span></div=
><div style=3D"font-family: arial, helvetica, sans-serif; font-size: 16px; =
color: rgb(0, 0, 0); background-color: transparent; font-style: normal;"><s=
pan>This describes the base and derived metrics which can be obtained from =
the IPv6 PDM DO Extension Header.</span></div><div style=3D"font-family: ar=
ial, helvetica, sans-serif; font-size: 16px; color: rgb(0, 0, 0); backgroun=
d-color: transparent; font-style: normal;"><span><br></span></div><div styl=
e=3D"font-family: arial, helvetica, sans-serif; font-size: 16px; color: rgb=
(0, 0, 0); background-color: transparent; font-style: normal;"><span><br></=
span></div><div style=3D"font-family: arial, helvetica, sans-serif; font-si=
ze: 16px; color: rgb(0, 0, 0); background-color: transparent; font-style: n=
ormal;"><span>2. &nbsp;In TicToc:</span></div><div style=3D"font-family: ar=
ial, helvetica, sans-serif; font-size: 16px; color: rgb(0, 0, 0);
 background-color: transparent; font-style: normal;"><span><br></span></div=
><div style=3D"background-color: transparent;"><span>http://www.ietf.org/in=
ternet-drafts/draft-ackermann-tictoc-pdm-ntp-usage-00.txt<br></span></div><=
div style=3D"background-color: transparent; color: rgb(0, 0, 0); font-size:=
 16px; font-family: arial, helvetica, sans-serif; font-style: normal;"><spa=
n><br></span></div><div style=3D"background-color: transparent; color: rgb(=
0, 0, 0); font-size: 16px; font-family: arial, helvetica, sans-serif; font-=
style: normal;"><span>This describes how NTP may be implemented to support =
PDM.</span></div><div style=3D"background-color: transparent; color: rgb(0,=
 0, 0); font-size: 16px; font-family: arial, helvetica, sans-serif; font-st=
yle: normal;"><span><br></span></div><div style=3D"background-color: transp=
arent; color: rgb(0, 0, 0); font-size: 16px; font-family: arial, helvetica,=
 sans-serif; font-style: normal;"><span><br></span></div><div
 style=3D"background-color: transparent; color: rgb(0, 0, 0); font-size: 16=
px; font-family: arial, helvetica, sans-serif; font-style: normal;"><span>T=
he updates are as follows</span></div><div style=3D"background-color: trans=
parent; color: rgb(0, 0, 0); font-size: 16px; font-family: arial, helvetica=
, sans-serif; font-style: normal;"><span><br></span></div><div style=3D"fon=
t-family: arial, helvetica, sans-serif; font-size: 16px; color: rgb(0, 0, 0=
); background-color: transparent; font-style: normal;">1. &nbsp;In&nbsp;<sp=
an style=3D"background-color: transparent;">6man:</span></div><div style=3D=
"font-family: arial, helvetica, sans-serif; font-size: 16px; color: rgb(0, =
0, 0); background-color: transparent; font-style: normal;"><span style=3D"b=
ackground-color: transparent;"><br></span></div><div style=3D"background-co=
lor: transparent;"><span style=3D"background-color: transparent;">http://ww=
w.ietf.org/internet-drafts/draft-elkins-ippm-pdm-metrics-00.txt<br></span><=
/div><div
 style=3D"background-color: transparent; color: rgb(0, 0, 0); font-size: 16=
px; font-family: arial, helvetica, sans-serif; font-style: normal;"><span s=
tyle=3D"background-color: transparent;"><br></span></div><div style=3D"back=
ground-color: transparent; color: rgb(0, 0, 0); font-size: 16px; font-famil=
y: arial, helvetica, sans-serif; font-style: normal;"><span style=3D"backgr=
ound-color: transparent;">This is the layout of the PDM DO header.</span></=
div><div style=3D"background-color: transparent; color: rgb(0, 0, 0); font-=
size: 16px; font-family: arial, helvetica, sans-serif; font-style: normal;"=
><span style=3D"background-color: transparent;"><br></span></div><div style=
=3D"background-color: transparent; color: rgb(0, 0, 0); font-size: 16px; fo=
nt-family: arial, helvetica, sans-serif; font-style: normal;"><span style=
=3D"background-color: transparent;"><br></span></div><div style=3D"backgrou=
nd-color: transparent; color: rgb(0, 0, 0); font-size: 16px; font-family: a=
rial,
 helvetica, sans-serif; font-style: normal;"><span style=3D"background-colo=
r: transparent;">2. &nbsp;In v6ops:</span></div><div style=3D"background-co=
lor: transparent; color: rgb(0, 0, 0); font-size: 16px; font-family: arial,=
 helvetica, sans-serif; font-style: normal;"><span style=3D"background-colo=
r: transparent;"><br></span></div><div style=3D"background-color: transpare=
nt;"><span style=3D"background-color: transparent;">http://www.ietf.org/int=
ernet-drafts/draft-elkins-v6ops-ipv6-packet-sequence-needed-01.txt<br></spa=
n></div><div style=3D"background-color: transparent; color: rgb(0, 0, 0); f=
ont-size: 16px; font-family: arial, helvetica, sans-serif; font-style: norm=
al;"><span style=3D"background-color: transparent;"><br></span></div><div s=
tyle=3D"background-color: transparent;"><span style=3D"background-color: tr=
ansparent;">http://www.ietf.org/internet-drafts/draft-elkins-v6ops-ipv6-pdm=
-recommended-usage-01.txt<br></span></div><div style=3D"background-color: t=
ransparent;
 color: rgb(0, 0, 0); font-size: 16px; font-family: arial, helvetica, sans-=
serif; font-style: normal;"><span style=3D"background-color: transparent;">=
<br></span></div><div style=3D"background-color: transparent;"><span style=
=3D"background-color: transparent;">http://www.ietf.org/internet-drafts/dra=
ft-elkins-v6ops-ipv6-end-to-end-rt-needed-01.txt<br></span></div><div style=
=3D"font-family: arial, helvetica, sans-serif; font-size: 16px; color: rgb(=
0, 0, 0); background-color: transparent; font-style: normal;"><br></div><di=
v style=3D"font-family: arial, helvetica, sans-serif; font-size: 16px; colo=
r: rgb(0, 0, 0); background-color: transparent; font-style: normal;">These =
are&nbsp;<span style=3D"background-color: transparent;">background for the =
proposal.</span></div><div style=3D"font-family: arial, helvetica, sans-ser=
if; font-size: 16px; color: rgb(0, 0, 0); background-color: transparent; fo=
nt-style: normal;"><span style=3D"background-color:
 transparent;"><br></span></div><div style=3D"font-family: arial, helvetica=
, sans-serif; font-size: 12pt;"></div><div style=3D"font-family: arial, hel=
vetica, sans-serif; font-size: 12pt;">&nbsp;</div><div style=3D"font-family=
: arial, helvetica, sans-serif; font-size: 12pt;">Thanks,</div><div style=
=3D"font-family: arial, helvetica, sans-serif; font-size: 12pt;"><br></div>=
<div style=3D"font-family: arial, helvetica, sans-serif; font-size: 12pt;">=
Nalini Elkins<br>Inside Products, Inc.<br>(831) 659-8360<br>www.insidethest=
ack.com<br></div><br>  <div style=3D"font-family: arial, helvetica, sans-se=
rif; font-size: 12pt;"> <div style=3D"font-family: 'times new roman', 'new =
york', times, serif; font-size: 12pt;"> <div dir=3D"ltr"> ----- Forwarded M=
essage -----<br>  <font size=3D"2" face=3D"Arial"> <b><span style=3D"font-w=
eight:bold;">From:</span></b> "internet-drafts@ietf.org" &lt;internet-draft=
s@ietf.org&gt;<br> <b><span style=3D"font-weight: bold;">To:</span></b> Nal=
ini Elkins
 &lt;nalini.elkins@insidethestack.com&gt;; William Jouris &lt;bill.jouris@i=
nsidethestack.com&gt; <br> <b><span style=3D"font-weight: bold;">Sent:</spa=
n></b> Thursday, October 3, 2013 8:04 PM<br> <b><span style=3D"font-weight:=
 bold;">Subject:</span></b> New Version Notification for draft-elkins-ippm-=
pdm-metrics-00.txt<br> </font> </div> <div class=3D"y_msg_container"><br>=
=0A<br>A new version of I-D, draft-elkins-ippm-pdm-metrics-00.txt<br>has be=
en successfully submitted by Nalini Elkins and posted to the<br>IETF reposi=
tory.<br><br>Filename:&nbsp;&nbsp;&nbsp;  draft-elkins-ippm-pdm-metrics<br>=
Revision:&nbsp;&nbsp;&nbsp;  00<br>Title:&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nb=
sp;  IPPM Considerations for the IPv6 PDM Extension Header<br>Creation date=
:&nbsp;&nbsp;&nbsp;  2013-10-03<br>Group:&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nb=
sp;  Individual Submission<br>Number of pages: 14<br>URL:&nbsp; &nbsp; &nbs=
p; &nbsp; &nbsp; &nbsp;  http://www.ietf.org/internet-drafts/draft-elkins-i=
ppm-pdm-metrics-00.txt<br>Status:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; http://=
datatracker.ietf.org/doc/draft-elkins-ippm-pdm-metrics<br>Htmlized:&nbsp; &=
nbsp; &nbsp; &nbsp; http://tools.ietf.org/html/draft-elkins-ippm-pdm-metric=
s-00<br><br><br>Abstract:<br>&nbsp;  To diagnose performance and connectivi=
ty problems, metrics on real<br>&nbsp;  (non-synthetic) transmission
 are critical for timely end-to-end<br>&nbsp;  problem resolution. Such dia=
gnostics may be real-time or after the<br>&nbsp;  fact, but must not impact=
 an operational production network. These<br>&nbsp;  metrics are defined in=
 the IPv6 Performance and Diagnostic Metrics<br>&nbsp;  Destination Option =
(PDM). The base metrics are: packet sequence<br>&nbsp;  number and packet t=
imestamp. Other metrics may be derived from these<br>&nbsp;  for use in dia=
gnostics.&nbsp; This document specifies such metrics, their<br>&nbsp;  calc=
ulation, and usage.<br><br><br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; <br><br><br>Please note that it may take a couple of minu=
tes from the time of submission<br>until the htmlized version and
 diff are available at <a target=3D"_blank" href=3D"http://tools.ietf.org/"=
>tools.ietf.org</a>.<br><br>The IETF Secretariat<br><br><br><br></div> </di=
v> </div>  </div></body></html>
--1619178251-585868665-1380892227=:93952--

From barryleiba@computer.org  Fri Oct  4 11:29:31 2013
Return-Path: <barryleiba@computer.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF90721F9C87; Fri,  4 Oct 2013 11:29:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.266
X-Spam-Level: 
X-Spam-Status: No, score=-102.266 tagged_above=-999 required=5 tests=[AWL=0.334, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rMTfCmwIggEv; Fri,  4 Oct 2013 11:29:31 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CC9A21F841A; Fri,  4 Oct 2013 11:29:31 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: "Barry Leiba" <barryleiba@computer.org>
To: The IESG <iesg@ietf.org>
Subject: Barry Leiba's No Objection on draft-ietf-6man-ext-transmit-04: (with COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131004182931.8835.74697.idtracker@ietfa.amsl.com>
Date: Fri, 04 Oct 2013 11:29:31 -0700
Cc: 6man-chairs@tools.ietf.org, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 04 Oct 2013 18:29:32 -0000

Barry Leiba has entered the following ballot position for
draft-ietf-6man-ext-transmit-04: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-6man-ext-transmit/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

As "Catch 22" is one of my favourite books (
http://staringatemptypages.blogspot.com/2007/10/you-must-read-this.html
), it pleases me to know that there'll be an RFC with a reference to it.

-- Section 4 --

   Additionally, IANA is requested to make the existing empty IPv6 Next
   Header Types registry redirect users to a new IPv6 Extension Header
   Types registry.  It will contain only those protocol numbers which
   are also marked as IPv6 Extension Header types in the Assigned
   Internet Protocol Numbers registry.

Two small points here:

1. "It" in the second sentence is ambiguous: it could refer to either of
the registries mentioned in the first sentence.  I suggest making it "The
IPv6 Extension Header Types registry will contain...".

2. Is it your intent that the (empty) IPv6 Next Header Types registry
also be closed to new registrations?  Whether or not, it would be best to
make that clear.



From brian.e.carpenter@gmail.com  Fri Oct  4 11:56:33 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0FD721F9CC6; Fri,  4 Oct 2013 11:56:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jwk4oWlMFNSw; Fri,  4 Oct 2013 11:56:33 -0700 (PDT)
Received: from mail-pb0-x22a.google.com (mail-pb0-x22a.google.com [IPv6:2607:f8b0:400e:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 54D1821F9CC5; Fri,  4 Oct 2013 11:56:33 -0700 (PDT)
Received: by mail-pb0-f42.google.com with SMTP id un15so4417608pbc.1 for <multiple recipients>; Fri, 04 Oct 2013 11:56:32 -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=MTBqzGA7/vTPJ2gAa2IUG5DX7UUyOUyR+kYR3xq/uCM=; b=l7VDGGN8X40YopSGlvdK2R+3VjAcjZGS/jCtG3KhATLpfu9EQmUyT+Cgsa+Su8z0+o v/2vrX2GSLvUS4j48QnxWOpY+7Uu5E9CFDeKvX8BWlDtBRqDookM8dhau5MvRu83gaKl dKdn9W8kHZbWCsQEGLn9ttiQMySXUZY4rVys9MzEjtfHDVqZz766dfBPwlRTXm1l6F5U Em7bm6k7b2xVFV+h2q9nntTejIY70PJ7Vm4NacHamnhl4R9MxObVNg4kAsHOVJZ5qVxE WWrDr+dGSyNl+CRD7kbWBhxQPjEa3byMNL2WIPi/5Fnvw2oJCFk97jKt7jCBAn/fiJMi ikIg==
X-Received: by 10.66.216.193 with SMTP id os1mr17383870pac.29.1380912653763; Fri, 04 Oct 2013 11:50:53 -0700 (PDT)
Received: from [192.168.178.20] (185.196.69.111.dynamic.snap.net.nz. [111.69.196.185]) by mx.google.com with ESMTPSA id f2sm16290580pbg.44.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 04 Oct 2013 11:50:52 -0700 (PDT)
Message-ID: <524F0E14.1010707@gmail.com>
Date: Sat, 05 Oct 2013 07:51:00 +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: Barry Leiba <barryleiba@computer.org>
Subject: Re: Barry Leiba's No Objection on draft-ietf-6man-ext-transmit-04: (with COMMENT)
References: <20131004182931.8835.74697.idtracker@ietfa.amsl.com>
In-Reply-To: <20131004182931.8835.74697.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 6man-chairs@tools.ietf.org, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org, The IESG <iesg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 04 Oct 2013 18:56:33 -0000

Hi Barry,

On 05/10/2013 07:29, Barry Leiba wrote:
...
> -- Section 4 --
> 
>    Additionally, IANA is requested to make the existing empty IPv6 Next
>    Header Types registry redirect users to a new IPv6 Extension Header
>    Types registry.  It will contain only those protocol numbers which
>    are also marked as IPv6 Extension Header types in the Assigned
>    Internet Protocol Numbers registry.
> 
> Two small points here:
> 
> 1. "It" in the second sentence is ambiguous: it could refer to either of
> the registries mentioned in the first sentence.  I suggest making it "The
> IPv6 Extension Header Types registry will contain...".

OK

> 
> 2. Is it your intent that the (empty) IPv6 Next Header Types registry
> also be closed to new registrations?  Whether or not, it would be best to
> make that clear.

Good catch. IMHO, it should be formally closed.

I'd be happy to see these as RFC Editor changes.

Thanks
    Brian

From Fred.L.Templin@boeing.com  Fri Oct  4 13:41:56 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC37D21F9E00; Fri,  4 Oct 2013 13:41:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0zJ-tqHw46a9; Fri,  4 Oct 2013 13:41:50 -0700 (PDT)
Received: from blv-mbsout-01.boeing.com (blv-mbsout-01.boeing.com [130.76.32.231]) by ietfa.amsl.com (Postfix) with ESMTP id 448B621F9E3A; Fri,  4 Oct 2013 13:41:39 -0700 (PDT)
Received: from blv-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r94KfdPe026666; Fri, 4 Oct 2013 13:41:39 -0700
Received: from XCH-NWHT-08.nw.nos.boeing.com (xch-nwht-08.nw.nos.boeing.com [130.247.25.112]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r94Kfbbg026628 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 4 Oct 2013 13:41:38 -0700
Received: from XCH-BLV-406.nw.nos.boeing.com (130.247.25.162) by XCH-NWHT-08.nw.nos.boeing.com (130.247.25.112) with Microsoft SMTP Server (TLS) id 8.3.327.1; Fri, 4 Oct 2013 13:41:37 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.29]) by XCH-BLV-406.nw.nos.boeing.com ([169.254.6.110]) with mapi id 14.02.0328.011; Fri, 4 Oct 2013 13:41:36 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOv6KmVHjrcZv7kkeUppI3Iq7lo5nk+jmg
Date: Fri, 4 Oct 2013 20:41:35 +0000
Message-ID: <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com>
In-Reply-To: <20131002185522.20697.96027.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 04 Oct 2013 20:41:56 -0000

Hi, I have a concern about this document. In the definition of "IPv6
Header Chain", it says:

  "However, if a second IPv6 header appears in the header chain, as
   is the case when IPv6 is tunneled over IPv6, the second IPv6
   header is considered to be an upper-layer header and terminates
   the header chain."

This means that stateless firewalls are being directed to discontinue
extension header parsing when a first encapsulated IPv6 header is
encountered - even though there may be many more parsable (inner)
headers that follow. As a result, the firewall would either have to
drop or forward the packet without examining the true upper layer
header. This may result in an incorrect perception that tunneled
traffic is either less reliable or more dangerous than non-tunneled
traffic.

Here are my suggested changes to address this issue:

1) Section 3, under "IPv6 Header Chain", change:

  "However, if a second IPv6 header appears in the header chain, as
   is the case when IPv6 is tunneled over IPv6, the second IPv6
   header is considered to be an upper-layer header and terminates
   the header chain."

to:

  "However, if a second IPv6 header appears in the header chain, as
   is the case when IPv6 is tunneled over IPv6, the second IPv6
   header is optionally considered to be either an upper-layer header
   that terminates the header chain or another extension header that
   continues the chain."

2) Section 3, under "Upper-layer Header", change:

  "In the general case, the upper-layer header is the first member
   of the header chain that is neither an IPv6 header nor an IPv6
   extension header."

to:

  "In the general case, the upper-layer header is the first member
   of the header chain that is not considered to be an extension header."

3) Section 3, under "Upper-layer Header", delete the following sentence:

  "However, if either an ESP header, or a second IPv6 header occur in
   the header chain, they are considered to be upper layer headers and
   they terminate the header chain."

4) Section 5, change the final paragraph to:

  "As a result of the above mentioned requirements, a packet's header
   chain length cannot exceed the Path MTU associated with its
   destination.  Hosts MAY discover the Path MTU, using procedures such
   as those defined in [RFC1981] and [RFC4821].  However, if a host does
   not discover the Path MTU, it MUST limit the header chain length to
   1024 bytes.  Limiting the header chain length to 1024 bytes ensures
   that the header chain length does not exceed the IPv6 minimum MTU
   [RFC2460] even if additional encapsulation headers are inserted by
   tunnels on the path."

Thanks - Fred
Fred.l.templin@boeing.com


=20

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> The IESG
> Sent: Wednesday, October 02, 2013 11:55 AM
> To: IETF-Announce
> Cc: ipv6@ietf.org
> Subject: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
>=20
> The IESG has received a request from the IPv6 Maintenance WG (6man) to
> consider the following document:
> - 'Implications of Oversized IPv6 Header Chains'
>   <draft-ietf-6man-oversized-header-chain-08.txt> as Proposed Standard
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-10-16. Exceptionally, comments may
> be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>=20
>    The IPv6 specification allows IPv6 header chains of an arbitrary
>    size.  The specification also allows options which can in turn
> extend
>    each of the headers.  In those scenarios in which the IPv6 header
>    chain or options are unusually long and packets are fragmented, or
>    scenarios in which the fragment size is very small, the first
>    fragment of a packet may fail to include the entire IPv6 header
>    chain.  This document discusses the interoperability and security
>    problems of such traffic, and updates RFC 2460 such that the first
>    fragment of a packet is required to contain the entire IPv6 header
>    chain.
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-6man-oversized-header-chain/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-6man-oversized-header-
> chain/ballot/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

From adrian@olddog.co.uk  Mon Oct  7 07:43:32 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22F0B11E80EC; Mon,  7 Oct 2013 07:43:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GY1zWYrv1g8N; Mon,  7 Oct 2013 07:43:31 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A1D1511E8149; Mon,  7 Oct 2013 07:43:27 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: The IESG <iesg@ietf.org>
Subject: Adrian Farrel's No Objection on draft-ietf-6man-ext-transmit-04: (with COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131007144327.16131.88173.idtracker@ietfa.amsl.com>
Date: Mon, 07 Oct 2013 07:43:27 -0700
Cc: 6man-chairs@tools.ietf.org, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 07 Oct 2013 14:43:32 -0000

Adrian Farrel has entered the following ballot position for
draft-ietf-6man-ext-transmit-04: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-6man-ext-transmit/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for the work on this document. I have no objection to its
publication and just two minor observations.

---

Section 1.1

A couple of points about the following paragraph:

   In this document "standard" IPv6 extension headers are those
   specified in detail by IETF standards actions.  "Experimental"
   extension headers are those defined by any Experimental RFC, and the
   experimental extension header values 253 and 254 defined by [RFC3692]
   and [RFC4727].  "Defined" extension headers are the "standard"
   extension headers plus the "experimental" ones.

My reading of the IANA registry (http://www.iana.org/assignments/
protocol-numbers/protocol-numbers.xhtml) is that allocations can be made
by IESG Approval or Standards Action. I think both of those are covered
by what you call "standard".

I am not convinced that an experiment that uses an experimental code =

point needs to be documented in an Experimental RFC. =


Are 253 and 254 intended solely for experimental extension headers? =

Couldn't the experiment be an experimental payload protocol?

---

I find myself in I-wouldn't-have-done-it-this-way land, so this is, of
course, just a Comment for you to chew on and accept or reject according
to how it strikes you...

It seems to me unwise to create a new registry that duplicates
information held in another registry. By adding a column to the
"Assigned Internet Protocol Numbers" registry you are making it =

completely clear which are the IPv6 Extension Headers. Rather than risk =

having this registry out of step with your new "IPv6 Extension Header
Types registry", I would have had the existing, empty "IPv6 Next Header
Types" registry redirect users to the "Assigned Internet Protocol
Numbers" registry and mention the existence of the specific column that
identifies extension headers.



From sarikaya2012@gmail.com  Mon Oct  7 09:23:31 2013
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAB3F11E80ED for <ipv6@ietfa.amsl.com>; Mon,  7 Oct 2013 09:23:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.533
X-Spam-Level: 
X-Spam-Status: No, score=-1.533 tagged_above=-999 required=5 tests=[AWL=1.067,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6c4XvQmwh8MS for <ipv6@ietfa.amsl.com>; Mon,  7 Oct 2013 09:23:31 -0700 (PDT)
Received: from mail-lb0-x22c.google.com (mail-lb0-x22c.google.com [IPv6:2a00:1450:4010:c04::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 4A50A11E80F2 for <6man@ietf.org>; Mon,  7 Oct 2013 09:23:14 -0700 (PDT)
Received: by mail-lb0-f172.google.com with SMTP id x18so5807303lbi.17 for <6man@ietf.org>; Mon, 07 Oct 2013 09: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:content-type; bh=Us/kFvtDv4VvBWn1u7foecNxwhXYIbPrOWLnstceJx8=; b=fPeQrLTQpaRod08RmrIx3K6ytKEJuOFxWMAG2To2JTLsTIZ0ApbWyrwHAkpn7shDKS IhL/zNd2N9fJ1w05nVUqWVGP1+lMxbOs7U19HJlCLan8dN5pVXwoqtKBq8lbk2BJazFy rTUR9hMTLFIpg+/TgBCtZ1yl//7hEH227grB17pJFi3nQSRpyt0xp9Z6VYAM4v8OXuHB l16C5nFUYyT0Zw8+jNDMJ+JoraGn1QCQPAMfzMPOBiEBEqiQrfinCQnaShh7DiMfcq+E zOChEH/fZYn+xs5e9vtYDC/KjlKeihNVJLYU6714D/+dkAGPL1zCbDD2bv7Tk3ZnsUNq MdMQ==
MIME-Version: 1.0
X-Received: by 10.112.156.74 with SMTP id wc10mr2011248lbb.44.1381162993163; Mon, 07 Oct 2013 09:23:13 -0700 (PDT)
Received: by 10.114.98.227 with HTTP; Mon, 7 Oct 2013 09:23:13 -0700 (PDT)
Date: Mon, 7 Oct 2013 11:23:13 -0500
Message-ID: <CAC8QAcfxbT4cSewaxVykT=ze7+iLwqPhbifMc5BWXn4Yva8dPg@mail.gmail.com>
Subject: draft-sarikaya-6man-rfc4191bis-00.txt
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: "6man@ietf.org" <6man@ietf.org>
Content-Type: multipart/alternative; boundary=089e0122976c95a3c504e82911bd
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 07 Oct 2013 16:23:32 -0000

--089e0122976c95a3c504e82911bd
Content-Type: text/plain; charset=ISO-8859-1

Hi all,

I had presented this draft in IETF 85 and received many comments from Dave
and Lorenzo.

I have tried to resolve the issues and published the revision as
draft-sarikaya-6man-rfc4191bis-00.txt

I would like to present the draft in Vancouver. Let's discuss the draft on
the list.
Please post your comments, as many as possible :-).

Regards,

Behcet

--089e0122976c95a3c504e82911bd
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div><div><div>Hi all,<br><br></div>I had p=
resented this draft in IETF 85 and received many comments from Dave and Lor=
enzo. <br><br></div>I have tried to resolve the issues and published the re=
vision as draft-sarikaya-6man-rfc4191bis-00.txt<br>
<br></div>I would like to present the draft in Vancouver. Let&#39;s discuss=
 the draft on the list.<br></div>Please post your comments, as many as poss=
ible :-).<br><br></div>Regards,<br><br></div>Behcet<br></div>

--089e0122976c95a3c504e82911bd--

From heard@pobox.com  Mon Oct  7 09:53:52 2013
Return-Path: <heard@pobox.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7798321F9D52 for <ipv6@ietfa.amsl.com>; Mon,  7 Oct 2013 09:53:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f0pcdYpGgDoc for <ipv6@ietfa.amsl.com>; Mon,  7 Oct 2013 09:53:47 -0700 (PDT)
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by ietfa.amsl.com (Postfix) with ESMTP id E657E21F9CC5 for <ipv6@ietf.org>; Mon,  7 Oct 2013 09:53:41 -0700 (PDT)
Received: (qmail 6924 invoked from network); 7 Oct 2013 09:53:40 -0700
Received: from shell4.bayarea.net (209.128.82.1) by shell4.bayarea.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 7 Oct 2013 09:53:40 -0700
Date: Mon, 7 Oct 2013 09:53:40 -0700 (PDT)
From: "C. M. Heard" <heard@pobox.com>
X-X-Sender: heard@shell4.bayarea.net
To: Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: Adrian Farrel's No Objection on draft-ietf-6man-ext-transmit-04: (with COMMENT)
In-Reply-To: <20131007144327.16131.88173.idtracker@ietfa.amsl.com>
Message-ID: <Pine.LNX.4.64.1310070914240.13173@shell4.bayarea.net>
References: <20131007144327.16131.88173.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: 6man-chairs@tools.ietf.org, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org, The IESG <iesg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 07 Oct 2013 16:53:52 -0000

On Mon, 7 Oct 2013, Adrian Farrel wrote:
> Section 1.1
> 
> A couple of points about the following paragraph:
> 
>    In this document "standard" IPv6 extension headers are those
>    specified in detail by IETF standards actions.  "Experimental"
>    extension headers are those defined by any Experimental RFC, and the
>    experimental extension header values 253 and 254 defined by [RFC3692]
>    and [RFC4727].  "Defined" extension headers are the "standard"
>    extension headers plus the "experimental" ones.
...
> Are 253 and 254 intended solely for experimental extension headers? 
> Couldn't the experiment be an experimental payload protocol?

This is a good point.  RFC 3692 calls these out as experimental 
values for the IP Protocol Field, so experiments could in principle 
use these values either for experimental upper layer protocols or 
for experimental IPv6 headers.  Nodes that are not involved in the 
experiment (including middleboxes) would have no way of knowing the 
difference.

This opens up a small can of worms, because Section 2.1 says that 
"[e]xperimental IPv6 extension headers SHOULD be treated in the same 
way as standard extension headers, including an individually 
configurable discard policy."  The problem is that if a node not 
participating in an experiment encounters a next header value of 253 
or 254 it won't know whether to treat what follows as an 
experimental extension header, conforming to the uniform TLV format 
specified in RFC 6564, or an experimental upper-layer protocol, 
where all bets are off with respect to format.  If packets 
containing these values are to be passed by a middlebox not 
participating in an experiment, it seems that the middlebox would 
have to stop parsing when encountering these values, and pass or 
drop the packet depending on what it's supposed to do with unknown 
upper layer protocol protocol types.

(As an aside, it occure to me that the same thing is true if a 
middlebox encounters a next header type that it does not recognize 
-- it won't know if it refers to an extension header or an upper 
layer protocol, and must treat it as the latter.  Hence the 
requirement that "[f]orwarding nodes MUST be configurable to allow 
packets containing unrecognised extension headers" means, in 
practice, that a middlebox needs to have a switch to allow unknown 
upper layer protocols to pass through.)


> ---
> 
> I find myself in I-wouldn't-have-done-it-this-way land, so this is, of
> course, just a Comment for you to chew on and accept or reject according
> to how it strikes you...
> 
> It seems to me unwise to create a new registry that duplicates
> information held in another registry. By adding a column to the
> "Assigned Internet Protocol Numbers" registry you are making it 
> completely clear which are the IPv6 Extension Headers. Rather than risk 
> having this registry out of step with your new "IPv6 Extension Header
> Types registry", I would have had the existing, empty "IPv6 Next Header
> Types" registry redirect users to the "Assigned Internet Protocol
> Numbers" registry and mention the existence of the specific column that
> identifies extension headers.

I think this idea has a lot of merit.  Putting that information in 
the Internet protocol numbers registry would also provide an 
opportunity to fix some things about extention header entryes that 
currently are not quite right, such as:


43	IPv6-Route	Routing Header for IPv6		[Steve_Deering]
44	IPv6-Frag	Fragment Header for IPv6	[Steve_Deering]


Thanks and regards,

Mike Heard

From Fred.L.Templin@boeing.com  Mon Oct  7 11:13:41 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B94111E8109; Mon,  7 Oct 2013 11:13:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fZ6HgwJ1BXjV; Mon,  7 Oct 2013 11:13:36 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) by ietfa.amsl.com (Postfix) with ESMTP id D592521F9FEE; Mon,  7 Oct 2013 11:13:28 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r97IDSkk027794; Mon, 7 Oct 2013 11:13:28 -0700
Received: from XCH-NWHT-01.nw.nos.boeing.com (xch-nwht-01.nw.nos.boeing.com [130.247.70.222]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r97IDRNQ027784 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 7 Oct 2013 11:13:28 -0700
Received: from XCH-BLV-303.nw.nos.boeing.com (130.247.25.215) by XCH-NWHT-01.nw.nos.boeing.com (130.247.70.222) with Microsoft SMTP Server (TLS) id 8.3.327.1; Mon, 7 Oct 2013 11:13:27 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.29]) by XCH-BLV-303.nw.nos.boeing.com ([169.254.3.177]) with mapi id 14.02.0328.011; Mon, 7 Oct 2013 11:13:26 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOv6KmVHjrcZv7kkeUppI3Iq7lo5nk+jmggASVUyA=
Date: Mon, 7 Oct 2013 18:13:26 +0000
Message-ID: <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 07 Oct 2013 18:13:41 -0000

Hi, I would like to make a small amendment to what I said in my
previous message as follows:

4) Section 5, change the final paragraph to:

   "As a result of the above mentioned requirements, a packet's header
   chain length MUST fit within the Path MTU associated with its
   destination.  Hosts MAY discover the Path MTU, using procedures such
   as those defined in [RFC1981] and [RFC4821]. However, if a host does
   not discover the Path MTU, it MUST assume the IPv6 minumum MTU of
   1280 bytes [RFC2460]. The host MUST then limit each packet's header
   chain length to the Path MTU minus 256 bytes in case additional
   encapsulation headers are inserted by tunnels on the path."

Thanks - Fred
fred.l.templin@boeing.com

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Templin, Fred L
> Sent: Friday, October 04, 2013 1:42 PM
> To: ietf@ietf.org; IETF-Announce
> Cc: ipv6@ietf.org
> Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> Hi, I have a concern about this document. In the definition of "IPv6
> Header Chain", it says:
>=20
>   "However, if a second IPv6 header appears in the header chain, as
>    is the case when IPv6 is tunneled over IPv6, the second IPv6
>    header is considered to be an upper-layer header and terminates
>    the header chain."
>=20
> This means that stateless firewalls are being directed to discontinue
> extension header parsing when a first encapsulated IPv6 header is
> encountered - even though there may be many more parsable (inner)
> headers that follow. As a result, the firewall would either have to
> drop or forward the packet without examining the true upper layer
> header. This may result in an incorrect perception that tunneled
> traffic is either less reliable or more dangerous than non-tunneled
> traffic.
>=20
> Here are my suggested changes to address this issue:
>=20
> 1) Section 3, under "IPv6 Header Chain", change:
>=20
>   "However, if a second IPv6 header appears in the header chain, as
>    is the case when IPv6 is tunneled over IPv6, the second IPv6
>    header is considered to be an upper-layer header and terminates
>    the header chain."
>=20
> to:
>=20
>   "However, if a second IPv6 header appears in the header chain, as
>    is the case when IPv6 is tunneled over IPv6, the second IPv6
>    header is optionally considered to be either an upper-layer header
>    that terminates the header chain or another extension header that
>    continues the chain."
>=20
> 2) Section 3, under "Upper-layer Header", change:
>=20
>   "In the general case, the upper-layer header is the first member
>    of the header chain that is neither an IPv6 header nor an IPv6
>    extension header."
>=20
> to:
>=20
>   "In the general case, the upper-layer header is the first member
>    of the header chain that is not considered to be an extension
> header."
>=20
> 3) Section 3, under "Upper-layer Header", delete the following
> sentence:
>=20
>   "However, if either an ESP header, or a second IPv6 header occur in
>    the header chain, they are considered to be upper layer headers and
>    they terminate the header chain."
>=20
> 4) Section 5, change the final paragraph to:
>=20
>   "As a result of the above mentioned requirements, a packet's header
>    chain length cannot exceed the Path MTU associated with its
>    destination.  Hosts MAY discover the Path MTU, using procedures such
>    as those defined in [RFC1981] and [RFC4821].  However, if a host
> does
>    not discover the Path MTU, it MUST limit the header chain length to
>    1024 bytes.  Limiting the header chain length to 1024 bytes ensures
>    that the header chain length does not exceed the IPv6 minimum MTU
>    [RFC2460] even if additional encapsulation headers are inserted by
>    tunnels on the path."
>=20
> Thanks - Fred
> Fred.l.templin@boeing.com
>=20
>=20
>=20
>=20
> > -----Original Message-----
> > From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf
> Of
> > The IESG
> > Sent: Wednesday, October 02, 2013 11:55 AM
> > To: IETF-Announce
> > Cc: ipv6@ietf.org
> > Subject: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> > (Implications of Oversized IPv6 Header Chains) to Proposed Standard
> >
> >
> > The IESG has received a request from the IPv6 Maintenance WG (6man)
> to
> > consider the following document:
> > - 'Implications of Oversized IPv6 Header Chains'
> >   <draft-ietf-6man-oversized-header-chain-08.txt> as Proposed
> Standard
> >
> > The IESG plans to make a decision in the next few weeks, and solicits
> > final comments on this action. Please send substantive comments to
> the
> > ietf@ietf.org mailing lists by 2013-10-16. Exceptionally, comments
> may
> > be
> > sent to iesg@ietf.org instead. In either case, please retain the
> > beginning of the Subject line to allow automated sorting.
> >
> > Abstract
> >
> >
> >    The IPv6 specification allows IPv6 header chains of an arbitrary
> >    size.  The specification also allows options which can in turn
> > extend
> >    each of the headers.  In those scenarios in which the IPv6 header
> >    chain or options are unusually long and packets are fragmented, or
> >    scenarios in which the fragment size is very small, the first
> >    fragment of a packet may fail to include the entire IPv6 header
> >    chain.  This document discusses the interoperability and security
> >    problems of such traffic, and updates RFC 2460 such that the first
> >    fragment of a packet is required to contain the entire IPv6 header
> >    chain.
> >
> >
> >
> >
> > The file can be obtained via
> > http://datatracker.ietf.org/doc/draft-ietf-6man-oversized-header-
> chain/
> >
> > IESG discussion can be tracked via
> > http://datatracker.ietf.org/doc/draft-ietf-6man-oversized-header-
> > chain/ballot/
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
> >
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------

From brian.e.carpenter@gmail.com  Mon Oct  7 12:07:39 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A90B711E811A; Mon,  7 Oct 2013 12:07:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.503
X-Spam-Level: 
X-Spam-Status: No, score=-102.503 tagged_above=-999 required=5 tests=[AWL=0.096, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MtBVOq8C3VjT; Mon,  7 Oct 2013 12:07:39 -0700 (PDT)
Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 7BCF911E8126; Mon,  7 Oct 2013 12:07:30 -0700 (PDT)
Received: by mail-pa0-f54.google.com with SMTP id kx10so7751513pab.41 for <multiple recipients>; Mon, 07 Oct 2013 12:07:30 -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=oJm0q8o1xdNfer+sh9BZaigpmmE8lhTEbIjzNLrRD+A=; b=wWDDNQTAsvqD/hevqPC/HXKSN5VkxR+1uHaT8jVczhuOYUgifLfCC0qF+p7AzJIPld EhAFNiihhJ2rYF3e0cQHbKkKhoJdy5l33teeMnEQNNr4msWr3hs6N4hJbV4S7O0J9Giw L3dg0be/6AzWx42JNBbDUd5whlbGv0RLY1pbXPWewe0D4BrC9991IE5JU69g1DPPeUaC cLwtBoYJBgF8QnHBqRupDeBlG6TtpxUz9WH6IA20ia7H33df5nY//YV4j8t/XB9Ffcf2 NPy9lI0DM3dhvrM4q48Z5M/oyoUHlshDOwafj4Wp/Fvopm3UB9yF160rtcrfhfOlkn5j VQWA==
X-Received: by 10.69.15.197 with SMTP id fq5mr4753066pbd.179.1381172850174; Mon, 07 Oct 2013 12:07:30 -0700 (PDT)
Received: from [192.168.178.20] (58.197.69.111.dynamic.snap.net.nz. [111.69.197.58]) by mx.google.com with ESMTPSA id b3sm34997047pbh.7.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 07 Oct 2013 12:07:29 -0700 (PDT)
Message-ID: <5253066F.5030903@gmail.com>
Date: Tue, 08 Oct 2013 08:07:27 +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: Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: Adrian Farrel's No Objection on draft-ietf-6man-ext-transmit-04: (with COMMENT)
References: <20131007144327.16131.88173.idtracker@ietfa.amsl.com>
In-Reply-To: <20131007144327.16131.88173.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 6man-chairs@tools.ietf.org, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org, The IESG <iesg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 07 Oct 2013 19:07:39 -0000

On 08/10/2013 03:43, Adrian Farrel wrote:
...
> Section 1.1
> 
> A couple of points about the following paragraph:
> 
>    In this document "standard" IPv6 extension headers are those
>    specified in detail by IETF standards actions.  "Experimental"
>    extension headers are those defined by any Experimental RFC, and the
>    experimental extension header values 253 and 254 defined by [RFC3692]
>    and [RFC4727].  "Defined" extension headers are the "standard"
>    extension headers plus the "experimental" ones.
> 
> My reading of the IANA registry (http://www.iana.org/assignments/
> protocol-numbers/protocol-numbers.xhtml) is that allocations can be made
> by IESG Approval or Standards Action. I think both of those are covered
> by what you call "standard".

I don't see that "IESG Approval" implies "standard", but I guess that's
a matter of interpretation.

> I am not convinced that an experiment that uses an experimental code 
> point needs to be documented in an Experimental RFC. 

Yes, the definition could perhaps be slightly wider. s/are those/include those/
for example.

> 
> Are 253 and 254 intended solely for experimental extension headers? 
> Couldn't the experiment be an experimental payload protocol?

I'll comment on Mike Heard's message.

> 
> ---
> 
> I find myself in I-wouldn't-have-done-it-this-way land, so this is, of
> course, just a Comment for you to chew on and accept or reject according
> to how it strikes you...
> 
> It seems to me unwise to create a new registry that duplicates
> information held in another registry. By adding a column to the
> "Assigned Internet Protocol Numbers" registry you are making it 
> completely clear which are the IPv6 Extension Headers. Rather than risk 
> having this registry out of step with your new "IPv6 Extension Header
> Types registry", I would have had the existing, empty "IPv6 Next Header
> Types" registry redirect users to the "Assigned Internet Protocol
> Numbers" registry and mention the existence of the specific column that
> identifies extension headers.

Logically, yes, but I (personally) think that the convenience factor
of a separate list is valuable. We have running code proof in current
firewall implementations that people are *not* identifying the extension
headers today, and we want to make it easy for them.

   Brian
> 
> 
> .
> 

From brian.e.carpenter@gmail.com  Mon Oct  7 12:19:04 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 071CC11E8123; Mon,  7 Oct 2013 12:19:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.511
X-Spam-Level: 
X-Spam-Status: No, score=-102.511 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cAXdWLepfpmH; Mon,  7 Oct 2013 12:19:03 -0700 (PDT)
Received: from mail-pd0-x22f.google.com (mail-pd0-x22f.google.com [IPv6:2607:f8b0:400e:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 038CF11E8128; Mon,  7 Oct 2013 12:19:00 -0700 (PDT)
Received: by mail-pd0-f175.google.com with SMTP id q10so7539524pdj.6 for <multiple recipients>; Mon, 07 Oct 2013 12:19:00 -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=jmnu9iImb7JEFRe5ODTPQPHyGodqaY9ZjrRb1xaLVcA=; b=mLW889gAMWPzmO+NfESiR11eY53qa5GgVKg4mbjJVm0yvmO6LQvk5TBoS6dRqjPpuG Jd/zgfSHorrqS0QYY0Jv1TKCAYuRXYvhuEHz+/q6Dh1SffGTjCGpVgE6uAa0xQO4Gequ Se28Jz6281rSrm0rOXe6W/vXutIZV2/nI7vZGQ4FhDM/OZ/eibLVzL2sTXYzXsw/Wt30 Q49rHqv+oywL4VFhpYC+wkgl0fUi0TeBYcujadmyom1ZLqQhylGAUITEUJG8zWMl/yJI 195LojhF9wARyUTuKNv83lFXrV/r2mOCbUV7Mj2aSq7NMoe+SMfjqtW8FFT5KIobNFSy KFaQ==
X-Received: by 10.66.148.97 with SMTP id tr1mr4895557pab.163.1381173540721; Mon, 07 Oct 2013 12:19:00 -0700 (PDT)
Received: from [192.168.178.20] (58.197.69.111.dynamic.snap.net.nz. [111.69.197.58]) by mx.google.com with ESMTPSA id kd1sm41536612pab.20.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 07 Oct 2013 12:18:59 -0700 (PDT)
Message-ID: <52530921.3060202@gmail.com>
Date: Tue, 08 Oct 2013 08:18:57 +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: "C. M. Heard" <heard@pobox.com>
Subject: Re: Adrian Farrel's No Objection on draft-ietf-6man-ext-transmit-04: (with COMMENT)
References: <20131007144327.16131.88173.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1310070914240.13173@shell4.bayarea.net>
In-Reply-To: <Pine.LNX.4.64.1310070914240.13173@shell4.bayarea.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 6man-chairs@tools.ietf.org, Adrian Farrel <adrian@olddog.co.uk>, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org, The IESG <iesg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 07 Oct 2013 19:19:04 -0000

On 08/10/2013 05:53, C. M. Heard wrote:
> On Mon, 7 Oct 2013, Adrian Farrel wrote:
>> Section 1.1
>>
>> A couple of points about the following paragraph:
>>
>>    In this document "standard" IPv6 extension headers are those
>>    specified in detail by IETF standards actions.  "Experimental"
>>    extension headers are those defined by any Experimental RFC, and the
>>    experimental extension header values 253 and 254 defined by [RFC3692]
>>    and [RFC4727].  "Defined" extension headers are the "standard"
>>    extension headers plus the "experimental" ones.
> ...
>> Are 253 and 254 intended solely for experimental extension headers? 
>> Couldn't the experiment be an experimental payload protocol?
> 
> This is a good point.  RFC 3692 calls these out as experimental 
> values for the IP Protocol Field, so experiments could in principle 
> use these values either for experimental upper layer protocols or 
> for experimental IPv6 headers.  Nodes that are not involved in the 
> experiment (including middleboxes) would have no way of knowing the 
> difference.
> 
> This opens up a small can of worms, because Section 2.1 says that 
> "[e]xperimental IPv6 extension headers SHOULD be treated in the same 
> way as standard extension headers, including an individually 
> configurable discard policy."  The problem is that if a node not 
> participating in an experiment encounters a next header value of 253 
> or 254 it won't know whether to treat what follows as an 
> experimental extension header, conforming to the uniform TLV format 
> specified in RFC 6564, or an experimental upper-layer protocol, 
> where all bets are off with respect to format.  If packets 
> containing these values are to be passed by a middlebox not 
> participating in an experiment, it seems that the middlebox would 
> have to stop parsing when encountering these values, and pass or 
> drop the packet depending on what it's supposed to do with unknown 
> upper layer protocol protocol types.
> 
> (As an aside, it occure to me that the same thing is true if a 
> middlebox encounters a next header type that it does not recognize 
> -- it won't know if it refers to an extension header or an upper 
> layer protocol, and must treat it as the latter.  Hence the 
> requirement that "[f]orwarding nodes MUST be configurable to allow 
> packets containing unrecognised extension headers" means, in 
> practice, that a middlebox needs to have a switch to allow unknown 
> upper layer protocols to pass through.)

Yes, and for a moment there you had me worried, but if the security
concern is that the unknown header may contain bad stuff and/or cause
a buffer overflow bug, then it really doesn't matter whether it is
an extension header or a payload header. In either case, if you let
the packet through, you are assuming that the destination host knows
what it's doing.

We might need a slight rewording to remove the implication that
253/254 can *only* be used as extension headers. Something like:

 "Experimental" extension headers include those defined by any
 Experimental RFC, and the values 253 and 254 defined by [RFC3692]
 and [RFC4727] when used as experimental extension headers.

>> ---
>>
>> I find myself in I-wouldn't-have-done-it-this-way land, so this is, of
>> course, just a Comment for you to chew on and accept or reject according
>> to how it strikes you...
>>
>> It seems to me unwise to create a new registry that duplicates
>> information held in another registry. By adding a column to the
>> "Assigned Internet Protocol Numbers" registry you are making it 
>> completely clear which are the IPv6 Extension Headers. Rather than risk 
>> having this registry out of step with your new "IPv6 Extension Header
>> Types registry", I would have had the existing, empty "IPv6 Next Header
>> Types" registry redirect users to the "Assigned Internet Protocol
>> Numbers" registry and mention the existence of the specific column that
>> identifies extension headers.
> 
> I think this idea has a lot of merit.  

Disagree, for reason given in my previous message.

> Putting that information in 
> the Internet protocol numbers registry would also provide an 
> opportunity to fix some things about extention header entryes that 
> currently are not quite right, such as:
> 
> 
> 43	IPv6-Route	Routing Header for IPv6		[Steve_Deering]
> 44	IPv6-Frag	Fragment Header for IPv6	[Steve_Deering]
> 

We can ask IANA to fix bugs anytime, surely?

    Brian

> 
> Thanks and regards,
> 
> Mike Heard
> 

From heard@pobox.com  Mon Oct  7 14:28:14 2013
Return-Path: <heard@pobox.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6AA711E817B for <ipv6@ietfa.amsl.com>; Mon,  7 Oct 2013 14:28:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6MHa870RYv1I for <ipv6@ietfa.amsl.com>; Mon,  7 Oct 2013 14:28:09 -0700 (PDT)
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by ietfa.amsl.com (Postfix) with ESMTP id A705B11E813D for <ipv6@ietf.org>; Mon,  7 Oct 2013 14:28:09 -0700 (PDT)
Received: (qmail 18952 invoked from network); 7 Oct 2013 14:28:07 -0700
Received: from shell4.bayarea.net (209.128.82.1) by shell4.bayarea.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 7 Oct 2013 14:28:07 -0700
Date: Mon, 7 Oct 2013 14:28:07 -0700 (PDT)
From: "C. M. Heard" <heard@pobox.com>
X-X-Sender: heard@shell4.bayarea.net
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Adrian Farrel's No Objection on draft-ietf-6man-ext-transmit-04: (with COMMENT)
In-Reply-To: <52530921.3060202@gmail.com>
Message-ID: <Pine.LNX.4.64.1310071315370.13828@shell4.bayarea.net>
References: <20131007144327.16131.88173.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1310070914240.13173@shell4.bayarea.net> <52530921.3060202@gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: 6man-chairs@tools.ietf.org, Adrian Farrel <adrian@olddog.co.uk>, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org, The IESG <iesg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 07 Oct 2013 21:28:14 -0000

On Tue, 8 Oct 2013, Brian E Carpenter wrote:
> Yes, and for a moment there you had me worried, but if the security
> concern is that the unknown header may contain bad stuff and/or cause
> a buffer overflow bug, then it really doesn't matter whether it is
> an extension header or a payload header. In either case, if you let
> the packet through, you are assuming that the destination host knows
> what it's doing.

That's correct.

> We might need a slight rewording to remove the implication that
> 253/254 can *only* be used as extension headers. Something like:
> 
>  "Experimental" extension headers include those defined by any
>  Experimental RFC, and the values 253 and 254 defined by [RFC3692]
>  and [RFC4727] when used as experimental extension headers.

That would be a good change to the last paragraph of Section 1.1 but 
I'm not sure that it's sufficient.

Section 2.1 recommends that forwarding nodes that inspect IPv6 
headers be able to parse all defined extension headers and deal with 
them appropriately, specifically by having an individually 
configurable discard policy.  I've assumed that this means that if a 
particular defined extension header type is not blackisted, the 
forwarding node should be able either to examine the innards of that 
header (a likely action with options headers) or skip over it and to 
proceed to the next header.  The problem with next header values 253 
and 254 when used as experimental next header types -- unlike 
assigned experimental extension header types that have a published 
spec -- is that it's not possible for the forwarding node to safely 
examine or skip over the headers they refer to without being part of 
the experiment.

Maybe I'm making too much of this.  Certainly a reasonable action 
for a middlebox that's told to pass packets with extension header 
types 253 and 254 is to stop parsing when it encounters those next 
header types and forward the packet in question.  Maybe that's 
obvious to everyone -- but it seems to me that the spec, as written, 
is actually asking for something different.

I'll gladly shut up if no one else sees a problem.

> > 43	IPv6-Route	Routing Header for IPv6		[Steve_Deering]
> > 44	IPv6-Frag	Fragment Header for IPv6	[Steve_Deering]
> > 
> 
> We can ask IANA to fix bugs anytime, surely?

Yes, and we should do that irrespective of the disposition of 
Adrian's comment.  Since I brought this up, I'll volunteer to bring 
this to IANA's attention if the leadership wants me to do so (please 
let me know).

//cmh

From brian.e.carpenter@gmail.com  Mon Oct  7 17:18:00 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5EDA21E80F3; Mon,  7 Oct 2013 17:18:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.522
X-Spam-Level: 
X-Spam-Status: No, score=-102.522 tagged_above=-999 required=5 tests=[AWL=0.077, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HpUtdlEDEMJy; Mon,  7 Oct 2013 17:18:00 -0700 (PDT)
Received: from mail-pd0-x22b.google.com (mail-pd0-x22b.google.com [IPv6:2607:f8b0:400e:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 3209821E80CC; Mon,  7 Oct 2013 17:17:57 -0700 (PDT)
Received: by mail-pd0-f171.google.com with SMTP id g10so7855877pdj.2 for <multiple recipients>; Mon, 07 Oct 2013 17:17:57 -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=94aJZ8A8kY/Slnv+WekfFBLNxlg7Omxb0qfwbs8r938=; b=sZUPrsBIhH6PMB8dC556BtepDjbUMgWvm9ygF0kjUTFp0+hwGqy94VTslEg+xWxXpy HN7f1wcUj01Vrh5VxiZa4NKYfOSggYxiWui84GUxO5EqyU50+QZhyehfL8LX/h5pQHKz jNH6Q+VoZfDXvfwDnir/s+54+qQ1K52zluWX4E+4si/byuWF+GmRobX+OM6jUUrJDT7V 4jKmiew/J4wK29f2aj58caAHfE/cDYT/56NpZMtLHF0cLxuIh+HY1VAfLXS8lE5fzYAr DomhcWFbb4lBjjpiisz/9vAXVAX3/5HiZV24wQ2LPBQ+ueeOLyRT8ZE8xyj0xRa/2Xpx xz+A==
X-Received: by 10.66.65.134 with SMTP id x6mr232323pas.142.1381191477055; Mon, 07 Oct 2013 17:17:57 -0700 (PDT)
Received: from [192.168.178.20] (58.197.69.111.dynamic.snap.net.nz. [111.69.197.58]) by mx.google.com with ESMTPSA id im2sm35941300pbd.31.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 07 Oct 2013 17:17:56 -0700 (PDT)
Message-ID: <52534F31.2020906@gmail.com>
Date: Tue, 08 Oct 2013 13:17:53 +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: "C. M. Heard" <heard@pobox.com>
Subject: Re: Adrian Farrel's No Objection on draft-ietf-6man-ext-transmit-04: (with COMMENT)
References: <20131007144327.16131.88173.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1310070914240.13173@shell4.bayarea.net> <52530921.3060202@gmail.com> <Pine.LNX.4.64.1310071315370.13828@shell4.bayarea.net>
In-Reply-To: <Pine.LNX.4.64.1310071315370.13828@shell4.bayarea.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 6man-chairs@tools.ietf.org, Adrian Farrel <adrian@olddog.co.uk>, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org, The IESG <iesg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Oct 2013 00:18:00 -0000

On 08/10/2013 10:28, C. M. Heard wrote:
...

> Maybe I'm making too much of this.  Certainly a reasonable action 
> for a middlebox that's told to pass packets with extension header 
> types 253 and 254 is to stop parsing when it encounters those next 
> header types and forward the packet in question.  Maybe that's 
> obvious to everyone -- but it seems to me that the spec, as written, 
> is actually asking for something different.

There's no header length field in an IPv6 header. That means that
since header types 253 and 254 might be used either for experimental
extension headers or for experimental payload types, there's no
generic way for a middlebox to tell the difference. I think that's
an issue that the current draft cannot resolve. I suspect we probably
need an extra sentence to state the problem, but the authors will
wait for direction on that.

    Brian

From joelja@bogus.com  Tue Oct  8 00:19:53 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F123621E815F; Tue,  8 Oct 2013 00:19:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DJ3x9PrKE+3E; Tue,  8 Oct 2013 00:19:52 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 03EAA21E8159; Tue,  8 Oct 2013 00:19:49 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: "Joel Jaeggli" <joelja@bogus.com>
To: The IESG <iesg@ietf.org>
Subject: Joel Jaeggli's Discuss on draft-ietf-6man-ext-transmit-04: (with DISCUSS and COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131008071948.25649.48005.idtracker@ietfa.amsl.com>
Date: Tue, 08 Oct 2013 00:19:48 -0700
Cc: 6man-chairs@tools.ietf.org, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Oct 2013 07:19:53 -0000

Joel Jaeggli has entered the following ballot position for
draft-ietf-6man-ext-transmit-04: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-6man-ext-transmit/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

This is a dicuss because I'd like to see if I'm in the rough in this.

Devices generally considered to be IP routers in fact are able to or find
it necessary to forward on the basis of headers other than the IP header
e.g. the transport header. By the definition applied in the problem
statement all ipv6 capable routers in the internet that  I'm aware are or
are capable of being middleboxes. =


I would welcome the existence proof of an ipv6 capable router which is
not capable of being a middlebox by the definition applied in the problem
statement.

I'm not sure that's a glaring flaw in the document but it certainly is
with our vocabulary around taxonomy if true.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

If you need to find the transport header due to configured policy and you
can't due to being unable to parse the extensions chain your configured
action will be to drop. That perhaps weasels it's way through section 2.1
requirements but it's still quite ugly.



From stephen.farrell@cs.tcd.ie  Tue Oct  8 03:31:12 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55F2021E81A9; Tue,  8 Oct 2013 03:31:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ol6qVA9KNGPA; Tue,  8 Oct 2013 03:31:11 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B56221E81C7; Tue,  8 Oct 2013 03:31:11 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
To: The IESG <iesg@ietf.org>
Subject: Stephen Farrell's No Objection on draft-ietf-6man-ext-transmit-04: (with COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131008103111.25649.95882.idtracker@ietfa.amsl.com>
Date: Tue, 08 Oct 2013 03:31:11 -0700
Cc: 6man-chairs@tools.ietf.org, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Oct 2013 10:31:12 -0000

Stephen Farrell has entered the following ballot position for
draft-ietf-6man-ext-transmit-04: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-6man-ext-transmit/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------


- 2.1 says nodes SHOULD forward rfc4727 experimental
headers, but earlier said that its ok (nodes MAY) default
to not forwarding packets with experimental headers. I
think you need to add an "unless otherwise stated here"
to the statement about defaults for experimental headers.

- section 4: Is it wise to ask IANA to "redirect" users
from one (empty) registry to another? That could be the
start of a slippery slope turning IANA registries into a
miasma of hypertext;-) Maybe it'd be better to ask that
IANA mark that registry as having being replaced by this
new one. Also - what if someone else asks IANA to add an
entry to the currently empty registry but not the new one
- is it clear what should happen in that case?



From Fred.L.Templin@boeing.com  Tue Oct  8 08:29:12 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BF0321E80F0; Tue,  8 Oct 2013 08:29:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oB+e-sin+Nx9; Tue,  8 Oct 2013 08:29:06 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) by ietfa.amsl.com (Postfix) with ESMTP id 6FC6721E80AC; Tue,  8 Oct 2013 08:28:56 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r98FStlG011151; Tue, 8 Oct 2013 10:28:55 -0500
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r98FSrpP010698 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 8 Oct 2013 10:28:54 -0500
Received: from XCH-BLV-502.nw.nos.boeing.com (130.247.25.191) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Tue, 8 Oct 2013 08:28:53 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.29]) by XCH-BLV-502.nw.nos.boeing.com ([169.254.2.118]) with mapi id 14.02.0328.011; Tue, 8 Oct 2013 08:28:53 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "C. M. Heard" <heard@pobox.com>
Subject: RE: Adrian Farrel's No Objection on draft-ietf-6man-ext-transmit-04:	(with COMMENT)
Thread-Topic: Adrian Farrel's No Objection on draft-ietf-6man-ext-transmit-04:	(with COMMENT)
Thread-Index: AQHOw7v2kD1BJLnfPEa6uJw0JWHTepnq7I1w
Date: Tue, 8 Oct 2013 15:28:52 +0000
Message-ID: <2134F8430051B64F815C691A62D9831811DA86@XCH-BLV-504.nw.nos.boeing.com>
References: <20131007144327.16131.88173.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1310070914240.13173@shell4.bayarea.net> <52530921.3060202@gmail.com> <Pine.LNX.4.64.1310071315370.13828@shell4.bayarea.net> <52534F31.2020906@gmail.com>
In-Reply-To: <52534F31.2020906@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Adrian Farrel <adrian@olddog.co.uk>, "draft-ietf-6man-ext-transmit@tools.ietf.org" <draft-ietf-6man-ext-transmit@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, The IESG <iesg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Oct 2013 15:29:12 -0000

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> Brian E Carpenter
> Sent: Monday, October 07, 2013 5:18 PM
> To: C. M. Heard
> Cc: 6man-chairs@tools.ietf.org; Adrian Farrel; draft-ietf-6man-ext-
> transmit@tools.ietf.org; ipv6@ietf.org; The IESG
> Subject: Re: Adrian Farrel's No Objection on draft-ietf-6man-ext-
> transmit-04: (with COMMENT)
>=20
> On 08/10/2013 10:28, C. M. Heard wrote:
> ...
>=20
> > Maybe I'm making too much of this.  Certainly a reasonable action
> > for a middlebox that's told to pass packets with extension header
> > types 253 and 254 is to stop parsing when it encounters those next
> > header types and forward the packet in question.  Maybe that's
> > obvious to everyone -- but it seems to me that the spec, as written,
> > is actually asking for something different.
>=20
> There's no header length field in an IPv6 header. That means that
> since header types 253 and 254 might be used either for experimental
> extension headers or for experimental payload types, there's no
> generic way for a middlebox to tell the difference. I think that's
> an issue that the current draft cannot resolve. I suspect we probably
> need an extra sentence to state the problem, but the authors will
> wait for direction on that.

When Wireshark encounters a header type 253 or 254, it assumes it is
an unknown extension header of length 8 bytes, then skips ahead and
attempts to parse anything that follows as additional headers.

Wireshark can be thought of as a middlebox of sorts (albeit one
that does not alter the traffic flow), and it wouldn't be hard to
imagine real middleboxes that do the same thing when they encounter
253/254.

Thanks - Fred
fred.l.templin@boeing.com
=20
>     Brian
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

From shwethab@cisco.com  Fri Oct  4 18:36:18 2013
Return-Path: <shwethab@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7F0521F9DB4; Fri,  4 Oct 2013 18:36:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IAXZN7dwT8AH; Fri,  4 Oct 2013 18:36:10 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 3839221F9DBD; Fri,  4 Oct 2013 18:36:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2722; q=dns/txt; s=iport; t=1380936967; x=1382146567; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=B7nS6RudhWWzlr3FyQ2N+G3K+0RRxWioiDsm+/3khIk=; b=ehI9TiJol6KKzx7hUDa5fQYauRy7KrisUGXddN2g9oT7TvTWFUwT4iCE kOBbggPp5PzBvlu3r8aKbeBV+U1IJTFwU5loCGCBxmFH1cMG30IBd2S7S tWIn5lHNeWtX/bAY2RgEDQBfJiOFVukLKo2pArk94zExGc/g4wVxt7UHJ I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjgFAFZsT1KtJV2Z/2dsb2JhbABZgwc4UsBXSoEWFnSCJQEBAQMBAQEBNzQQDQEIIhQ3CyUCBAESCId4Bgy8OQSPIDiDH4EEA6oAgySCKg
X-IronPort-AV: E=Sophos;i="4.90,1037,1371081600"; d="scan'208";a="268338955"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-7.cisco.com with ESMTP; 05 Oct 2013 01:36:06 +0000
Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r951a6al008098 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 5 Oct 2013 01:36:06 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.47]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.02.0318.004; Fri, 4 Oct 2013 20:36:06 -0500
From: "Shwetha Bhandari (shwethab)" <shwethab@cisco.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, "ipv6@ietf.org" <ipv6@ietf.org>, homenet <homenet@ietf.org>
Subject: Re: [homenet] draft-lepape-6man-prefix-metadata-00
Thread-Topic: [homenet] draft-lepape-6man-prefix-metadata-00
Thread-Index: AQHOue78VAvHfq2MDkilZ8/+bcdu3pnmEq+A
Date: Sat, 5 Oct 2013 01:36:06 +0000
Message-ID: <D760207426D56242BAF68F47647CF1071F38EE60@xmb-rcd-x04.cisco.com>
In-Reply-To: <6253.1380113890@sandelman.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.0.0.100825
x-originating-ip: [10.65.79.169]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9B26338F332B92479712A020AA398C71@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 08 Oct 2013 08:53:34 -0700
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 05 Oct 2013 01:36:19 -0000

Hi Michael,

Thanks for the review, please find comments inline @SB

On 9/25/13 6:28 PM, "Michael Richardson" <mcr+ietf@sandelman.ca> wrote:

>
>I think that this draft is useful land should be adopted.
>
>I think that application writers will be much happier asking for prefix
>colours than properties, if there is a clear set of default colours.
>I am concerned that there is an attempt to be too indirect, the way that
>DiffServ tried with DSCP, and yet nearly only code point is really
>supported
>for EF on real networks, so the point where application writers tend to
>embed it, at least at the documentation layer.
>
>section 3.3 talks about:
>
>   Once an application has determined the appropriate property **and**
>color
>   for its use it has to communicate with the network stack to select
>
>and I thought up to this point that one could select by colour, or by
>property.

[SB] you are right about colour OR property for selection. Will fix the
wording in the draft.




>  While it's true that the host interface is host specific, for this
>to work, someone needs to publish a reference implementation for
>Android/Java
>and Linux/C/Python...


[SB] There is an implementation for Android Section A.1.5
draft-lepape-6man-prefix-metadata-00#appendix-A.1.5 has the details.


>
>Suggesting three different userspace/kernel methods isn't going to help
>get
>applications written. APIs matter here.  Being able to set a default
>colour
>for a process (and it's children!!) is probably the initial killer
>interface,
>because I can now do something like:
>        low-latency-colour skype &
>where the command "low-latency-colour" sets the default colour and then
>invokes another command.
>
>3.5 I believe that local scoping of prefix color is going to be useless.
>The prefix colour is a proxy for which ISP/servie, so making it ISP scoped
>makes it useless for the application.
>
>Instead, I suggest that the prefix colour either be a global IANA registry
>(DS PHB may already be the right thing...),or make it a uuid.  Then
>T-mobile
>can embed their network prefix colour for video in the video player app
>that
>they want to shove into my phone...


[SB] Yes, UUID to attach e.g. ISP's enterprise ID or using access network
identifier
information along with the locally scoped colour for selection would
provide flexibility while a global registry may be suitable for the
properties.


Thanks,
Shwetha


>
>--
>Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>
>
>_______________________________________________
>homenet mailing list
>homenet@ietf.org
>https://www.ietf.org/mailman/listinfo/homenet


From rlb@ipv.sx  Tue Oct  8 08:44:02 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6375621E81C6; Tue,  8 Oct 2013 08:44:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x+TcaexJ9CK7; Tue,  8 Oct 2013 08:44:01 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EAE3721E81C0; Tue,  8 Oct 2013 08:44:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: "Richard Barnes" <rlb@ipv.sx>
To: The IESG <iesg@ietf.org>
Subject: Richard Barnes' No Objection on draft-ietf-6man-ext-transmit-04: (with COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131008154401.25649.85053.idtracker@ietfa.amsl.com>
Date: Tue, 08 Oct 2013 08:44:01 -0700
X-Mailman-Approved-At: Tue, 08 Oct 2013 08:53:34 -0700
Cc: 6man-chairs@tools.ietf.org, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Oct 2013 15:44:02 -0000

Richard Barnes has entered the following ballot position for
draft-ietf-6man-ext-transmit-04: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-6man-ext-transmit/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Could you provide any citations on the middle box behaviors, e.g., lack
of support for all of 2460?

10 points to the INT area for the cite to Heller :)

"... Not just a failure to recognize such a header".  =

Isn't this another Catch-22?  If a node doesn't recognize a header, how
does it know if it's standard or not?  This also seems in contradiction
to later guidance that unrecognized extensions may be dropped by
default.

A flow chart or pseudo code might be useful in Section 2.1, like "if
(known && standard) { /* policy */ }"



From otroan@employees.org  Tue Oct  8 10:35:29 2013
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB79221E8271; Tue,  8 Oct 2013 10:35:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qi3qBnT55re9; Tue,  8 Oct 2013 10:35:29 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) by ietfa.amsl.com (Postfix) with ESMTP id 6B30D21E8213; Tue,  8 Oct 2013 10:35:29 -0700 (PDT)
Received: from dhcp-10-61-105-20.cisco.com (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 5B50C5FF8; Tue,  8 Oct 2013 10:35:28 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_4799F997-C3FE-4A9C-8293-DC74B62CF3B2"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
From: Ole Troan <otroan@employees.org>
In-Reply-To: <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com>
Date: Tue, 8 Oct 2013 18:16:30 +0200
Message-Id: <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.1510)
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Oct 2013 17:35:29 -0000

--Apple-Mail=_4799F997-C3FE-4A9C-8293-DC74B62CF3B2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Fred,

> Hi, I would like to make a small amendment to what I said in my
> previous message as follows:
>=20
> 4) Section 5, change the final paragraph to:
>=20
>   "As a result of the above mentioned requirements, a packet's header
>   chain length MUST fit within the Path MTU associated with its
>   destination.  Hosts MAY discover the Path MTU, using procedures such
>   as those defined in [RFC1981] and [RFC4821]. However, if a host does
>   not discover the Path MTU, it MUST assume the IPv6 minumum MTU of
>   1280 bytes [RFC2460]. The host MUST then limit each packet's header
>   chain length to the Path MTU minus 256 bytes in case additional
>   encapsulation headers are inserted by tunnels on the path."

I would claim that additional encapsulation headers are already =
considered in the 1280 minimum MTU.
as in: 1500 - 1280.

cheers,
Ole


--Apple-Mail=_4799F997-C3FE-4A9C-8293-DC74B62CF3B2
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

iQEcBAEBCgAGBQJSVC/eAAoJEFuJXizso86gh94H/jJKuujErKuYtUuNt+76rscy
wcx5MwBLGTEOhwGmZxhmScKtruLrcjH96v+bmaBKMGXsga+37lyJWd45TB2EeAU2
bePszxUXpStZfSvoFHWhEV424N6IDU8AAq5snbmakWKBwMBYeMxO/hWgf24OazSi
Sn4R62UiJvF8jePMSaiIcGCPFJN+oQGjZB9oh3Eb48+vsSsJ4oC6iIG0idn0AIrB
G79FTpELYujBoam01SUromjpuJuwkHog1MZXySskKIIauFtoh2XuBLeNcH3pklLX
5HLELg78n2oKnswXDj6m2ziB5e10rNHUeUDwRhfIbmQOpOTeQBYA/QWhQ28To4M=
=6pim
-----END PGP SIGNATURE-----

--Apple-Mail=_4799F997-C3FE-4A9C-8293-DC74B62CF3B2--

From Fred.L.Templin@boeing.com  Tue Oct  8 11:34:06 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF1F121E828A; Tue,  8 Oct 2013 11:34:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yghdhBE3N+Mk; Tue,  8 Oct 2013 11:34:00 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (stl-mbsout-01.boeing.com [130.76.96.169]) by ietfa.amsl.com (Postfix) with ESMTP id 3810E21E8278; Tue,  8 Oct 2013 11:34:00 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r98IXxgR008418; Tue, 8 Oct 2013 13:33:59 -0500
Received: from XCH-NWHT-06.nw.nos.boeing.com (xch-nwht-06.nw.nos.boeing.com [130.247.25.110]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r98IXwhd008382 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 8 Oct 2013 13:33:59 -0500
Received: from XCH-BLV-306.nw.nos.boeing.com (130.247.25.218) by XCH-NWHT-06.nw.nos.boeing.com (130.247.25.110) with Microsoft SMTP Server (TLS) id 8.3.327.1; Tue, 8 Oct 2013 11:33:58 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.29]) by XCH-BLV-306.nw.nos.boeing.com ([169.254.6.159]) with mapi id 14.02.0328.011; Tue, 8 Oct 2013 11:33:58 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ole Troan <otroan@employees.org>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOxEzPebc9KTehbEGO6mhunuAlj5nrHdCQ
Date: Tue, 8 Oct 2013 18:33:57 +0000
Message-ID: <2134F8430051B64F815C691A62D9831811DF44@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org>
In-Reply-To: <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Oct 2013 18:34:06 -0000

Hi Ole,

> -----Original Message-----
> From: Ole Troan [mailto:otroan@employees.org]
> Sent: Tuesday, October 08, 2013 9:17 AM
> To: Templin, Fred L
> Cc: ietf@ietf.org; IETF-Announce; ipv6@ietf.org
> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> Fred,
>=20
> > Hi, I would like to make a small amendment to what I said in my
> > previous message as follows:
> >
> > 4) Section 5, change the final paragraph to:
> >
> >   "As a result of the above mentioned requirements, a packet's header
> >   chain length MUST fit within the Path MTU associated with its
> >   destination.  Hosts MAY discover the Path MTU, using procedures
> such
> >   as those defined in [RFC1981] and [RFC4821]. However, if a host
> does
> >   not discover the Path MTU, it MUST assume the IPv6 minumum MTU of
> >   1280 bytes [RFC2460]. The host MUST then limit each packet's header
> >   chain length to the Path MTU minus 256 bytes in case additional
> >   encapsulation headers are inserted by tunnels on the path."
>=20
> I would claim that additional encapsulation headers are already
> considered in the 1280 minimum MTU.
> as in: 1500 - 1280.

It is kind of like that, but what I am concerned about is tunnels
in the path that fragment either because they cannot meet the IPv6
minimum MTU without doing so, or because they are trying to allow
a larger-sized MTU when the path doesn't support it due to the
addition of the encapsulating headers.

Take the simplest case when the host assumes a path MTU of 1280.
If there is a tunnel in the path that crosses another 1280 link,
then the tunnel has to fragment, and the header chain might not
all fit within the first fragment if the host does not allow
headspace room. If the host limits the size of its header chain
to 1280 - 512 =3D 1024 bytes, then the entire chain should fit
within the first fragment even if there are multiple nested
tunnel ingresses on the path and each one of them fragments.

That said, I am wondering how this document relates to the
discussions we had earlier and the resulting draft from Mark
Andrews on what to do when the header chain spans multiple
fragments? Are we trying to keep the header chain all within
the first fragment or not?

Thanks - Fred
fred.l.templin@boeing.com

> cheers,
> Ole


From fernando@gont.com.ar  Tue Oct  8 11:52:12 2013
Return-Path: <fernando@gont.com.ar>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBD4111E80F2; Tue,  8 Oct 2013 11:52:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7zOdMnHMnVcQ; Tue,  8 Oct 2013 11:52:11 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 6E1F711E80D9; Tue,  8 Oct 2013 11:52:11 -0700 (PDT)
Received: from 17-153-16-190.fibertel.com.ar ([190.16.153.17] helo=[192.168.1.101]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fernando@gont.com.ar>) id 1VTcNz-0007lz-Jg; Tue, 08 Oct 2013 20:52:02 +0200
Message-ID: <52545449.2020701@gont.com.ar>
Date: Tue, 08 Oct 2013 15:51:53 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>,  Ole Troan <otroan@employees.org>
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com>	<2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com>	<2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com>	<9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <2134F8430051B64F815C691A62D9831811DF44@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831811DF44@XCH-BLV-504.nw.nos.boeing.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Oct 2013 18:52:13 -0000

Hi, Fred,

Thanks so much for your feedback! -- Please find my comments in-line...

On 10/08/2013 03:33 PM, Templin, Fred L wrote:
>> I would claim that additional encapsulation headers are already
>> considered in the 1280 minimum MTU.
>> as in: 1500 - 1280.
> 
> It is kind of like that, but what I am concerned about is tunnels
> in the path that fragment either because they cannot meet the IPv6
> minimum MTU without doing so, or because they are trying to allow
> a larger-sized MTU when the path doesn't support it due to the
> addition of the encapsulating headers.
> 
> Take the simplest case when the host assumes a path MTU of 1280.
> If there is a tunnel in the path that crosses another 1280 link,
> then the tunnel has to fragment, 

Well, at least in theory, the tunnel could do Path-MTU... In which case,
if the underlying MTU is of, say, 1500 bytes, then you can probably go
through several layers of encapsulation, without problem.

Besides, while one would probably would nto phrase it like this, truth
is that even 512 f headers would be pretty much non-sensical: Headers
are overhead. So at the point in which you have 50$ of overhead in every
single packet, it starts looking that the inforation is probably being
conveyed in thr wrong place.

That is, in the real world, you would not even get to 1K headers even
ater several layers of encapsulation.


> That said, I am wondering how this document relates to the
> discussions we had earlier and the resulting draft from Mark
> Andrews on what to do when the header chain spans multiple
> fragments? Are we trying to keep the header chain all within
> the first fragment or not?

Yes.

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 brian.e.carpenter@gmail.com  Tue Oct  8 12:07:22 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3498821F9473; Tue,  8 Oct 2013 12:07:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.527
X-Spam-Level: 
X-Spam-Status: No, score=-102.527 tagged_above=-999 required=5 tests=[AWL=0.072, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oNPtUNgPzgx9; Tue,  8 Oct 2013 12:07:21 -0700 (PDT)
Received: from mail-pb0-x22b.google.com (mail-pb0-x22b.google.com [IPv6:2607:f8b0:400e:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id E78E521F9AFE; Tue,  8 Oct 2013 12:06:47 -0700 (PDT)
Received: by mail-pb0-f43.google.com with SMTP id md4so9023522pbc.16 for <multiple recipients>; Tue, 08 Oct 2013 12:06:47 -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=45dpDwva0YrLT7XMTnkZtIQKB+XNRReREchgUgTH514=; b=to37PzcdN9MeZneFYef2iEGn5WHqY6Ae9WK49rukzMWRWp2Ua4Kr8ok//1+TRlTPtC U7vC86KpeBvgHOQs5fcy65IgX0A+b8cl346/k3TsswosII8sV4UJyrxBOTJ0k1rc38mJ evdeWgLu3QFkg3pBPELDaYW/Yq2LuG6kBTaplILJOxlXGMGoO4f9UfkdjsB+JFF4E1HW mfbUFhPI8hS69AwYOGhpeVsT0+fXxEaO27CB7o2/5OQAZ2Ch4mbvSNWtlGxeNaHKZM4I naqubwWBRD8m+V6+EL5b3YEMX8WITOGsO3oqGed71mypoYNP+Hws8YTfpc0zvqZ4aFVs VNTA==
X-Received: by 10.66.149.73 with SMTP id ty9mr5263170pab.36.1381259207641; Tue, 08 Oct 2013 12:06:47 -0700 (PDT)
Received: from [192.168.178.20] (157.202.69.111.dynamic.snap.net.nz. [111.69.202.157]) by mx.google.com with ESMTPSA id xs1sm49249539pac.7.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 08 Oct 2013 12:06:46 -0700 (PDT)
Message-ID: <525457C1.5030503@gmail.com>
Date: Wed, 09 Oct 2013 08:06: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: Joel Jaeggli <joelja@bogus.com>
Subject: Re: Joel Jaeggli's Discuss on draft-ietf-6man-ext-transmit-04: (with DISCUSS and COMMENT)
References: <20131008071948.25649.48005.idtracker@ietfa.amsl.com>
In-Reply-To: <20131008071948.25649.48005.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 6man-chairs@tools.ietf.org, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org, The IESG <iesg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Oct 2013 19:07:22 -0000

On 08/10/2013 20:19, Joel Jaeggli wrote:
...
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
> This is a dicuss because I'd like to see if I'm in the rough in this.
> 
> Devices generally considered to be IP routers in fact are able to or find
> it necessary to forward on the basis of headers other than the IP header
> e.g. the transport header. By the definition applied in the problem
> statement all ipv6 capable routers in the internet that  I'm aware are or
> are capable of being middleboxes. 

IMHO, yes, if a box is taking a forwarding decision on the basis of anything
other than the first 40 bytes of an IPv6 header, then it's a middlebox
as far as this draft is concerned. Any such box is not a "straightforward IP
router".

In the process of working on the draft I have actually corresponded briefly
with Steve Deering, and I'm pretty sure he would agree with me (with
added expletives).

> I would welcome the existence proof of an ipv6 capable router which is
> not capable of being a middlebox by the definition applied in the problem
> statement.
> 
> I'm not sure that's a glaring flaw in the document but it certainly is
> with our vocabulary around taxonomy if true.
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> If you need to find the transport header due to configured policy and you
> can't due to being unable to parse the extensions chain your configured
> action will be to drop. That perhaps weasels it's way through section 2.1
> requirements but it's still quite ugly.

Yes, and it's the reason that the Internet is mainly opaque to IPv6
extensions headers today.

    Brian

From joelja@bogus.com  Tue Oct  8 12:22:10 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 487EF21F9E89; Tue,  8 Oct 2013 12:22:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CZ85-u6Q+BpG; Tue,  8 Oct 2013 12:22:09 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id D87F421F9E99; Tue,  8 Oct 2013 12:22:08 -0700 (PDT)
Received: from mb-aye.corp.zynga.com ([199.48.105.4]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r98JM4ug020442 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 8 Oct 2013 19:22:05 GMT (envelope-from joelja@bogus.com)
Content-Type: multipart/signed; boundary="Apple-Mail=_D1C7F777-5FB4-4D31-A3BF-86A6B645F4E6"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Joel Jaeggli's Discuss on draft-ietf-6man-ext-transmit-04: (with DISCUSS and COMMENT)
From: joel jaeggli <joelja@bogus.com>
In-Reply-To: <525457C1.5030503@gmail.com>
Date: Tue, 8 Oct 2013 12:22:05 -0700
Message-Id: <E93EBFCB-54C3-44D3-8126-8439AD15046E@bogus.com>
References: <20131008071948.25649.48005.idtracker@ietfa.amsl.com> <525457C1.5030503@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1510)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 08 Oct 2013 19:22:05 +0000 (UTC)
Cc: 6man-chairs@tools.ietf.org, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org, The IESG <iesg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Oct 2013 19:22:10 -0000

--Apple-Mail=_D1C7F777-5FB4-4D31-A3BF-86A6B645F4E6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Oct 8, 2013, at 12:06 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

> On 08/10/2013 20:19, Joel Jaeggli wrote:
> ...
>> =
----------------------------------------------------------------------
>> DISCUSS:
>> =
----------------------------------------------------------------------
>>=20
>> This is a dicuss because I'd like to see if I'm in the rough in this.
>>=20
>> Devices generally considered to be IP routers in fact are able to or =
find
>> it necessary to forward on the basis of headers other than the IP =
header
>> e.g. the transport header. By the definition applied in the problem
>> statement all ipv6 capable routers in the internet that  I'm aware =
are or
>> are capable of being middleboxes.=20
>=20
> IMHO, yes, if a box is taking a forwarding decision on the basis of =
anything
> other than the first 40 bytes of an IPv6 header, then it's a middlebox
> as far as this draft is concerned. Any such box is not a =
"straightforward IP
> router".
>=20
> In the process of working on the draft I have actually corresponded =
briefly
> with Steve Deering, and I'm pretty sure he would agree with me (with
> added expletives).

Right, so there are no IP routers on the internet today and you should =
update the document accordingly because as it stands now it seems to =
presume their existence.

>=20
>> I would welcome the existence proof of an ipv6 capable router which =
is
>> not capable of being a middlebox by the definition applied in the =
problem
>> statement.
>>=20
>> I'm not sure that's a glaring flaw in the document but it certainly =
is
>> with our vocabulary around taxonomy if true.
>>=20
>>=20
>> =
----------------------------------------------------------------------
>> COMMENT:
>> =
----------------------------------------------------------------------
>>=20
>> If you need to find the transport header due to configured policy and =
you
>> can't due to being unable to parse the extensions chain your =
configured
>> action will be to drop. That perhaps weasels it's way through section =
2.1
>> requirements but it's still quite ugly.
>=20
> Yes, and it's the reason that the Internet is mainly opaque to IPv6
> extensions headers today.
>=20
>    Brian
>=20


--Apple-Mail=_D1C7F777-5FB4-4D31-A3BF-86A6B645F4E6
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 - http://gpgtools.org

iEYEARECAAYFAlJUW10ACgkQ8AA1q7Z/VrJNFACfTuLkK3ZTMYs7CzxMmTa0w16S
ziwAnRQdDMS8sKDYV+Ti0qoOfGq68ga7
=mv0X
-----END PGP SIGNATURE-----

--Apple-Mail=_D1C7F777-5FB4-4D31-A3BF-86A6B645F4E6--

From brian.e.carpenter@gmail.com  Tue Oct  8 12:45:41 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEF3F21F936F; Tue,  8 Oct 2013 12:45:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.531
X-Spam-Level: 
X-Spam-Status: No, score=-102.531 tagged_above=-999 required=5 tests=[AWL=0.068, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id usE3oWiv84Zn; Tue,  8 Oct 2013 12:45:36 -0700 (PDT)
Received: from mail-pb0-x231.google.com (mail-pb0-x231.google.com [IPv6:2607:f8b0:400e:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 8772721F9CC0; Tue,  8 Oct 2013 12:45:19 -0700 (PDT)
Received: by mail-pb0-f49.google.com with SMTP id xb4so9075511pbc.36 for <multiple recipients>; Tue, 08 Oct 2013 12:45:19 -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=loqLpYL5xELDMUrxWABRQAB09KWU3s79F+AxisiXnhI=; b=BjdQm5/tTuJqpW0oZTHhRwyxaST703B0xrIpQhmdKMC3gmUNkd+qmJRoJIYUK/iUli O5OfhEwf1oAn1vYgI8k+B9ea7xSPcNJ0jMtOmWKsz3JeTyVPSbM1pypTR87wN7YjcsZp DrexU/0Ya+OZCjHOPL6LFtfB2au69vP12vdakME5F3L0GwSPDLCSHX0MiZyi9Md0fvN3 OnWcScxEZTBAZyTVrwacS5hIWhxal/HbwmiQBflkpWs0744rtSbDsYWb0REtFV+86p7v G2OWDsMM51uHvhu9r6b6tas2MQqL0/cSAdP1pC7yJ58wjGQBE+MMTH+0H/WGbv9UYKoo wVYA==
X-Received: by 10.67.5.132 with SMTP id cm4mr4042790pad.186.1381261519126; Tue, 08 Oct 2013 12:45:19 -0700 (PDT)
Received: from [192.168.178.20] (157.202.69.111.dynamic.snap.net.nz. [111.69.202.157]) by mx.google.com with ESMTPSA id qf7sm49379544pac.14.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 08 Oct 2013 12:45:18 -0700 (PDT)
Message-ID: <525460CF.108@gmail.com>
Date: Wed, 09 Oct 2013 08:45: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: joel jaeggli <joelja@bogus.com>
Subject: Re: Joel Jaeggli's Discuss on draft-ietf-6man-ext-transmit-04: (with DISCUSS and COMMENT)
References: <20131008071948.25649.48005.idtracker@ietfa.amsl.com> <525457C1.5030503@gmail.com> <E93EBFCB-54C3-44D3-8126-8439AD15046E@bogus.com>
In-Reply-To: <E93EBFCB-54C3-44D3-8126-8439AD15046E@bogus.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 6man-chairs@tools.ietf.org, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org, The IESG <iesg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Oct 2013 19:45:41 -0000

Joel,

Would this help?

OLD
   Today, packets are often forwarded not only by straightforward IP
   routers, but also by a variety of intermediate nodes, often referred
   to as middleboxes, such as firewalls, load balancers, or packet
   classifiers.

NEW
   Today, IPv6 packets are often forwarded not only on the basis of their
   first 40 bytes by straightforward IP routing. Some routers, and a
   variety of intermediate nodes often referred to as middleboxes, such
   as firewalls, load balancers, or packet classifiers, inspect other
   parts of each packet.

(and possibly some changes for consistency later in the document)

    Brian


On 09/10/2013 08:22, joel jaeggli wrote:
> On Oct 8, 2013, at 12:06 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
>> On 08/10/2013 20:19, Joel Jaeggli wrote:
>> ...
>>> ----------------------------------------------------------------------
>>> DISCUSS:
>>> ----------------------------------------------------------------------
>>>
>>> This is a dicuss because I'd like to see if I'm in the rough in this.
>>>
>>> Devices generally considered to be IP routers in fact are able to or find
>>> it necessary to forward on the basis of headers other than the IP header
>>> e.g. the transport header. By the definition applied in the problem
>>> statement all ipv6 capable routers in the internet that  I'm aware are or
>>> are capable of being middleboxes. 
>> IMHO, yes, if a box is taking a forwarding decision on the basis of anything
>> other than the first 40 bytes of an IPv6 header, then it's a middlebox
>> as far as this draft is concerned. Any such box is not a "straightforward IP
>> router".
>>
>> In the process of working on the draft I have actually corresponded briefly
>> with Steve Deering, and I'm pretty sure he would agree with me (with
>> added expletives).
> 
> Right, so there are no IP routers on the internet today and you should update the document accordingly because as it stands now it seems to presume their existence.
> 
>>> I would welcome the existence proof of an ipv6 capable router which is
>>> not capable of being a middlebox by the definition applied in the problem
>>> statement.
>>>
>>> I'm not sure that's a glaring flaw in the document but it certainly is
>>> with our vocabulary around taxonomy if true.
>>>
>>>
>>> ----------------------------------------------------------------------
>>> COMMENT:
>>> ----------------------------------------------------------------------
>>>
>>> If you need to find the transport header due to configured policy and you
>>> can't due to being unable to parse the extensions chain your configured
>>> action will be to drop. That perhaps weasels it's way through section 2.1
>>> requirements but it's still quite ugly.
>> Yes, and it's the reason that the Internet is mainly opaque to IPv6
>> extensions headers today.
>>
>>    Brian
>>
> 

From joelja@bogus.com  Tue Oct  8 13:07:35 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3D5821F93E4; Tue,  8 Oct 2013 13:07:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M3m4pj+o87Yu; Tue,  8 Oct 2013 13:07:35 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 15ADF21F9FB6; Tue,  8 Oct 2013 13:07:34 -0700 (PDT)
Received: from mb-aye.corp.zynga.com ([199.48.105.4]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r98K7VE7020942 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 8 Oct 2013 20:07:31 GMT (envelope-from joelja@bogus.com)
Content-Type: multipart/signed; boundary="Apple-Mail=_1D45D010-A15C-4CF2-AC02-854B5E4E5CED"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Joel Jaeggli's Discuss on draft-ietf-6man-ext-transmit-04: (with DISCUSS and COMMENT)
From: joel jaeggli <joelja@bogus.com>
In-Reply-To: <525460CF.108@gmail.com>
Date: Tue, 8 Oct 2013 13:07:27 -0700
Message-Id: <21DD9C6E-287F-4D18-B3F5-3FE01C5351E5@bogus.com>
References: <20131008071948.25649.48005.idtracker@ietfa.amsl.com> <525457C1.5030503@gmail.com> <E93EBFCB-54C3-44D3-8126-8439AD15046E@bogus.com> <525460CF.108@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1510)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 08 Oct 2013 20:07:32 +0000 (UTC)
Cc: 6man-chairs@tools.ietf.org, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org, The IESG <iesg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Oct 2013 20:07:36 -0000

--Apple-Mail=_1D45D010-A15C-4CF2-AC02-854B5E4E5CED
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Oct 8, 2013, at 12:45 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

> Joel,
>=20
> Would this help?
>=20
> OLD
>   Today, packets are often forwarded not only by straightforward IP
>   routers, but also by a variety of intermediate nodes, often referred
>   to as middleboxes, such as firewalls, load balancers, or packet
>   classifiers.
>=20
> NEW
>   Today, IPv6 packets are often forwarded not only on the basis of =
their
>   first 40 bytes by straightforward IP routing. Some routers, and a
>   variety of intermediate nodes often referred to as middleboxes, such
>   as firewalls, load balancers, or packet classifiers, inspect other
>   parts of each packet.
>=20

I find that more palatable yeah.

> (and possibly some changes for consistency later in the document)
>=20
>    Brian
>=20
>=20
> On 09/10/2013 08:22, joel jaeggli wrote:
>> On Oct 8, 2013, at 12:06 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>>=20
>>> On 08/10/2013 20:19, Joel Jaeggli wrote:
>>> ...
>>>> =
----------------------------------------------------------------------
>>>> DISCUSS:
>>>> =
----------------------------------------------------------------------
>>>>=20
>>>> This is a dicuss because I'd like to see if I'm in the rough in =
this.
>>>>=20
>>>> Devices generally considered to be IP routers in fact are able to =
or find
>>>> it necessary to forward on the basis of headers other than the IP =
header
>>>> e.g. the transport header. By the definition applied in the problem
>>>> statement all ipv6 capable routers in the internet that  I'm aware =
are or
>>>> are capable of being middleboxes.=20
>>> IMHO, yes, if a box is taking a forwarding decision on the basis of =
anything
>>> other than the first 40 bytes of an IPv6 header, then it's a =
middlebox
>>> as far as this draft is concerned. Any such box is not a =
"straightforward IP
>>> router".
>>>=20
>>> In the process of working on the draft I have actually corresponded =
briefly
>>> with Steve Deering, and I'm pretty sure he would agree with me (with
>>> added expletives).
>>=20
>> Right, so there are no IP routers on the internet today and you =
should update the document accordingly because as it stands now it seems =
to presume their existence.
>>=20
>>>> I would welcome the existence proof of an ipv6 capable router which =
is
>>>> not capable of being a middlebox by the definition applied in the =
problem
>>>> statement.
>>>>=20
>>>> I'm not sure that's a glaring flaw in the document but it certainly =
is
>>>> with our vocabulary around taxonomy if true.
>>>>=20
>>>>=20
>>>> =
----------------------------------------------------------------------
>>>> COMMENT:
>>>> =
----------------------------------------------------------------------
>>>>=20
>>>> If you need to find the transport header due to configured policy =
and you
>>>> can't due to being unable to parse the extensions chain your =
configured
>>>> action will be to drop. That perhaps weasels it's way through =
section 2.1
>>>> requirements but it's still quite ugly.
>>> Yes, and it's the reason that the Internet is mainly opaque to IPv6
>>> extensions headers today.
>>>=20
>>>   Brian
>>>=20
>>=20
>=20


--Apple-Mail=_1D45D010-A15C-4CF2-AC02-854B5E4E5CED
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 - http://gpgtools.org

iEYEARECAAYFAlJUZf8ACgkQ8AA1q7Z/VrIXlwCggMBDrB/U3bBTl+o0MY3ubl/p
HtUAnifTfbDLtaArah1UNGvoq/SEwjxz
=WFzY
-----END PGP SIGNATURE-----

--Apple-Mail=_1D45D010-A15C-4CF2-AC02-854B5E4E5CED--

From roland.bless@kit.edu  Tue Oct  8 14:09:01 2013
Return-Path: <roland.bless@kit.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4961321F9E63 for <ipv6@ietfa.amsl.com>; Tue,  8 Oct 2013 14:09:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dXCmHVpOa7qH for <ipv6@ietfa.amsl.com>; Tue,  8 Oct 2013 14:08:55 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) by ietfa.amsl.com (Postfix) with ESMTP id E378821F9C7B for <ipv6@ietf.org>; Tue,  8 Oct 2013 14:08:53 -0700 (PDT)
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5]) by iramx2.ira.uni-karlsruhe.de with esmtps port 25  id 1VTeWM-0005Rr-U7; Tue, 08 Oct 2013 23:08:48 +0200
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=vorta.tm.kit.edu) by irams1.ira.uni-karlsruhe.de with esmtp port 25  id 1VTeWQ-0006QS-Le; Tue, 08 Oct 2013 23:08:50 +0200
Received: from [IPv6:::1] (localhost [127.0.0.1]) by vorta.tm.kit.edu (Postfix) with ESMTPS id 6ADB5A80700; Tue,  8 Oct 2013 23:08:50 +0200 (CEST)
Message-ID: <52547462.5010309@kit.edu>
Date: Tue, 08 Oct 2013 23:08:50 +0200
From: Roland Bless <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology (KIT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Joel Jaeggli's Discuss on draft-ietf-6man-ext-transmit-04: (with DISCUSS and COMMENT)
References: <20131008071948.25649.48005.idtracker@ietfa.amsl.com>	<525457C1.5030503@gmail.com>	<E93EBFCB-54C3-44D3-8126-8439AD15046E@bogus.com> <525460CF.108@gmail.com>
In-Reply-To: <525460CF.108@gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-ATIS-AV: ClamAV (irams1.ira.uni-karlsruhe.de)
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1381266528.
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Oct 2013 21:09:01 -0000

Hi Brian,

On 08.10.2013 21:45, Brian E Carpenter wrote:
> NEW
>    Today, IPv6 packets are often forwarded not only on the basis of their
>    first 40 bytes by straightforward IP routing. Some routers, and a
>    variety of intermediate nodes often referred to as middleboxes, such
>    as firewalls, load balancers, or packet classifiers, inspect other
>    parts of each packet.

Yes, but not necessarily?
I guess a NAT66 device is quite happy with processing the first 40 bytes
only. Not clear what's the exact purpose of these sentences
(definition of what a middlebox is or the fact that other parts
are also of interest for middleboxes),
but probably it's better to insert a "may also" before "inspect other".

Regards,
 Roland


From bclaise@cisco.com  Tue Oct  8 15:11:31 2013
Return-Path: <bclaise@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B65D221F9D98; Tue,  8 Oct 2013 15:11:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.569
X-Spam-Level: 
X-Spam-Status: No, score=-10.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id izDrJ5lHSNef; Tue,  8 Oct 2013 15:11:26 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 754A521F9E4F; Tue,  8 Oct 2013 15:11:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3333; q=dns/txt; s=iport; t=1381270284; x=1382479884; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=UV3xVd7+B9sasm82ptzW58XDgZwhnux/q6aJ0r5rb6I=; b=NamwiV49Y7Twghy7O/7CxNAjgwcOz1aybe00DfQVRH6qvothfWlHXj5R 9X+98PWlsFfrbGTtEv4iwJpKumT+FHOVbbCeEHRElcQzHQRXr6LmTATld GTZGeTyGf9Sk00Q1HwrTum1Ov9SX2GEM+N1OFa33+M3Y6acOTpDoK26X5 A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah0FACOCVFKQ/khR/2dsb2JhbABZgwc4wXuBJhZ0giUBAQEEOC0TARALGAkWDwkDAgECAQ82Bg0BBQIBAYdwAw8MsDcNiWuMV4JrB4QjA5YYgWmBL4UHhhSFNoFmgUA6
X-IronPort-AV: E=Sophos;i="4.90,1059,1371081600"; d="scan'208";a="160465633"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-1.cisco.com with ESMTP; 08 Oct 2013 22:11:23 +0000
Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r98MBH6e011852; Tue, 8 Oct 2013 22:11:19 GMT
Message-ID: <52548305.4080909@cisco.com>
Date: Wed, 09 Oct 2013 00:11:17 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: joel jaeggli <joelja@bogus.com>
Subject: Re: Joel Jaeggli's Discuss on draft-ietf-6man-ext-transmit-04: (with DISCUSS and COMMENT)
References: <20131008071948.25649.48005.idtracker@ietfa.amsl.com> <525457C1.5030503@gmail.com> <E93EBFCB-54C3-44D3-8126-8439AD15046E@bogus.com> <525460CF.108@gmail.com> <21DD9C6E-287F-4D18-B3F5-3FE01C5351E5@bogus.com>
In-Reply-To: <21DD9C6E-287F-4D18-B3F5-3FE01C5351E5@bogus.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 6man-chairs@tools.ietf.org, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org, The IESG <iesg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Oct 2013 22:11:31 -0000

FYI, there is a middlebox definition at 
http://tools.ietf.org/html/rfc3303#section-2.1

Regards, Benoit
> On Oct 8, 2013, at 12:45 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>
>> Joel,
>>
>> Would this help?
>>
>> OLD
>>    Today, packets are often forwarded not only by straightforward IP
>>    routers, but also by a variety of intermediate nodes, often referred
>>    to as middleboxes, such as firewalls, load balancers, or packet
>>    classifiers.
>>
>> NEW
>>    Today, IPv6 packets are often forwarded not only on the basis of their
>>    first 40 bytes by straightforward IP routing. Some routers, and a
>>    variety of intermediate nodes often referred to as middleboxes, such
>>    as firewalls, load balancers, or packet classifiers, inspect other
>>    parts of each packet.
>>
> I find that more palatable yeah.
>
>> (and possibly some changes for consistency later in the document)
>>
>>     Brian
>>
>>
>> On 09/10/2013 08:22, joel jaeggli wrote:
>>> On Oct 8, 2013, at 12:06 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>>
>>>> On 08/10/2013 20:19, Joel Jaeggli wrote:
>>>> ...
>>>>> ----------------------------------------------------------------------
>>>>> DISCUSS:
>>>>> ----------------------------------------------------------------------
>>>>>
>>>>> This is a dicuss because I'd like to see if I'm in the rough in this.
>>>>>
>>>>> Devices generally considered to be IP routers in fact are able to or find
>>>>> it necessary to forward on the basis of headers other than the IP header
>>>>> e.g. the transport header. By the definition applied in the problem
>>>>> statement all ipv6 capable routers in the internet that  I'm aware are or
>>>>> are capable of being middleboxes.
>>>> IMHO, yes, if a box is taking a forwarding decision on the basis of anything
>>>> other than the first 40 bytes of an IPv6 header, then it's a middlebox
>>>> as far as this draft is concerned. Any such box is not a "straightforward IP
>>>> router".
>>>>
>>>> In the process of working on the draft I have actually corresponded briefly
>>>> with Steve Deering, and I'm pretty sure he would agree with me (with
>>>> added expletives).
>>> Right, so there are no IP routers on the internet today and you should update the document accordingly because as it stands now it seems to presume their existence.
>>>
>>>>> I would welcome the existence proof of an ipv6 capable router which is
>>>>> not capable of being a middlebox by the definition applied in the problem
>>>>> statement.
>>>>>
>>>>> I'm not sure that's a glaring flaw in the document but it certainly is
>>>>> with our vocabulary around taxonomy if true.
>>>>>
>>>>>
>>>>> ----------------------------------------------------------------------
>>>>> COMMENT:
>>>>> ----------------------------------------------------------------------
>>>>>
>>>>> If you need to find the transport header due to configured policy and you
>>>>> can't due to being unable to parse the extensions chain your configured
>>>>> action will be to drop. That perhaps weasels it's way through section 2.1
>>>>> requirements but it's still quite ugly.
>>>> Yes, and it's the reason that the Internet is mainly opaque to IPv6
>>>> extensions headers today.
>>>>
>>>>    Brian
>>>>


From internet-drafts@ietf.org  Tue Oct  8 15:16:17 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED22F21E80A6; Tue,  8 Oct 2013 15:16:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.571
X-Spam-Level: 
X-Spam-Status: No, score=-102.571 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w3JZw2r9Jylu; Tue,  8 Oct 2013 15:16:15 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5497E21F9FB1; Tue,  8 Oct 2013 15:15:49 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-addr-select-opt-13.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131008221549.28645.42330.idtracker@ietfa.amsl.com>
Date: Tue, 08 Oct 2013 15:15:49 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Oct 2013 22:16:17 -0000

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           : Distributing Address Selection Policy using DHCPv6
	Author(s)       : Arifumi Matsumoto
                          Tomohiro Fujisaki
                          Tim Chown
	Filename        : draft-ietf-6man-addr-select-opt-13.txt
	Pages           : 12
	Date            : 2013-10-08

Abstract:
   RFC 6724 defines default address selection mechanisms for IPv6 that
   allow nodes to select an appropriate address when faced with multiple
   source and/or destination addresses to choose between.  RFC 6724
   allows for the future definition of methods to administratively
   configure the address selection policy information.  This document
   defines a new DHCPv6 option for such configuration, allowing a site
   administrator to distribute address selection policy overriding the
   default address selection parameters and policy table, and thus to
   control the address selection behavior of nodes in their site.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-addr-select-opt-13

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-addr-select-opt-13


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 joelja@bogus.com  Tue Oct  8 15:39:54 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BBD621F93F3; Tue,  8 Oct 2013 15:39:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tKg4tIEI7VVP; Tue,  8 Oct 2013 15:39:53 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 3215F21F90AF; Tue,  8 Oct 2013 15:39:46 -0700 (PDT)
Received: from mb-aye.corp.zynga.com ([199.48.105.4]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r98Mdg4f022734 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 8 Oct 2013 22:39:42 GMT (envelope-from joelja@bogus.com)
Content-Type: multipart/signed; boundary="Apple-Mail=_8F8C117B-F800-4EC6-A768-981DEB6AE39D"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Joel Jaeggli's Discuss on draft-ietf-6man-ext-transmit-04: (with DISCUSS and COMMENT)
From: joel jaeggli <joelja@bogus.com>
In-Reply-To: <52548305.4080909@cisco.com>
Date: Tue, 8 Oct 2013 15:39:39 -0700
Message-Id: <03355A6D-EE6A-45BC-8E4C-DDB2F20E8B88@bogus.com>
References: <20131008071948.25649.48005.idtracker@ietfa.amsl.com> <525457C1.5030503@gmail.com> <E93EBFCB-54C3-44D3-8126-8439AD15046E@bogus.com> <525460CF.108@gmail.com> <21DD9C6E-287F-4D18-B3F5-3FE01C5351E5@bogus.com> <52548305.4080909@cisco.com>
To: Benoit Claise <bclaise@cisco.com>
X-Mailer: Apple Mail (2.1510)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 08 Oct 2013 22:39:42 +0000 (UTC)
Cc: 6man-chairs@tools.ietf.org, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org, The IESG <iesg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Oct 2013 22:39:54 -0000

--Apple-Mail=_8F8C117B-F800-4EC6-A768-981DEB6AE39D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Oct 8, 2013, at 3:11 PM, Benoit Claise <bclaise@cisco.com> wrote:

> FYI, there is a middlebox definition at =
http://tools.ietf.org/html/rfc3303#section-2.1
>=20

yes I'm aware of it=85 As with discussion that dwells on the question of =
what was an ip router of the future expected to be like in 1994 and =
although it is temporally nearer, if there are no devices that any =
longer meets a strictly definition of a router (and the MIDCOM =
Architecture and Framework does not define router, middlebox taxonomy =
(3234) did, brian wrote that,  1812 does), then there are no routers =
anymore. only middleboxes.

If you like 1812 (and who doesn't). the transport layer ACLs are already =
in there. and thusly we're back here having as dicussion about whether a =
router is a device that needs to be able to find the upper layer header.

RFC 1812 5.3.9
=85

   If supported, a router SHOULD be configurable to allow one of an

   o Include list - specification of a list of message definitions to be
      forwarded, or an

   o Exclude list - specification of a list of message definitions NOT
      to be forwarded.

   A "message definition", in this context, specifies the source and
   destination network prefix, and may include other identifying
   information such as IP Protocol Type or TCP port number.
=85




> Regards, Benoit
>> On Oct 8, 2013, at 12:45 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>>=20
>>> Joel,
>>>=20
>>> Would this help?
>>>=20
>>> OLD
>>>   Today, packets are often forwarded not only by straightforward IP
>>>   routers, but also by a variety of intermediate nodes, often =
referred
>>>   to as middleboxes, such as firewalls, load balancers, or packet
>>>   classifiers.
>>>=20
>>> NEW
>>>   Today, IPv6 packets are often forwarded not only on the basis of =
their
>>>   first 40 bytes by straightforward IP routing. Some routers, and a
>>>   variety of intermediate nodes often referred to as middleboxes, =
such
>>>   as firewalls, load balancers, or packet classifiers, inspect other
>>>   parts of each packet.
>>>=20
>> I find that more palatable yeah.
>>=20
>>> (and possibly some changes for consistency later in the document)
>>>=20
>>>    Brian
>>>=20
>>>=20
>>> On 09/10/2013 08:22, joel jaeggli wrote:
>>>> On Oct 8, 2013, at 12:06 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>>>>=20
>>>>> On 08/10/2013 20:19, Joel Jaeggli wrote:
>>>>> ...
>>>>>> =
----------------------------------------------------------------------
>>>>>> DISCUSS:
>>>>>> =
----------------------------------------------------------------------
>>>>>>=20
>>>>>> This is a dicuss because I'd like to see if I'm in the rough in =
this.
>>>>>>=20
>>>>>> Devices generally considered to be IP routers in fact are able to =
or find
>>>>>> it necessary to forward on the basis of headers other than the IP =
header
>>>>>> e.g. the transport header. By the definition applied in the =
problem
>>>>>> statement all ipv6 capable routers in the internet that  I'm =
aware are or
>>>>>> are capable of being middleboxes.
>>>>> IMHO, yes, if a box is taking a forwarding decision on the basis =
of anything
>>>>> other than the first 40 bytes of an IPv6 header, then it's a =
middlebox
>>>>> as far as this draft is concerned. Any such box is not a =
"straightforward IP
>>>>> router".
>>>>>=20
>>>>> In the process of working on the draft I have actually =
corresponded briefly
>>>>> with Steve Deering, and I'm pretty sure he would agree with me =
(with
>>>>> added expletives).
>>>> Right, so there are no IP routers on the internet today and you =
should update the document accordingly because as it stands now it seems =
to presume their existence.
>>>>=20
>>>>>> I would welcome the existence proof of an ipv6 capable router =
which is
>>>>>> not capable of being a middlebox by the definition applied in the =
problem
>>>>>> statement.
>>>>>>=20
>>>>>> I'm not sure that's a glaring flaw in the document but it =
certainly is
>>>>>> with our vocabulary around taxonomy if true.
>>>>>>=20
>>>>>>=20
>>>>>> =
----------------------------------------------------------------------
>>>>>> COMMENT:
>>>>>> =
----------------------------------------------------------------------
>>>>>>=20
>>>>>> If you need to find the transport header due to configured policy =
and you
>>>>>> can't due to being unable to parse the extensions chain your =
configured
>>>>>> action will be to drop. That perhaps weasels it's way through =
section 2.1
>>>>>> requirements but it's still quite ugly.
>>>>> Yes, and it's the reason that the Internet is mainly opaque to =
IPv6
>>>>> extensions headers today.
>>>>>=20
>>>>>   Brian
>>>>>=20
>=20


--Apple-Mail=_8F8C117B-F800-4EC6-A768-981DEB6AE39D
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 - http://gpgtools.org

iEYEARECAAYFAlJUiasACgkQ8AA1q7Z/VrI6CACcDUwj/VJR0svhFacCG4l7LLp9
b6kAnjRYVEeh0anD4PVjrnFyfS2nvIGC
=Ug5Z
-----END PGP SIGNATURE-----

--Apple-Mail=_8F8C117B-F800-4EC6-A768-981DEB6AE39D--

From brian.e.carpenter@gmail.com  Tue Oct  8 16:10:16 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBEA121F9A2D for <ipv6@ietfa.amsl.com>; Tue,  8 Oct 2013 16:10:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.274
X-Spam-Level: 
X-Spam-Status: No, score=-102.274 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0hXpM7o2L9zG for <ipv6@ietfa.amsl.com>; Tue,  8 Oct 2013 16:10:16 -0700 (PDT)
Received: from mail-pd0-x22d.google.com (mail-pd0-x22d.google.com [IPv6:2607:f8b0:400e:c02::22d]) by ietfa.amsl.com (Postfix) with ESMTP id C583821F9CA1 for <ipv6@ietf.org>; Tue,  8 Oct 2013 16:10:10 -0700 (PDT)
Received: by mail-pd0-f173.google.com with SMTP id p10so9104pdj.4 for <ipv6@ietf.org>; Tue, 08 Oct 2013 16:10:10 -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=G5FkkLb/xyDm23U1KcnyCkPg+OBDtpolC3aHbGjdLNo=; b=ZcNI7JuYXxcuuv0HCBjcP78RlwBLMiLJzgJSQdWNk8bNSJPjwsGYyjL8QnqqdkJeq6 K1DnjKM1XFjOtIhWhd0NzsLG8bZ6BmuVebUSS7xvY9o+OxYDtUqp6miwkWmyRIv+DXtS 9/tTA7RhgJRngEyQeNrGAS6wxkpR2OK9XcmDz1ylVew2MBs4ll9iDM7kpI+w3mVsJfKv AEHe8PHdfHrr9hd6htPmraVJPiZyakiiurO69/16IpPQuRA1eHUGDExs5iuod0mtij8r qSi8GFMKD7cMzhzrZguJfdSbA2uyxW/oBPBYjdrH1WxeGxrGfhzQzXoxZqFx0wYMmSl/ 9NPA==
X-Received: by 10.68.135.100 with SMTP id pr4mr4687335pbb.62.1381273810392; Tue, 08 Oct 2013 16:10:10 -0700 (PDT)
Received: from [130.216.38.234] (dhcp-38-19.cs.auckland.ac.nz. [130.216.38.234]) by mx.google.com with ESMTPSA id oj6sm50159230pab.9.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 08 Oct 2013 16:10:09 -0700 (PDT)
Message-ID: <525490D3.9000505@gmail.com>
Date: Wed, 09 Oct 2013 12:10:11 +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: Roland Bless <roland.bless@kit.edu>
Subject: Re: Joel Jaeggli's Discuss on draft-ietf-6man-ext-transmit-04: (with DISCUSS and COMMENT)
References: <20131008071948.25649.48005.idtracker@ietfa.amsl.com>	<525457C1.5030503@gmail.com>	<E93EBFCB-54C3-44D3-8126-8439AD15046E@bogus.com> <525460CF.108@gmail.com> <52547462.5010309@kit.edu>
In-Reply-To: <52547462.5010309@kit.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Oct 2013 23:10:17 -0000

On 09/10/2013 10:08, Roland Bless wrote:
> Hi Brian,
> 
> On 08.10.2013 21:45, Brian E Carpenter wrote:
>> NEW
>>    Today, IPv6 packets are often forwarded not only on the basis of their
>>    first 40 bytes by straightforward IP routing. Some routers, and a
>>    variety of intermediate nodes often referred to as middleboxes, such
>>    as firewalls, load balancers, or packet classifiers, inspect other
>>    parts of each packet.
> 
> Yes, but not necessarily?
> I guess a NAT66 device is quite happy with processing the first 40 bytes
> only. 

I don't care about NAT66 but if you mean NPTv6, I suppose it's true.
Inserting "may" or perhaps "might" is OK by me.

    Brian

> Not clear what's the exact purpose of these sentences
> (definition of what a middlebox is or the fact that other parts
> are also of interest for middleboxes),
> but probably it's better to insert a "may also" before "inspect other".
> 
> Regards,
>  Roland
> 
> 

From rbonica@juniper.net  Tue Oct  8 17:46:44 2013
Return-Path: <rbonica@juniper.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CED521F9FB0; Tue,  8 Oct 2013 17:46:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.724
X-Spam-Level: 
X-Spam-Status: No, score=-102.724 tagged_above=-999 required=5 tests=[AWL=-0.125, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cSG7XsC3eMZP; Tue,  8 Oct 2013 17:46:38 -0700 (PDT)
Received: from db8outboundpool.messaging.microsoft.com (mail-db8lp0189.outbound.messaging.microsoft.com [213.199.154.189]) by ietfa.amsl.com (Postfix) with ESMTP id 2041C21F9FA3; Tue,  8 Oct 2013 17:46:35 -0700 (PDT)
Received: from mail134-db8-R.bigfish.com (10.174.8.230) by DB8EHSOBE027.bigfish.com (10.174.4.90) with Microsoft SMTP Server id 14.1.225.22; Wed, 9 Oct 2013 00:46:32 +0000
Received: from mail134-db8 (localhost [127.0.0.1])	by mail134-db8-R.bigfish.com (Postfix) with ESMTP id 63DEDA00C7; Wed,  9 Oct 2013 00:46:32 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT001.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -21
X-BigFish: VPS-21(zz9371I542I1432Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h1033IL1de097h8275dhz2fh2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1fe8h1ff5h9a9j1155h)
Received-SPF: pass (mail134-db8: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rbonica@juniper.net; helo=BL2PRD0510HT001.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(51704005)(377454003)(199002)(189002)(13464003)(54316002)(56776001)(85306002)(81686001)(76482001)(65816001)(66066001)(80022001)(74366001)(79102001)(77982001)(63696002)(59766001)(81816001)(74876001)(74706001)(83072001)(69226001)(47736001)(49866001)(50986001)(47976001)(53806001)(4396001)(46102001)(51856001)(54356001)(80976001)(31966008)(47446002)(74662001)(19580405001)(74502001)(83322001)(19580395003)(81542001)(74316001)(76796001)(76786001)(76576001)(81342001)(77096001)(33646001)(56816003)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BLUPR05MB436; H:BLUPR05MB433.namprd05.prod.outlook.com; CLIP:66.129.232.2; FPR:; RD:InfoNoRecords; A:1; MX:1; LANG:en; 
Received: from mail134-db8 (localhost.localdomain [127.0.0.1]) by mail134-db8 (MessageSwitch) id 138127959026135_8924; Wed,  9 Oct 2013 00:46:30 +0000 (UTC)
Received: from DB8EHSMHS018.bigfish.com (unknown [10.174.8.238])	by mail134-db8.bigfish.com (Postfix) with ESMTP id EBBF6480067; Wed,  9 Oct 2013 00:46:29 +0000 (UTC)
Received: from BL2PRD0510HT001.namprd05.prod.outlook.com (157.56.240.101) by DB8EHSMHS018.bigfish.com (10.174.4.28) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 9 Oct 2013 00:46:29 +0000
Received: from BLUPR05MB436.namprd05.prod.outlook.com (10.141.27.152) by BL2PRD0510HT001.namprd05.prod.outlook.com (10.255.100.36) with Microsoft SMTP Server (TLS) id 14.16.371.2; Wed, 9 Oct 2013 00:46:28 +0000
Received: from BLUPR05MB433.namprd05.prod.outlook.com (10.141.27.140) by BLUPR05MB436.namprd05.prod.outlook.com (10.141.27.152) with Microsoft SMTP Server (TLS) id 15.0.785.10; Wed, 9 Oct 2013 00:46:27 +0000
Received: from BLUPR05MB433.namprd05.prod.outlook.com ([169.254.16.72]) by BLUPR05MB433.namprd05.prod.outlook.com ([169.254.16.72]) with mapi id 15.00.0785.001; Wed, 9 Oct 2013 00:46:27 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Ole Troan <otroan@employees.org>, "Templin, Fred L" <Fred.L.Templin@boeing.com>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOv6KsdJvRhXd90UuLWVq4yr1RsZnlBPWAgASNmgCAAXGqAIAAjlqg
Date: Wed, 9 Oct 2013 00:46:27 +0000
Message-ID: <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org>
In-Reply-To: <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
x-forefront-prvs: 0994F5E0C5
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 09 Oct 2013 00:46:44 -0000

I agree with Ole.

       Ron

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> Ole Troan
> Sent: Tuesday, October 08, 2013 12:17 PM
> To: Templin, Fred L
> Cc: ipv6@ietf.org; ietf@ietf.org; IETF-Announce
> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> Fred,
>=20
> > Hi, I would like to make a small amendment to what I said in my
> > previous message as follows:
> >
> > 4) Section 5, change the final paragraph to:
> >
> >   "As a result of the above mentioned requirements, a packet's header
> >   chain length MUST fit within the Path MTU associated with its
> >   destination.  Hosts MAY discover the Path MTU, using procedures
> such
> >   as those defined in [RFC1981] and [RFC4821]. However, if a host
> does
> >   not discover the Path MTU, it MUST assume the IPv6 minumum MTU of
> >   1280 bytes [RFC2460]. The host MUST then limit each packet's header
> >   chain length to the Path MTU minus 256 bytes in case additional
> >   encapsulation headers are inserted by tunnels on the path."
>=20
> I would claim that additional encapsulation headers are already
> considered in the 1280 minimum MTU.
> as in: 1500 - 1280.
>=20
> cheers,
> Ole



From roland.bless@kit.edu  Wed Oct  9 03:20:42 2013
Return-Path: <roland.bless@kit.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C09721F8D20 for <ipv6@ietfa.amsl.com>; Wed,  9 Oct 2013 03:20:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JKQhyqQyL81d for <ipv6@ietfa.amsl.com>; Wed,  9 Oct 2013 03:20:36 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) by ietfa.amsl.com (Postfix) with ESMTP id F236C21F92B2 for <ipv6@ietf.org>; Wed,  9 Oct 2013 03:20:34 -0700 (PDT)
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5]) by iramx2.ira.uni-karlsruhe.de with esmtps port 25  id 1VTqsZ-0004Lq-Fr; Wed, 09 Oct 2013 12:20:33 +0200
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=vorta.tm.kit.edu) by irams1.ira.uni-karlsruhe.de with esmtp port 25  id 1VTqsZ-0001yc-GL; Wed, 09 Oct 2013 12:20:31 +0200
Received: from [IPv6:::1] (ip6-localhost [IPv6:::1]) by vorta.tm.kit.edu (Postfix) with ESMTPS id 6596DA8066A; Wed,  9 Oct 2013 12:20:31 +0200 (CEST)
Message-ID: <52552DEF.107@kit.edu>
Date: Wed, 09 Oct 2013 12:20:31 +0200
From: "Bless, Roland (TM)" <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Joel Jaeggli's Discuss on draft-ietf-6man-ext-transmit-04: (with DISCUSS and COMMENT)
References: <20131008071948.25649.48005.idtracker@ietfa.amsl.com>	<525457C1.5030503@gmail.com>	<E93EBFCB-54C3-44D3-8126-8439AD15046E@bogus.com> <525460CF.108@gmail.com> <52547462.5010309@kit.edu> <525490D3.9000505@gmail.com>
In-Reply-To: <525490D3.9000505@gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-ATIS-AV: ClamAV (irams1.ira.uni-karlsruhe.de)
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1381314033.
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 09 Oct 2013 10:20:42 -0000

Hi Brian,

On 09.10.2013 01:10, Brian E Carpenter wrote:
> I don't care about NAT66 but if you mean NPTv6, I suppose it's true.
> Inserting "may" or perhaps "might" is OK by me.

You are right, I meant NPTv6 - sorry didn't use the correct term.

Regards,
 Roland


From Fred.L.Templin@boeing.com  Wed Oct  9 08:38:34 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CF7B11E81A0; Wed,  9 Oct 2013 08:38:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4jQkWYCyevaE; Wed,  9 Oct 2013 08:38:25 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) by ietfa.amsl.com (Postfix) with ESMTP id 807FD11E81AC; Wed,  9 Oct 2013 08:38:17 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r99FcGCu028861; Wed, 9 Oct 2013 08:38:16 -0700
Received: from XCH-PHX-309.sw.nos.boeing.com (xch-phx-309.sw.nos.boeing.com [130.247.25.163]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r99FcEUr028393 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Wed, 9 Oct 2013 08:38:15 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.29]) by XCH-PHX-309.sw.nos.boeing.com ([169.254.9.168]) with mapi id 14.02.0328.011; Wed, 9 Oct 2013 08:38:14 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ronald Bonica <rbonica@juniper.net>, Ole Troan <otroan@employees.org>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOv6KsVHjrcZv7kkeUppI3Iq7lo5nlBPWAgASNmgCAAXGqAIAAjlqggAD4aZA=
Date: Wed, 9 Oct 2013 15:38:14 +0000
Message-ID: <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com>
In-Reply-To: <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 09 Oct 2013 15:38:34 -0000

> -----Original Message-----
> From: Ronald Bonica [mailto:rbonica@juniper.net]
> Sent: Tuesday, October 08, 2013 5:46 PM
> To: Ole Troan; Templin, Fred L
> Cc: ipv6@ietf.org; ietf@ietf.org
> Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> I agree with Ole.

How so? A tunnel that crosses a 1280 MTU link MUST fragment
in order to satisfy the IPv6 minMTU. If it must fragment, then
an MTU-length IPv6 header chain would not fit within the first
fragment, and we have opened an attack vector against tunnels.
This is not a matter to be agreed or disagreed with - it is
a simple fact.

Thanks - Fred
fred.l.templin@boeing.com
=20
>        Ron
>=20
> > -----Original Message-----
> > From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf
> Of
> > Ole Troan
> > Sent: Tuesday, October 08, 2013 12:17 PM
> > To: Templin, Fred L
> > Cc: ipv6@ietf.org; ietf@ietf.org; IETF-Announce
> > Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-
> 08.txt>
> > (Implications of Oversized IPv6 Header Chains) to Proposed Standard
> >
> > Fred,
> >
> > > Hi, I would like to make a small amendment to what I said in my
> > > previous message as follows:
> > >
> > > 4) Section 5, change the final paragraph to:
> > >
> > >   "As a result of the above mentioned requirements, a packet's
> header
> > >   chain length MUST fit within the Path MTU associated with its
> > >   destination.  Hosts MAY discover the Path MTU, using procedures
> > such
> > >   as those defined in [RFC1981] and [RFC4821]. However, if a host
> > does
> > >   not discover the Path MTU, it MUST assume the IPv6 minumum MTU of
> > >   1280 bytes [RFC2460]. The host MUST then limit each packet's
> header
> > >   chain length to the Path MTU minus 256 bytes in case additional
> > >   encapsulation headers are inserted by tunnels on the path."
> >
> > I would claim that additional encapsulation headers are already
> > considered in the 1280 minimum MTU.
> > as in: 1500 - 1280.
> >
> > cheers,
> > Ole
>=20


From otroan@employees.org  Wed Oct  9 09:54:04 2013
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A77C21F9EF6; Wed,  9 Oct 2013 09:54:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UDalrdE9AQtq; Wed,  9 Oct 2013 09:53:58 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [198.137.202.19]) by ietfa.amsl.com (Postfix) with ESMTP id D91D821F8DDD; Wed,  9 Oct 2013 09:53:54 -0700 (PDT)
Received: from dhcp-10-61-105-179.cisco.com (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id EDE946052; Wed,  9 Oct 2013 09:53:52 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_3F38F5EB-81AD-41C7-9D61-91842357817C"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
From: Ole Troan <otroan@employees.org>
In-Reply-To: <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com>
Date: Wed, 9 Oct 2013 18:53:48 +0200
Message-Id: <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.1510)
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 09 Oct 2013 16:54:04 -0000

--Apple-Mail=_3F38F5EB-81AD-41C7-9D61-91842357817C
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Fred,

>> -----Original Message-----
>> From: Ronald Bonica [mailto:rbonica@juniper.net]
>> Sent: Tuesday, October 08, 2013 5:46 PM
>> To: Ole Troan; Templin, Fred L
>> Cc: ipv6@ietf.org; ietf@ietf.org
>> Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
>> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>> 
>> I agree with Ole.
> 
> How so? A tunnel that crosses a 1280 MTU link MUST fragment
> in order to satisfy the IPv6 minMTU. If it must fragment, then
> an MTU-length IPv6 header chain would not fit within the first
> fragment, and we have opened an attack vector against tunnels.
> This is not a matter to be agreed or disagreed with - it is
> a simple fact.

right, and RFC2460 has this to say about it:

   IPv6 requires that every link in the internet have an MTU of 1280
   octets or greater.  On any link that cannot convey a 1280-octet
   packet in one piece, link-specific fragmentation and reassembly must
   be provided at a layer below IPv6.

cheers,
Ole

--Apple-Mail=_3F38F5EB-81AD-41C7-9D61-91842357817C
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

iQEcBAEBCgAGBQJSVYocAAoJEFuJXizso86ggAsIAJnGAgJoyw+0vJ4g5UQE3KQC
Y+L90GWYQCx6ae1BCbDqdklSlUSRYKyBWwyScpPEaH5cCiobKVA3IKbFf18f0BST
DsArIO3aZ0aTe0PmBqoHeW8M0At40jJYw6O3OTXrm1Hw7z3LS2DLfzflWgXoXjDz
SF8R32yClsU7IcZi1wgHxvERFk/DgGcDtCBOPpAXKtxwDU53tnpy9NgqCWfmH9hd
B5dmCgHkEknbrGo2ebWgdwrvMF8AVDxpnh4vtn0YrrP+8frN6FnpAIVjQvizAvyM
6+ze3z2XjA9oNbsmHQnQeN7+lcdJTWuPmUHvzdPuozM+2N/ecXCdNaP+w0FsDLk=
=N2+D
-----END PGP SIGNATURE-----

--Apple-Mail=_3F38F5EB-81AD-41C7-9D61-91842357817C--

From Fred.L.Templin@boeing.com  Wed Oct  9 10:20:28 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A43AF21E80A8; Wed,  9 Oct 2013 10:20:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BTzulXFa5UTY; Wed,  9 Oct 2013 10:20:22 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) by ietfa.amsl.com (Postfix) with ESMTP id 2B88A21E805F; Wed,  9 Oct 2013 10:20:17 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r99HKDXB003755; Wed, 9 Oct 2013 10:20:13 -0700
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r99HK9rY003654 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Wed, 9 Oct 2013 10:20:13 -0700
Received: from XCH-BLV-306.nw.nos.boeing.com (130.247.25.218) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Wed, 9 Oct 2013 10:20:03 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.29]) by XCH-BLV-306.nw.nos.boeing.com ([169.254.6.159]) with mapi id 14.02.0328.011; Wed, 9 Oct 2013 10:20:02 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ole Troan <otroan@employees.org>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOxRAfebc9KTehbEGO6mhunuAlj5nsnKbg
Date: Wed, 9 Oct 2013 17:20:01 +0000
Message-ID: <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org>
In-Reply-To: <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 09 Oct 2013 17:20:29 -0000

Hi Ole,

> -----Original Message-----
> From: Ole Troan [mailto:otroan@employees.org]
> Sent: Wednesday, October 09, 2013 9:54 AM
> To: Templin, Fred L
> Cc: Ronald Bonica; ipv6@ietf.org; ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> Fred,
>=20
> >> -----Original Message-----
> >> From: Ronald Bonica [mailto:rbonica@juniper.net]
> >> Sent: Tuesday, October 08, 2013 5:46 PM
> >> To: Ole Troan; Templin, Fred L
> >> Cc: ipv6@ietf.org; ietf@ietf.org
> >> Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-
> 08.txt>
> >> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
> >>
> >> I agree with Ole.
> >
> > How so? A tunnel that crosses a 1280 MTU link MUST fragment
> > in order to satisfy the IPv6 minMTU. If it must fragment, then
> > an MTU-length IPv6 header chain would not fit within the first
> > fragment, and we have opened an attack vector against tunnels.
> > This is not a matter to be agreed or disagreed with - it is
> > a simple fact.
>=20
> right, and RFC2460 has this to say about it:
>=20
>    IPv6 requires that every link in the internet have an MTU of 1280
>    octets or greater.  On any link that cannot convey a 1280-octet
>    packet in one piece, link-specific fragmentation and reassembly must
>    be provided at a layer below IPv6.

Very true. In this case, the "link" is the tunnel and the "link-specific
fragmentation" is IPv6 fragmentation. Which places the first part of an
MTU-length IPv6 header chain in the first fragment and the remainder of
the header chain in the second fragment.

Thanks - Fred
fred.l.templin@boeing.com

> cheers,
> Ole

From otroan@employees.org  Wed Oct  9 10:31:24 2013
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EA2621E815F; Wed,  9 Oct 2013 10:31:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wk4hj0wrUEbF; Wed,  9 Oct 2013 10:31:23 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) by ietfa.amsl.com (Postfix) with ESMTP id 9411A21E8149; Wed,  9 Oct 2013 10:31:16 -0700 (PDT)
Received: from dhcp-10-61-106-139.cisco.com (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 2665B6002; Wed,  9 Oct 2013 10:31:13 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_D6F7732C-6360-4A9A-8B7E-20A0DFE08AEA"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
From: Ole Troan <otroan@employees.org>
In-Reply-To: <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com>
Date: Wed, 9 Oct 2013 19:31:10 +0200
Message-Id: <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.1510)
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 09 Oct 2013 17:31:24 -0000

--Apple-Mail=_D6F7732C-6360-4A9A-8B7E-20A0DFE08AEA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Fred,

>>>> -----Original Message-----
>>>> From: Ronald Bonica [mailto:rbonica@juniper.net]
>>>> Sent: Tuesday, October 08, 2013 5:46 PM
>>>> To: Ole Troan; Templin, Fred L
>>>> Cc: ipv6@ietf.org; ietf@ietf.org
>>>> Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-
>> 08.txt>
>>>> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>>>>=20
>>>> I agree with Ole.
>>>=20
>>> How so? A tunnel that crosses a 1280 MTU link MUST fragment
>>> in order to satisfy the IPv6 minMTU. If it must fragment, then
>>> an MTU-length IPv6 header chain would not fit within the first
>>> fragment, and we have opened an attack vector against tunnels.
>>> This is not a matter to be agreed or disagreed with - it is
>>> a simple fact.
>>=20
>> right, and RFC2460 has this to say about it:
>>=20
>>   IPv6 requires that every link in the internet have an MTU of 1280
>>   octets or greater.  On any link that cannot convey a 1280-octet
>>   packet in one piece, link-specific fragmentation and reassembly =
must
>>   be provided at a layer below IPv6.
>=20
> Very true. In this case, the "link" is the tunnel and the =
"link-specific
> fragmentation" is IPv6 fragmentation. Which places the first part of =
an
> MTU-length IPv6 header chain in the first fragment and the remainder =
of
> the header chain in the second fragment.

indeed. which would violate the MUST in oversized-header-chain.

what do we do?
a) ignore this particular corner case
b) suggest the tunnel head end to drop the packet
c) develop a new tunnel segmentations scheme that doesn't depend on IPv6 =
fragmentation. :-)

cheers,
Ole


--Apple-Mail=_D6F7732C-6360-4A9A-8B7E-20A0DFE08AEA
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

iQEcBAEBCgAGBQJSVZLeAAoJEFuJXizso86gXzEH+wcd6qhbVkHKDUDLAuPxgiNu
Q2W1lXgeeT3u4bzfEolKEeYRgnOV1nscX94feKCKuQfX2XHaK8IEnQ2R22CkzZMQ
WXjwrRVIjJ2xuSCNJodEJjoRpbv5KhjNP/uEyyj/GE+zKa1eYaQ3aYC7ZPhlLW/p
lLekX6kwMGkHfbCGDWD5HpHgEUEJOUfkWZTxYl45BlZ5BrYZ8BHuzG87QlUFLLrG
+EpE1ch6mTV2hdxuTpRfDRRlgVmgmv6xE+bR5vZ6+psrxCPAzJZVnVBRbj8TGwFF
05cfiMyFlOjzPh5Dt2+jiyPhuCKC+7x7u5GqQpAhV3U8UvhBn5MhrYiCzjPasIo=
=pUDl
-----END PGP SIGNATURE-----

--Apple-Mail=_D6F7732C-6360-4A9A-8B7E-20A0DFE08AEA--

From Fred.L.Templin@boeing.com  Wed Oct  9 10:43:05 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F17C21E814A; Wed,  9 Oct 2013 10:43:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gZVczlVSfcOd; Wed,  9 Oct 2013 10:42:59 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (stl-mbsout-01.boeing.com [130.76.96.169]) by ietfa.amsl.com (Postfix) with ESMTP id E290C21E8151; Wed,  9 Oct 2013 10:42:58 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r99HgujR023300; Wed, 9 Oct 2013 12:42:56 -0500
Received: from XCH-PHX-409.sw.nos.boeing.com (xch-phx-409.sw.nos.boeing.com [10.57.37.40]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r99HgtaJ023293 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Wed, 9 Oct 2013 12:42:56 -0500
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.29]) by XCH-PHX-409.sw.nos.boeing.com ([169.254.9.8]) with mapi id 14.02.0328.011; Wed, 9 Oct 2013 10:42:55 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ole Troan <otroan@employees.org>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOxRVXebc9KTehbEGO6mhunuAlj5nsok8A
Date: Wed, 9 Oct 2013 17:42:54 +0000
Message-ID: <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org>
In-Reply-To: <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 09 Oct 2013 17:43:05 -0000

Hi Ole,

> -----Original Message-----
> From: Ole Troan [mailto:otroan@employees.org]
> Sent: Wednesday, October 09, 2013 10:31 AM
> To: Templin, Fred L
> Cc: Ronald Bonica; ipv6@ietf.org; ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> Fred,
>=20
> >>>> -----Original Message-----
> >>>> From: Ronald Bonica [mailto:rbonica@juniper.net]
> >>>> Sent: Tuesday, October 08, 2013 5:46 PM
> >>>> To: Ole Troan; Templin, Fred L
> >>>> Cc: ipv6@ietf.org; ietf@ietf.org
> >>>> Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-
> >> 08.txt>
> >>>> (Implications of Oversized IPv6 Header Chains) to Proposed
> Standard
> >>>>
> >>>> I agree with Ole.
> >>>
> >>> How so? A tunnel that crosses a 1280 MTU link MUST fragment
> >>> in order to satisfy the IPv6 minMTU. If it must fragment, then
> >>> an MTU-length IPv6 header chain would not fit within the first
> >>> fragment, and we have opened an attack vector against tunnels.
> >>> This is not a matter to be agreed or disagreed with - it is
> >>> a simple fact.
> >>
> >> right, and RFC2460 has this to say about it:
> >>
> >>   IPv6 requires that every link in the internet have an MTU of 1280
> >>   octets or greater.  On any link that cannot convey a 1280-octet
> >>   packet in one piece, link-specific fragmentation and reassembly
> must
> >>   be provided at a layer below IPv6.
> >
> > Very true. In this case, the "link" is the tunnel and the "link-
> specific
> > fragmentation" is IPv6 fragmentation. Which places the first part of
> an
> > MTU-length IPv6 header chain in the first fragment and the remainder
> of
> > the header chain in the second fragment.
>=20
> indeed. which would violate the MUST in oversized-header-chain.
>=20
> what do we do?
> a) ignore this particular corner case
> b) suggest the tunnel head end to drop the packet
> c) develop a new tunnel segmentations scheme that doesn't depend on
> IPv6 fragmentation. :-)

You know I have an interest in alternative c), but that does not
address the issue of splitting the header chain across multiple
fragments. So, my choice is:

d) limit the size of the IPv6 header chain so that the chain will
fit within the first fragment by having the host limit the chain
to the MTU size minus 256 bytes.

Actually, I would be even happier if we just asked the host to limit
the size of the header chain to 1024 bytes regardless of the path MTU.

Thanks - Fred
fred.l.templin@boeing.com

> cheers,
> Ole


From ietf-secretariat-reply@ietf.org  Wed Oct  9 12:07:58 2013
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEFD721E81AC for <ipv6@ietfa.amsl.com>; Wed,  9 Oct 2013 12:07:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.407
X-Spam-Level: 
X-Spam-Status: No, score=-102.407 tagged_above=-999 required=5 tests=[AWL=0.193, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wvx+AnKBmH4o; Wed,  9 Oct 2013 12:07:58 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 84A7821E81AF; Wed,  9 Oct 2013 12:06:55 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
To: 6man-chairs@tools.ietf.org, draft-ietf-6man-oversized-header-chain@tools.ietf.org, ipv6@ietf.org
Subject: ID Tracker State Update Notice: <draft-ietf-6man-oversized-header-chain-08.txt>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131009190655.22946.73352.idtracker@ietfa.amsl.com>
Date: Wed, 09 Oct 2013 12:06:55 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 09 Oct 2013 19:07:59 -0000

IANA review state changed to IANA OK - Actions Needed
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-6man-oversized-h=
eader-chain/


From iesg-secretary@ietf.org  Wed Oct  9 13:41:38 2013
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2044B11E80FC; Wed,  9 Oct 2013 13:41:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.373
X-Spam-Level: 
X-Spam-Status: No, score=-102.373 tagged_above=-999 required=5 tests=[AWL=0.227, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0BHFf9QLm3im; Wed,  9 Oct 2013 13:41:37 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E6A3921E81BE; Wed,  9 Oct 2013 13:41:33 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'Distributing Address Selection Policy using DHCPv6' to Proposed Standard (draft-ietf-6man-addr-select-opt-13.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131009204133.15919.94972.idtracker@ietfa.amsl.com>
Date: Wed, 09 Oct 2013 13:41:33 -0700
Cc: 6man chair <6man-chairs@tools.ietf.org>, 6man mailing list <ipv6@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 09 Oct 2013 20:41:38 -0000

The IESG has approved the following document:
- 'Distributing Address Selection Policy using DHCPv6'
  (draft-ietf-6man-addr-select-opt-13.txt) as Proposed Standard

This document is the product of the IPv6 Maintenance Working Group.

The IESG contact persons are Brian Haberman and Ted Lemon.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-6man-addr-select-opt/




Technical Summary:

   RFC 6724 defines default address selection mechanisms for IPv6 that
   allow nodes to select an appropriate address when faced with multiple
   source and/or destination addresses to choose between.  The RFC 6724
   allowed for the future definition of methods to administratively
   configure the address selection policy information.  This document
   defines a new DHCPv6 option for such configuration, allowing a site
   administrator to distribute address selection policy overriding the
   default address selection parameters and policy table, and thus
   control the address selection behavior of nodes in their site.

Working Group Summary:

Was there anything in WG process that is worth noting? For example,
was there controversy about particular points or were there decisions
where the consensus was particularly rough?

  Nothing in particular.

Document Quality:

Are there existing implementations of the protocol? Have a significant
number of vendors indicated their plan to implement the specification?
Are there any reviewers that merit special mention as having done a
thorough review, e.g., one that resulted in important changes or a
conclusion that the document had no substantive issues? If there was a
MIB Doctor, Media Type or other expert review, what was its course
(briefly)? In the case of a Media Type review, on what date was the
request posted?

  Ray Hunter has done a thorough review of the document,
  in addition has the 6man chairs done a 'chair's review' of 
  the document.

  The document has also been through a last call in the DHC WG.

Personnel:

  Ole Troan is the Document Shepherd. 
  Brian Haberman is the Responsible Area Director.

RFC Editor Note

In the IANA considerations section, please make the following change:

OLD:
http://www.iana.org/assignments/dhcpv6-parameters/dhcpv6-parameters.xml

NEW:
https://www.iana.org/assignments/dhcpv6-parameters

From brian.e.carpenter@gmail.com  Wed Oct  9 15:21:35 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9032321F9B90; Wed,  9 Oct 2013 15:21:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.547
X-Spam-Level: 
X-Spam-Status: No, score=-102.547 tagged_above=-999 required=5 tests=[AWL=0.052, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WqQl7Y85ScDf; Wed,  9 Oct 2013 15:21:35 -0700 (PDT)
Received: from mail-pd0-x231.google.com (mail-pd0-x231.google.com [IPv6:2607:f8b0:400e:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id 40B5821E81C6; Wed,  9 Oct 2013 15:21:32 -0700 (PDT)
Received: by mail-pd0-f177.google.com with SMTP id y10so1607351pdj.8 for <multiple recipients>; Wed, 09 Oct 2013 15:21:32 -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=UtIt7IW8dgroLa5U6prSejhIJGLl3dTBB1Vf3Gv5uSs=; b=oq/eHwqT/s1vH9KSq8dntWuNJAk95daRkCdIDXTi/pddV8U/GSov9qq1p1kEY1IJ2+ kVqYgBb++2dGYOBpFvWphSWyazZZ3aRDJGUeE0dU2pm0EsdCCaHpxEkEEFVCuQEsN4pk 0S35Y8yP9HGgV025FOezObrWmRJWok5Z7zEY15yixa6q/i5Hj3cvDNjLFGnEKXIEdKc+ TFt9YfId5uDGnuNTrA4jUGTrHbEHDpH7cPgt+LbGZk06QvQZWvjya38ikESAkqTcr+ZU BQ09RG1rkz3k4B8C37JWBGWJ93AHFwkKwRMR52VhgtKoBFvBVPVesBtMduKMjEeL9pby XVrg==
X-Received: by 10.67.5.132 with SMTP id cm4mr65764pad.186.1381357291923; Wed, 09 Oct 2013 15:21:31 -0700 (PDT)
Received: from [192.168.178.20] (103.197.69.111.dynamic.snap.net.nz. [111.69.197.103]) by mx.google.com with ESMTPSA id zq10sm57534522pab.6.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 09 Oct 2013 15:21:31 -0700 (PDT)
Message-ID: <5255D6EE.4050300@gmail.com>
Date: Thu, 10 Oct 2013 11:21: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: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>	(Implications of Oversized IPv6 Header Chains) to Proposed Standard
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com>	<2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com>	<2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com>	<9300F272-E282-41C3-9DA8-59134B975FC7@employees.org>	<9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com>	<2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com>	<D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org>	<2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com>	<E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 09 Oct 2013 22:21:35 -0000

Fred,

See below...

On 10/10/2013 06:42, Templin, Fred L wrote:
> Hi Ole,
> 
>> -----Original Message-----
>> From: Ole Troan [mailto:otroan@employees.org]
>> Sent: Wednesday, October 09, 2013 10:31 AM
>> To: Templin, Fred L
>> Cc: Ronald Bonica; ipv6@ietf.org; ietf@ietf.org
>> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
>> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>>
>> Fred,
>>
>>>>>> -----Original Message-----
>>>>>> From: Ronald Bonica [mailto:rbonica@juniper.net]
>>>>>> Sent: Tuesday, October 08, 2013 5:46 PM
>>>>>> To: Ole Troan; Templin, Fred L
>>>>>> Cc: ipv6@ietf.org; ietf@ietf.org
>>>>>> Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-
>>>> 08.txt>
>>>>>> (Implications of Oversized IPv6 Header Chains) to Proposed
>> Standard
>>>>>> I agree with Ole.
>>>>> How so? A tunnel that crosses a 1280 MTU link MUST fragment
>>>>> in order to satisfy the IPv6 minMTU. If it must fragment, then
>>>>> an MTU-length IPv6 header chain would not fit within the first
>>>>> fragment, and we have opened an attack vector against tunnels.
>>>>> This is not a matter to be agreed or disagreed with - it is
>>>>> a simple fact.
>>>> right, and RFC2460 has this to say about it:
>>>>
>>>>   IPv6 requires that every link in the internet have an MTU of 1280
>>>>   octets or greater.  On any link that cannot convey a 1280-octet
>>>>   packet in one piece, link-specific fragmentation and reassembly
>> must
>>>>   be provided at a layer below IPv6.
>>> Very true. In this case, the "link" is the tunnel and the "link-
>> specific
>>> fragmentation" is IPv6 fragmentation. Which places the first part of
>> an
>>> MTU-length IPv6 header chain in the first fragment and the remainder
>> of
>>> the header chain in the second fragment.
>> indeed. which would violate the MUST in oversized-header-chain.
>>
>> what do we do?
>> a) ignore this particular corner case
>> b) suggest the tunnel head end to drop the packet
>> c) develop a new tunnel segmentations scheme that doesn't depend on
>> IPv6 fragmentation. :-)
> 
> You know I have an interest in alternative c), but that does not
> address the issue of splitting the header chain across multiple
> fragments. So, my choice is:
> 
> d) limit the size of the IPv6 header chain so that the chain will
> fit within the first fragment by having the host limit the chain
> to the MTU size minus 256 bytes.
> 
> Actually, I would be even happier if we just asked the host to limit
> the size of the header chain to 1024 bytes regardless of the path MTU.

Since the problem recurses as we tunnel tunnels, I don't see how any
finite limit can solve the problem. 1280 itself is a pragmatic choice
of "a bit shorter than 1500".

The problem is that you are asserting that middleboxes that a tunnel
passes through are expected to examine the complete header chain of
the encapsulated packet even if the encapsulated packet is a fragment.
I think that's an unreasonable expectation. A reasonable expectation
is that middleboxes should identify the encapsulated packet as
a payload that they cannot analyse, and let it go (unless they
have a policy setting to drop tunnelled packets, which is a
different discussion).

I understood that to be the basis on which the WG reached consensus.

    Brian


From Fred.L.Templin@boeing.com  Wed Oct  9 16:13:34 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAE5421E81F2; Wed,  9 Oct 2013 16:13:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.335
X-Spam-Level: 
X-Spam-Status: No, score=-6.335 tagged_above=-999 required=5 tests=[AWL=0.264,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dJFQgSs59KA4; Wed,  9 Oct 2013 16:13:19 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) by ietfa.amsl.com (Postfix) with ESMTP id 227D121E81ED; Wed,  9 Oct 2013 16:13:14 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r99NDDWV009348; Wed, 9 Oct 2013 16:13:13 -0700
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r99NDCkY009345 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Wed, 9 Oct 2013 16:13:12 -0700
Received: from XCH-BLV-301.nw.nos.boeing.com (130.247.25.213) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Wed, 9 Oct 2013 16:13:11 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.29]) by XCH-BLV-301.nw.nos.boeing.com ([169.254.1.180]) with mapi id 14.02.0328.011; Wed, 9 Oct 2013 16:13:11 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOxT3pVHjrcZv7kkeUppI3Iq7lo5ns+Qtg
Date: Wed, 9 Oct 2013 23:13:11 +0000
Message-ID: <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com>
In-Reply-To: <5255D6EE.4050300@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 09 Oct 2013 23:13:34 -0000

SGkgQnJpYW4sDQoNClJlc3BvbmRpbmcgaW4gYSBzbGlnaHRseSByZS1hcnJhbmdlZCBvcmRlcjoN
Cg0KPiBUaGUgcHJvYmxlbSBpcyB0aGF0IHlvdSBhcmUgYXNzZXJ0aW5nIHRoYXQgbWlkZGxlYm94
ZXMgdGhhdCBhIHR1bm5lbA0KPiBwYXNzZXMgdGhyb3VnaCBhcmUgZXhwZWN0ZWQgdG8gZXhhbWlu
ZSB0aGUgY29tcGxldGUgaGVhZGVyIGNoYWluIG9mDQo+IHRoZSBlbmNhcHN1bGF0ZWQgcGFja2V0
IGV2ZW4gaWYgdGhlIGVuY2Fwc3VsYXRlZCBwYWNrZXQgaXMgYSBmcmFnbWVudC4NCg0KWWVzLCBi
dXQgY2hhbmdlICJhcmUgZXhwZWN0ZWQgdG8iIHRvICJzaG91bGQgYmUgYWJsZSB0byIuDQoNCj4g
SSB0aGluayB0aGF0J3MgYW4gdW5yZWFzb25hYmxlIGV4cGVjdGF0aW9uLiBBIHJlYXNvbmFibGUg
ZXhwZWN0YXRpb24NCj4gaXMgdGhhdCBtaWRkbGVib3hlcyBzaG91bGQgaWRlbnRpZnkgdGhlIGVu
Y2Fwc3VsYXRlZCBwYWNrZXQgYXMNCj4gYSBwYXlsb2FkIHRoYXQgdGhleSBjYW5ub3QgYW5hbHlz
ZSwgYW5kIGxldCBpdCBnbyAodW5sZXNzIHRoZXkNCj4gaGF2ZSBhIHBvbGljeSBzZXR0aW5nIHRv
IGRyb3AgdHVubmVsbGVkIHBhY2tldHMsIHdoaWNoIGlzIGENCj4gZGlmZmVyZW50IGRpc2N1c3Np
b24pLg0KDQpCdXQgd2h5PyBJZiBoZWFkZXJzIGJleW9uZCB0aGUgZmlyc3QgSVB2NiBlbmNhcHN1
bGF0aW9uIGhlYWRlciBhcmUNCmF2YWlsYWJsZSBpbiB0aGUgY2xlYXIsIHRoZSBtaWRkbGVib3gg
c2hvdWxkIGJlIGFibGUgdG8gcGFyc2UgdGhlbQ0KaWYgaXQgd2FudHMgdG8uIFdpcmVzaGFyayBh
bHJlYWR5IGRvZXMgZXhhY3RseSB0aGF0IC0gaXQga2VlcHMgb24NCnBhcnNpbmcgYmV5b25kIHRo
ZSBmaXJzdCBlbmNhcHN1bGF0aW9uIGhlYWRlciB1cCB0byBhbmQgaW5jbHVkaW5nDQp0aGUgdHJ1
ZSBVTFAgaGVhZGVyLiBBbmQsIGlmIFdpcmVzaGFyayBjYW4gZG8gaXQsIHNvIGNhbiBhbnkgb3Ro
ZXINCm1pZGRsZWJveCB0aGF0IGJlbGlldmVzIHNlY3VyaXR5IHdvdWxkIGJlIGltcHJvdmVkIGJ5
IGNvbnRpbnVpbmcNCnRvIHBhcnNlIHRoZSBlbnRpcmUgY2hhaW4gLSB3aGV0aGVyIG9yIG5vdCB0
aGVyZSBpcyBhIHN0YW5kYXJkDQpzYXlpbmcgaXQgbXVzdCBub3QgZG8gc28uDQoNClBhcnNpbmcg
dGhlIGFkZGl0aW9uYWwgaGVhZGVycyBiZXlvbmQgdGhlIGZpcnN0IGVuY2Fwc3VsYXRpb24gaGVh
ZGVyDQpwcm92aWRlcyBkZWZlbnNlLWluLWRlcHRoLiBQZXJpbWV0ZXIgbWlkZGxlYm94ZXMgY2Fu
IHRoZW4gd2VlZCBvdXQNCnRoZSBiYWQgc3R1ZmYgd2l0aG91dCBlaXRoZXIgYWxsb3dpbmcgdGhl
IGJhZCBzdHVmZiB0byBwZW5ldHJhdGUgbW9yZQ0KZGVlcGx5IGludG8gdGhlIG9yZ2FuaXphdGlv
biBvciBkcm9wcGluZyBnb29kIHN0dWZmIHRoYXQgc2hvdWxkIGJlDQphbGxvd2VkIHRocm91Z2gu
DQoNCj4gU2luY2UgdGhlIHByb2JsZW0gcmVjdXJzZXMgYXMgd2UgdHVubmVsIHR1bm5lbHMsIEkg
ZG9uJ3Qgc2VlIGhvdyBhbnkNCj4gZmluaXRlIGxpbWl0IGNhbiBzb2x2ZSB0aGUgcHJvYmxlbS4g
MTI4MCBpdHNlbGYgaXMgYSBwcmFnbWF0aWMgY2hvaWNlDQo+IG9mICJhIGJpdCBzaG9ydGVyIHRo
YW4gMTUwMCIuDQoNClRoZSAxMjgwIGlzIGFzc3VtaW5nIHRoYXQgYWxsIGxpbmtzIGluIHRoZSBw
YXRoIGhhdmUgYSAxNTAwIE1UVSBhbmQNCnNvIFJGQzI0NjAgYWxsb3dlZCAoMTUwMCAtIDEyODAp
ID0gMjIwIGJ5dGVzIGZvciBhZGRpdGlvbmFsIElQdjYNCmhlYWRlcnMgYWRkZWQgYnkgbmVzdGVk
IHR1bm5lbHMgd2l0aG91dCBpbmN1cnJpbmcgZnJhZ21lbnRhdGlvbi4NCkkgYW0gYXNzZXJ0aW5n
IGluc3RlYWQgdGhhdCB3ZSBoYXZlIHRvIGFsbG93IGZvciBwYXRocyB0aGF0IGluY2x1ZGUNCmxp
bmtzIHdpdGggYSAxMjgwIE1UVSBhbmQgc28gdHVubmVscyB3aWxsIGhhdmUgdG8gZnJhZ21lbnQg
b3Zlcg0Kc3VjaCBwYXRocy4NCg0KVGhhdCBtZWFucyB0aGF0IHRoZSBmaXJzdCBmcmFnbWVudGlu
ZyB0dW5uZWwgd291bGQgaGF2ZSByb29tIGZvcg0KMTI0MCBpbiB0aGUgZmlyc3QgZnJhZ21lbnQs
IHRoZSBzZWNvbmQgZnJhZ21lbnRpbmcgdHVubmVsIHdvdWxkDQpoYXZlIHJvb20gZm9yIDEyMDAg
aW4gdGhlIGZpcnN0IGZyYWdtZW50LCBldGMuIFRoYXQgaXMgd2h5IEkgd291bGQNCnByZWZlciB0
aGF0IGhvc3RzIGxpbWl0IHRoZSBzaXplIG9mIHRoZWlyIGhlYWRlciBjaGFpbnMgdG8gMTAyNDsg
c28NCnRoYXQgbmVzdGVkIHR1bm5lbHMgdGhhdCBmcmFnbWVudCB3aWxsIHN0aWxsIGJlIGhpZ2hs
eSBsaWtlbHkgdG8NCmhhdmUgdGhlIGVudGlyZSBoZWFkZXIgY2hhaW4gaW4gdGhlIGZpcnN0IGZy
YWdtZW50Lg0KIA0KPiBJIHVuZGVyc3Rvb2QgdGhhdCB0byBiZSB0aGUgYmFzaXMgb24gd2hpY2gg
dGhlIFdHIHJlYWNoZWQgY29uc2Vuc3VzLg0KDQpNYXliZSB0aGUgV0cgZGlkbid0IHVuZGVyc3Rh
bmQgdGhhdCBzdWNoIGEgY29uc2Vuc3VzIHdvdWxkIG1ha2UNCnR1bm5lbHMgbGVzcyByZWxpYWJs
ZSBhbmQgbGVzcyBzZWN1cmUuDQoNClRoYW5rcyAtIEZyZWQNCmZyZWQubC50ZW1wbGluQGJvZWlu
Zy5jb20NCg0KPiAgICAgQnJpYW4NCg0K

From stbryant@cisco.com  Wed Oct  9 21:32:26 2013
Return-Path: <stbryant@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 925D011E8121; Wed,  9 Oct 2013 21:32:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1qy7n4+KBMSl; Wed,  9 Oct 2013 21:32:25 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5876311E8123; Wed,  9 Oct 2013 21:32:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: "Stewart Bryant" <stbryant@cisco.com>
To: The IESG <iesg@ietf.org>
Subject: Stewart Bryant's No Objection on draft-ietf-6man-ext-transmit-04: (with COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131010043225.15919.55354.idtracker@ietfa.amsl.com>
Date: Wed, 09 Oct 2013 21:32:25 -0700
Cc: 6man-chairs@tools.ietf.org, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 10 Oct 2013 04:32:26 -0000

Stewart Bryant has entered the following ballot position for
draft-ietf-6man-ext-transmit-04: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-6man-ext-transmit/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Comment:

In section 2.1, I think that it would be helpful to the reader to use the

option name, as well as the number.



From joelja@bogus.com  Thu Oct 10 10:04:02 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F25C321F9EE9; Thu, 10 Oct 2013 10:04:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ABqLxUw36rdB; Thu, 10 Oct 2013 10:04:01 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 49A0D21F90DC; Thu, 10 Oct 2013 10:04:00 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: "Joel Jaeggli" <joelja@bogus.com>
To: The IESG <iesg@ietf.org>
Subject: Joel Jaeggli's No Objection on draft-ietf-6man-ext-transmit-04: (with COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131010170400.971.88090.idtracker@ietfa.amsl.com>
Date: Thu, 10 Oct 2013 10:04:00 -0700
Cc: 6man-chairs@tools.ietf.org, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 10 Oct 2013 17:04:02 -0000

Joel Jaeggli has entered the following ballot position for
draft-ietf-6man-ext-transmit-04: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-6man-ext-transmit/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Converting the discuss to a comment on the assumption the proposed text
will make it into the document under brian's watch.

If you need to find the transport header due to configured policy and you
can't due to being unable to parse the extensions chain your configured
action will be to drop. That perhaps weasels it's way through section 2.1
requirements but it's still quite ugly.

...
former discuss

This is a dicuss because I'd like to see if I'm in the rough in this.

Devices generally considered to be IP routers in fact are able to or find
it necessary to forward on the basis of headers other than the IP header
e.g. the transport header. By the definition applied in the problem
statement all ipv6 capable routers in the internet that  I'm aware are or
are capable of being middleboxes. =


I would welcome the existence proof of an ipv6 capable router which is
not capable of being a middlebox by the definition applied in the problem
statement.

I'm not sure that's a glaring flaw in the document but it certainly is
with our vocabulary around taxonomy if true.



From ietf-secretariat-reply@ietf.org  Thu Oct 10 11:54:52 2013
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BEA521F96B1 for <ipv6@ietfa.amsl.com>; Thu, 10 Oct 2013 11:54:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.311
X-Spam-Level: 
X-Spam-Status: No, score=-101.311 tagged_above=-999 required=5 tests=[AWL=-0.930, BAYES_00=-2.599, NO_RELAYS=-0.001, TVD_SPACE_RATIO=2.219, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KeZifZNnDTy9; Thu, 10 Oct 2013 11:54:39 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 63C3F21E80F0; Thu, 10 Oct 2013 11:53:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
To: 6man-chairs@tools.ietf.org, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org
Subject: ID Tracker State Update Notice: <draft-ietf-6man-ext-transmit-04.txt>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131010185348.971.53852.idtracker@ietfa.amsl.com>
Date: Thu, 10 Oct 2013 11:53:48 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 10 Oct 2013 18:54:52 -0000

State changed to IESG Evaluation::Revised I-D Needed from IESG Evaluation
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-6man-ext-transmi=
t/


From brian.e.carpenter@gmail.com  Thu Oct 10 20:52:34 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B6C321F970E; Thu, 10 Oct 2013 20:52:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.559
X-Spam-Level: 
X-Spam-Status: No, score=-102.559 tagged_above=-999 required=5 tests=[AWL=0.040, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QVsS5twPez2p; Thu, 10 Oct 2013 20:52:33 -0700 (PDT)
Received: from mail-pd0-x232.google.com (mail-pd0-x232.google.com [IPv6:2607:f8b0:400e:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id 809CC21E8190; Thu, 10 Oct 2013 20:52:23 -0700 (PDT)
Received: by mail-pd0-f178.google.com with SMTP id w10so3572533pde.23 for <multiple recipients>; Thu, 10 Oct 2013 20:52: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=TeFMNbHMhaAfy/fNOV8YVQ9oMB1A/1d1ZrGX4DuaU2U=; b=n9NaJMPOTCUHZpsgPcBCWtooPnyIEv22NOEJccEQPYqsmu2ffyskelx2mp4On0yD3J KHs7ZG0knbDJ2Jw9dLY/Pyv8WuEno9C0ozsd8AeCxAUbj+wf952eQaR+nk0ISbkEUQvD ygZ+XA8h+KVgF2pyEE2PRhvtWAlnJdJEU7Wav/TWq/d7GVnYjdacBQ0xuQGC4Qw16Ysf KpRHi0rrH+3+i5BeOJlr3xyAOk/amIxn5FtqNFKdtefhJynyqd5n9YZO044O/2807JBz XR51mNVnyTMVmhqYMcs3AlnVKX2g1EwUqq1sreRnTY2IW1YcEhOA41JV6M8eFCXxdA8f ynWg==
X-Received: by 10.66.141.144 with SMTP id ro16mr678865pab.173.1381463543337; Thu, 10 Oct 2013 20:52:23 -0700 (PDT)
Received: from [192.168.178.20] (167.201.69.111.dynamic.snap.net.nz. [111.69.201.167]) by mx.google.com with ESMTPSA id a6sm10016406pbr.17.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Oct 2013 20:52:22 -0700 (PDT)
Message-ID: <525775FD.3050704@gmail.com>
Date: Fri, 11 Oct 2013 16:52:29 +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: Richard Barnes <rlb@ipv.sx>
Subject: Re: Richard Barnes' No Objection on draft-ietf-6man-ext-transmit-04: (with COMMENT)
References: <20131008154401.25649.85053.idtracker@ietfa.amsl.com>
In-Reply-To: <20131008154401.25649.85053.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 6man-chairs@tools.ietf.org, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org, The IESG <iesg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Oct 2013 03:52:34 -0000

On 09/10/2013 04:44, Richard Barnes wrote:
...
> Could you provide any citations on the middle box behaviors, e.g., lack
> of support for all of 2460?

The documentation of pretty much any firewall would do it, but that gets
a bit like name-calling. The whole problem came to my attention when a
student discovered that SHIM6 is in practice undeployable across the
Internet unless both hosts are outside all enterprise firewalls.

> 10 points to the INT area for the cite to Heller :)
> 
> "... Not just a failure to recognize such a header".  
> Isn't this another Catch-22?  If a node doesn't recognize a header, how
> does it know if it's standard or not?  This also seems in contradiction
> to later guidance that unrecognized extensions may be dropped by
> default.

I think it's part of the same Catch-22 really; and yes, there's a
problem period after a new extension is defined and before it's
been implemented. Hence the warning at the end of the 3rd paragraph
here: http://tools.ietf.org/html/draft-ietf-6man-ext-transmit-04#section-3

> A flow chart or pseudo code might be useful in Section 2.1, like "if
> (known && standard) { /* policy */ }"

Can we keep that for version 2?

    Brian


From brian.e.carpenter@gmail.com  Thu Oct 10 21:15:04 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE39D21E8164 for <ipv6@ietfa.amsl.com>; Thu, 10 Oct 2013 21:15:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.561
X-Spam-Level: 
X-Spam-Status: No, score=-102.561 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KeGB1dWLXe4s for <ipv6@ietfa.amsl.com>; Thu, 10 Oct 2013 21:15:03 -0700 (PDT)
Received: from mail-pa0-x230.google.com (mail-pa0-x230.google.com [IPv6:2607:f8b0:400e:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id EAD5C11E811D for <ipv6@ietf.org>; Thu, 10 Oct 2013 21:14:58 -0700 (PDT)
Received: by mail-pa0-f48.google.com with SMTP id bj1so3761039pad.21 for <ipv6@ietf.org>; Thu, 10 Oct 2013 21:14: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=3tYMD3MnkH9AArl13Wr7FBPTx0x3MBUWv/kIHinEBj4=; b=UTuBHMEupdgQ8LjC8KWJb0smKaDxXATm04t/6sfQeKLVcp3pSAyfvvCyei+V1VIdn5 CVJIxLEcRyjuraqAUlx7TSH7CY8ZSXhDjMOwRaZiBHO9NWFnAC5qdBYlFuhW0AREcPRc drherF0IiZYmzIzNNCRHLdfm2NkNnK0hVT+TQOOeZjWH9vWEu+Mz8vBnlQWXcbKvLXJG exbz+FVA651hjvKdPStZHuvYxhfR2EMFa2bkvwBR6GEqECeaLhqC6nM4/o2xHfeNPSS9 EgjqHfPhj8YAMCvoW3p9Q0SMyAkObbjIc9TmlbIueUbTWNQjmIML+Rd/d5Leh1r2N6GU XZkQ==
X-Received: by 10.66.119.78 with SMTP id ks14mr19199779pab.140.1381464898649;  Thu, 10 Oct 2013 21:14:58 -0700 (PDT)
Received: from [192.168.178.20] (167.201.69.111.dynamic.snap.net.nz. [111.69.201.167]) by mx.google.com with ESMTPSA id sb9sm56784336pbb.0.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Oct 2013 21:14:57 -0700 (PDT)
Message-ID: <52577B48.8030901@gmail.com>
Date: Fri, 11 Oct 2013 17:15:04 +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: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Subject: Re: Adrian Farrel's No Objection on draft-ietf-6man-ext-transmit-04: (with COMMENT)
References: <20131007144327.16131.88173.idtracker@ietfa.amsl.com>	<Pine.LNX.4.64.1310070914240.13173@shell4.bayarea.net>	<52530921.3060202@gmail.com>	<Pine.LNX.4.64.1310071315370.13828@shell4.bayarea.net> <52534F31.2020906@gmail.com> <2134F8430051B64F815C691A62D9831811DA86@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831811DA86@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "C. M. Heard" <heard@pobox.com>, "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, "draft-ietf-6man-ext-transmit@tools.ietf.org" <draft-ietf-6man-ext-transmit@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, Adrian Farrel <adrian@olddog.co.uk>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Oct 2013 04:15:04 -0000

Fred,

On 09/10/2013 04:28, Templin, Fred L wrote:
...
> When Wireshark encounters a header type 253 or 254, it assumes it is
> an unknown extension header of length 8 bytes, then skips ahead and
> attempts to parse anything that follows as additional headers.

They must have just made that up; there's no justification for it.
It could be an unknown extension header of unknown length, or it
could be an unknown payload of unknown length. In real life
I'd expect firewalls to default-drop such packets.

We'll note this issue in the Security Considerations.

    Brian

From brian.e.carpenter@gmail.com  Thu Oct 10 21:25:09 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36B2711E811D; Thu, 10 Oct 2013 21:25:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.562
X-Spam-Level: 
X-Spam-Status: No, score=-102.562 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rm9TqGUyGDUs; Thu, 10 Oct 2013 21:25:01 -0700 (PDT)
Received: from mail-pb0-x229.google.com (mail-pb0-x229.google.com [IPv6:2607:f8b0:400e:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id C6EEE21E812A; Thu, 10 Oct 2013 21:24:49 -0700 (PDT)
Received: by mail-pb0-f41.google.com with SMTP id rp2so3638338pbb.28 for <multiple recipients>; Thu, 10 Oct 2013 21:24:49 -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=9kzB8EO3d3P9YP4LLaz/5mzfSqvNZrKGRM7AJqY+/8M=; b=YHAxKcKYdNVXSoKV3zuGzpbAkAnFFretztf28gBqZ0xWpl0fXg05ZxGQsBaaBsPqYb FIASbF5mQzpoesbwxpBZ5K8MDi2LNrj8gRGXvtL78vmmGD+ktjkh8+vl2vLRuy9Iasci G9KSVady3EvM2y40VQq92zcRxTgJ4h4/ud29g5tlGpwbvwnI76TFqXSowE3bbF3kljM+ Njxhj7CRocfdr9T8XJ594uWZVSe0+bLXY86YIvmTyH65lqs/2mnNoZ8hAVnp1JMLEf0N Da4a/dNE0mt/XYKAHNsUilvo+u+bH2qHn0MZxzwu0+lVrzZ36ZJviQnFNhPuh9+ziPEq fejQ==
X-Received: by 10.66.192.132 with SMTP id hg4mr19584825pac.84.1381465489589; Thu, 10 Oct 2013 21:24:49 -0700 (PDT)
Received: from [192.168.178.20] (167.201.69.111.dynamic.snap.net.nz. [111.69.201.167]) by mx.google.com with ESMTPSA id yh1sm56802011pbc.21.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Oct 2013 21:24:48 -0700 (PDT)
Message-ID: <52577D97.1010009@gmail.com>
Date: Fri, 11 Oct 2013 17:24:55 +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: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Stephen Farrell's No Objection on draft-ietf-6man-ext-transmit-04: (with COMMENT)
References: <20131008103111.25649.95882.idtracker@ietfa.amsl.com>
In-Reply-To: <20131008103111.25649.95882.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 6man-chairs@tools.ietf.org, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org, The IESG <iesg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Oct 2013 04:25:09 -0000

On 08/10/2013 23:31, Stephen Farrell wrote:
...
> - 2.1 says nodes SHOULD forward rfc4727 experimental
> headers, but earlier said that its ok (nodes MAY) default
> to not forwarding packets with experimental headers. I
> think you need to add an "unless otherwise stated here"
> to the statement about defaults for experimental headers.

I must be missing something, but I can't find an inconsistency.

> 
> - section 4: Is it wise to ask IANA to "redirect" users
> from one (empty) registry to another? That could be the
> start of a slippery slope turning IANA registries into a
> miasma of hypertext;-) Maybe it'd be better to ask that
> IANA mark that registry as having being replaced by this
> new one. Also - what if someone else asks IANA to add an
> entry to the currently empty registry but not the new one
> - is it clear what should happen in that case?

It does need to be clear that the old registry is closed,
but we have to leave a pointer because it's referred to
elsewhere. I think IANA can figure it out, but we should
add "close to new entries".

I think we are already in a miasma of hypertext.

     Brian
> 
> 
> 

From v6ops@globis.net  Fri Oct 11 00:48:53 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1E1121E809C; Fri, 11 Oct 2013 00:48:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mJPt+iWMOpul; Fri, 11 Oct 2013 00:48:53 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id AB32D21E8190; Fri, 11 Oct 2013 00:48:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 986BF870077; Fri, 11 Oct 2013 09:48:47 +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 22SVJ3o5CgrH; Fri, 11 Oct 2013 09:48:47 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 63527870056; Fri, 11 Oct 2013 09:48:47 +0200 (CEST)
Message-ID: <5257AD5E.9090806@globis.net>
Date: Fri, 11 Oct 2013 09:48:46 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, brian.e.carpenter@gmail.com
Subject: Re: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 6man Mailing List <ipv6@ietf.org>, ietf@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Oct 2013 07:48:54 -0000

Templin, Fred L wrote:
> Hi Brian,
>
> Responding in a slightly re-arranged order:
>
>> The problem is that you are asserting that middleboxes that a tunnel
>> passes through are expected to examine the complete header chain of
>> the encapsulated packet even if the encapsulated packet is a fragment.
> Yes, but change "are expected to" to "should be able to".

I personally don't see this going anywhere.

Unless you specifically define what is a "tunnel" and you specifically
define a maximum depth of nesting.

The term Upper-Layer Protocol (ULP) is also itself a vague term IMHO
since the value of the "IPv6 next header" is taken from the same code
space as the ULP header values, and there's no specific marker or
"header length" field in IPv6 that explicitly marks a point as "This is
the end of the IPv6 header chain in all circumstances: stop header
parsing here."

Ok, there's a bunch of current code-points that are today considered as
valid ULP's or next-header values, but that is neither time invariant
nor exhaustive, so solving this issue via a registry means there will
always be middlebox code in the wild that lags any updates.

These middleboxes won't be able to differentiate between an unknown ULP,
and an unknown IPv6 next-header. That potentially makes a default pass
or drop decision awkward.

If it's so important to be able to differentiate between what is an ULP
and what is a next header, and we can't reliably do that today, maybe
that's a fundamental flaw in IPv6 that should be addressed.


>
>> I think that's an unreasonable expectation. A reasonable expectation
>> is that middleboxes should identify the encapsulated packet as
>> a payload that they cannot analyse, and let it go (unless they
>> have a policy setting to drop tunnelled packets, which is a
>> different discussion).
> But why? If headers beyond the first IPv6 encapsulation header are
> available in the clear, the middlebox should be able to parse them
> if it wants to. Wireshark already does exactly that - it keeps on
> parsing beyond the first encapsulation header up to and including
> the true ULP header. And, if Wireshark can do it, so can any other
> middlebox that believes security would be improved by continuing
> to parse the entire chain - whether or not there is a standard
> saying it must not do so.

Because it leaves open the possibility for an attacker to apply the
obfuscation we seek to limit.


> Parsing the additional headers beyond the first encapsulation header
> provides defense-in-depth. Perimeter middleboxes can then weed out
> the bad stuff without either allowing the bad stuff to penetrate more
> deeply into the organization or dropping good stuff that should be
> allowed through.


There's also a myriad of tunneling technology out there.

Again, what is an ULP? Where do you stop parsing?

Is GRE a tunnel or an ULP? (GRE can run over almost anything)
Is SSH an ULP or a tunnel? (port tunneling)
Is Teredo a tunnel or is it an ULP (UDP) or both?
GRE/ LT2P over HTTP anyone?

The notion of "perimeter" is moveable in the presence of such tunnels.

Presumably there comes a point where the tunnel is terminated and the
transported packet is de-encapsulated, and that IMHO forms another
perimeter where you'd anyway have to apply further security checks.

I think the draft does what it can in a pragmatic manner, but might
benefit from some acknowledgement that this security approach of
applying parsing at a single perimeter can never ever catch all variants
of transporting FOO over BAR.

IMHO It's only at the moment of de-encapsulation that the full semantics
of the payload are revealed in these modern times of "everything
transported over HTTP".




>> Since the problem recurses as we tunnel tunnels, I don't see how any
>> finite limit can solve the problem. 1280 itself is a pragmatic choice
>> of "a bit shorter than 1500".

Agreed.

> The 1280 is assuming that all links in the path have a 1500 MTU and
> so RFC2460 allowed (1500 - 1280) = 220 bytes for additional IPv6
> headers added by nested tunnels without incurring fragmentation.
> I am asserting instead that we have to allow for paths that include
> links with a 1280 MTU and so tunnels will have to fragment over
> such paths.
>
> That means that the first fragmenting tunnel would have room for
> 1240 in the first fragment, the second fragmenting tunnel would
> have room for 1200 in the first fragment, etc. That is why I would
> prefer that hosts limit the size of their header chains to 1024; so
> that nested tunnels that fragment will still be highly likely to
> have the entire header chain in the first fragment.
>  
>> I understood that to be the basis on which the WG reached consensus.
> Maybe the WG didn't understand that such a consensus would make
> tunnels less reliable and less secure.
>
> Thanks - Fred
> fred.l.templin@boeing.com
>
>>     Brian
>  


-- 
Regards,
RayH


From fgont@si6networks.com  Fri Oct 11 01:36:14 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E99D921E80C7; Fri, 11 Oct 2013 01:36:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UvEwTaGLwDdB; Fri, 11 Oct 2013 01:36:14 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 5D7B021E80C1; Fri, 11 Oct 2013 01:36:13 -0700 (PDT)
Received: from 17-153-16-190.fibertel.com.ar ([190.16.153.17] helo=[192.168.1.193]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1VUYCb-0007iu-Dz; Fri, 11 Oct 2013 10:36:05 +0200
Message-ID: <5257B870.1060003@si6networks.com>
Date: Fri, 11 Oct 2013 05:36:00 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Ray Hunter <v6ops@globis.net>,  "Templin, Fred L" <Fred.L.Templin@boeing.com>, brian.e.carpenter@gmail.com
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com>	<2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com>	<2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com>	<9300F272-E282-41C3-9DA8-59134B975FC7@employees.org>	<9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com>	<2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com>	<D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org>	<2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com>	<E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org>	<2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com>	<5255D6EE.4050300@gmail.com>	<2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net>
In-Reply-To: <5257AD5E.9090806@globis.net>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 6man Mailing List <ipv6@ietf.org>, ietf@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Oct 2013 08:36:15 -0000

On 10/11/2013 04:48 AM, Ray Hunter wrote:
> 
> I think the draft does what it can in a pragmatic manner, but might
> benefit from some acknowledgement that this security approach of
> applying parsing at a single perimeter can never ever catch all variants
> of transporting FOO over BAR.

FWIW, my idea of the I-D is that it says "look, if you don't put all
this info into the first fragment, it's extremely likely that your
packets will be dropped". That doesn't mean that a middle-box may want
to look further. But looking further might imply
reassemble-inspect-and-refragment... or even reassemble the TCP stream
(e.g. think about a SSL/TCP-based VPN...)

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





From internet-drafts@ietf.org  Fri Oct 11 04:43:54 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C67521E80E4; Fri, 11 Oct 2013 04:43:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.574
X-Spam-Level: 
X-Spam-Status: No, score=-102.574 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b5bHAwUkwLLy; Fri, 11 Oct 2013 04:43:53 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BFE0621E80E9; Fri, 11 Oct 2013 04:43:49 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-stable-privacy-addresses-14.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131011114349.4950.70712.idtracker@ietfa.amsl.com>
Date: Fri, 11 Oct 2013 04:43:49 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Oct 2013 11:43:54 -0000

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           : A Method for Generating Semantically Opaque Interface Id=
entifiers with IPv6 Stateless Address Autoconfiguration (SLAAC)
	Author(s)       : Fernando Gont
	Filename        : draft-ietf-6man-stable-privacy-addresses-14.txt
	Pages           : 26
	Date            : 2013-10-11

Abstract:
   This document specifies a method for generating IPv6 Interface
   Identifiers to be used with IPv6 Stateless Address Autoconfiguration
   (SLAAC), such that addresses configured using this method are stable
   within each subnet, but the Interface Identifier changes when hosts
   move from one network to another.  This method is meant to be an
   alternative to generating Interface Identifiers based on hardware
   addresses (e.g., IEEE LAN MAC addresses), such that the benefits of
   stable addresses can be achieved without sacrificing the privacy of
   users.  The method specified in this document applies to all prefixes
   a host may be employing, including link-local, global, and unique-
   local addresses.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-stable-privacy-addresses-14

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-stable-privacy-addresses=
-14


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 stephen.farrell@cs.tcd.ie  Fri Oct 11 05:13:48 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63C8821E80FE; Fri, 11 Oct 2013 05:13:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id glAzC7-ZU2JW; Fri, 11 Oct 2013 05:13:42 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 97DB221E80FB; Fri, 11 Oct 2013 05:13:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id DC97EBE50; Fri, 11 Oct 2013 13:13:38 +0100 (IST)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0I9lEFx71U9j; Fri, 11 Oct 2013 13:13:38 +0100 (IST)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 899DCBE4D; Fri, 11 Oct 2013 13:13:38 +0100 (IST)
Message-ID: <5257EB74.9070309@cs.tcd.ie>
Date: Fri, 11 Oct 2013 13:13:40 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Stephen Farrell's No Objection on draft-ietf-6man-ext-transmit-04: (with COMMENT)
References: <20131008103111.25649.95882.idtracker@ietfa.amsl.com> <52577D97.1010009@gmail.com>
In-Reply-To: <52577D97.1010009@gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 6man-chairs@tools.ietf.org, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org, The IESG <iesg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Oct 2013 12:13:48 -0000

On 10/11/2013 05:24 AM, Brian E Carpenter wrote:
> On 08/10/2013 23:31, Stephen Farrell wrote:
> ...
>> - 2.1 says nodes SHOULD forward rfc4727 experimental
>> headers, but earlier said that its ok (nodes MAY) default
>> to not forwarding packets with experimental headers. I
>> think you need to add an "unless otherwise stated here"
>> to the statement about defaults for experimental headers.
> 
> I must be missing something, but I can't find an inconsistency.

Or maybe I misread it.

I read it as saying "nodes MAY default to not forwarding
packets with experimental headers" and as also saying
"nodes SHOULD forward 4727 experimental headers."

My suggestion is to say "nodes MAY default to not forwarding
packets with experimental headers except as noted below"
since otherwise developers might just see the MAY and
ignore the SHOULD.

That's not quite fixing an inconsistency but more just
flagging that there's a SHOULD later for 4727. But if you
prefer it as-is that's fine.

Cheers,
S

> 
>>
>> - section 4: Is it wise to ask IANA to "redirect" users
>> from one (empty) registry to another? That could be the
>> start of a slippery slope turning IANA registries into a
>> miasma of hypertext;-) Maybe it'd be better to ask that
>> IANA mark that registry as having being replaced by this
>> new one. Also - what if someone else asks IANA to add an
>> entry to the currently empty registry but not the new one
>> - is it clear what should happen in that case?
> 
> It does need to be clear that the old registry is closed,
> but we have to leave a pointer because it's referred to
> elsewhere. I think IANA can figure it out, but we should
> add "close to new entries".
> 
> I think we are already in a miasma of hypertext.
> 
>      Brian
>>
>>
>>

From otroan@employees.org  Fri Oct 11 05:57:27 2013
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2866321E81B2 for <ipv6@ietfa.amsl.com>; Fri, 11 Oct 2013 05:57:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aVjTi+LhC-lX for <ipv6@ietfa.amsl.com>; Fri, 11 Oct 2013 05:57:25 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) by ietfa.amsl.com (Postfix) with ESMTP id C377721E81AF for <ipv6@ietf.org>; Fri, 11 Oct 2013 05:57:23 -0700 (PDT)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id 448FC601C; Fri, 11 Oct 2013 05:57:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :content-type:subject:date:message-id:cc:to:mime-version; s= selector1; bh=JxzHolM8HhRwB9vZsIlEM5NNOqM=; b=L2GWr3X/Ivx8SJHDTR gAxZLVLhy6bAUH2zRcNjja1tLqowQBZGrWyYoAui3WvyzRVmjTjQWSfLDi8/7qQj OWtya8tFoetKPrcGUyPglwuVSdm780e+nQeKPcHglIbpQyam0lSDkP+/cc7yL46v H0zTrk2hdpTWROS5OCYO9LrSU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :content-type:subject:date:message-id:cc:to:mime-version; q=dns; s=selector1; b=BwJoXPU5LemsBeKQEJGUcQka03F7GKoRefU0s7qyTa7HEEmk yvJkNfiLPmR2qp+VOxBST81THnpjN8/a8oF4Ih3RoserQ/hwsuUfyzxRMRU/viet mGLzbT4yJqgL6LOJcbqll2cKC/pK3XN6mwrPPQKFUZsLdLx77dB82u+SNxk=
Received: from [10.16.0.33] (unknown [195.159.143.154]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id A4F655F39; Fri, 11 Oct 2013 05:57:22 -0700 (PDT)
From: Ole Troan <otroan@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_490247D5-3C2E-47AC-BD4F-E4005CBB88D0"; protocol="application/pgp-signature"; micalg=pgp-sha512
Subject: 6man IETF 88 Call for agenda items
Date: Fri, 11 Oct 2013 14:57:19 +0200
Message-Id: <0CF6A0CC-513E-4348-BA63-06720F8C7FCB@employees.org>
To: 6man WG <ipv6@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
X-Mailer: Apple Mail (2.1510)
Cc: 6man Chairs <6man-chairs@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Oct 2013 12:57:27 -0000

--Apple-Mail=_490247D5-3C2E-47AC-BD4F-E4005CBB88D0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

We have asked for a two and a half hour slot in Vancouver for the 6MAN =
working group.
The preliminary agenda has given us the 0900-1130 Monday morning slot.

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 about 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 2013-10-25 and also note the draft =
deadline for IETF88:
2013-10-21 (Monday): Internet Draft submission cut-off (for all drafts, =
including -00) by UTC 24:00

Regards,

Bob & Ole

--Apple-Mail=_490247D5-3C2E-47AC-BD4F-E4005CBB88D0
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

iQEcBAEBCgAGBQJSV/WwAAoJEFuJXizso86gLVoIAMq2L7RNSK67ZVtFjmSRUMHL
4nf0ld41Xsz4k4RKsjOqiDVY5bcJRk3KaafULjnoxuiTSUEKsyYrLMXihmclomby
RqKd5oTgGV6lYX00lWIaxiozruiwcz3lDONI4Sf0clSGn9qb9MDn7bZ2tPq9tr4s
VyBxKCeHILi3uT8TMrUEUcnoSY+8qmps6xwSNm6+Oa5U+cJsjpLqnm/reYPodh0X
mpEQlmY5C26QbbTRs+p8Ti+wS/ZtarLUxUAYrn+zvqBttUJr/60HH4W3k7+hGBjC
LZQHTZqqLB+pNhzD/FheOnrJyUxjTWbhiRAafyJQsnB30ZdyjyK9McS9QFRm7N4=
=fV78
-----END PGP SIGNATURE-----

--Apple-Mail=_490247D5-3C2E-47AC-BD4F-E4005CBB88D0--

From Fred.L.Templin@boeing.com  Fri Oct 11 08:33:28 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2B7311E81CE; Fri, 11 Oct 2013 08:33:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.365
X-Spam-Level: 
X-Spam-Status: No, score=-6.365 tagged_above=-999 required=5 tests=[AWL=0.234,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1+MSz2AHkRZr; Fri, 11 Oct 2013 08:33:22 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (stl-mbsout-01.boeing.com [130.76.96.169]) by ietfa.amsl.com (Postfix) with ESMTP id E03DA11E820C; Fri, 11 Oct 2013 08:33:20 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9BFXJvI003282; Fri, 11 Oct 2013 10:33:20 -0500
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9BFXI7a003278 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 11 Oct 2013 10:33:19 -0500
Received: from XCH-EXCO-103.nw.nos.boeing.com (130.247.25.37) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Fri, 11 Oct 2013 08:33:18 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-EXCO-103.nw.nos.boeing.com ([fe80::7434:66d:a0ba:2234%15]) with mapi id 14.03.0158.001; Fri, 11 Oct 2013 08:33:17 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ray Hunter <v6ops@globis.net>, "brian.e.carpenter@gmail.com" <brian.e.carpenter@gmail.com>
Subject: RE: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOxlZjF9Ic7sRuGU+T9Pt4WN8/H5nvmo2Q
Date: Fri, 11 Oct 2013 15:33:17 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812C105@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net>
In-Reply-To: <5257AD5E.9090806@globis.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Oct 2013 15:33:28 -0000

Hi Ray,

> -----Original Message-----
> From: Ray Hunter [mailto:v6ops@globis.net]
> Sent: Friday, October 11, 2013 12:49 AM
> To: Templin, Fred L; brian.e.carpenter@gmail.com
> Cc: ietf@ietf.org; 6man Mailing List
> Subject: Re: RE: Last Call: <draft-ietf-6man-oversized-header-chain-
> 08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed
> Standard
>=20
> Templin, Fred L wrote:
> > Hi Brian,
> >
> > Responding in a slightly re-arranged order:
> >
> >> The problem is that you are asserting that middleboxes that a tunnel
> >> passes through are expected to examine the complete header chain of
> >> the encapsulated packet even if the encapsulated packet is a
> fragment.
> > Yes, but change "are expected to" to "should be able to".
>=20
> I personally don't see this going anywhere.
>=20
> Unless you specifically define what is a "tunnel" and you specifically
> define a maximum depth of nesting.
>=20
> The term Upper-Layer Protocol (ULP) is also itself a vague term IMHO
> since the value of the "IPv6 next header" is taken from the same code
> space as the ULP header values, and there's no specific marker or
> "header length" field in IPv6 that explicitly marks a point as "This is
> the end of the IPv6 header chain in all circumstances: stop header
> parsing here."
>=20
> Ok, there's a bunch of current code-points that are today considered as
> valid ULP's or next-header values, but that is neither time invariant
> nor exhaustive, so solving this issue via a registry means there will
> always be middlebox code in the wild that lags any updates.
>=20
> These middleboxes won't be able to differentiate between an unknown
> ULP,
> and an unknown IPv6 next-header. That potentially makes a default pass
> or drop decision awkward.
>=20
> If it's so important to be able to differentiate between what is an ULP
> and what is a next header, and we can't reliably do that today, maybe
> that's a fundamental flaw in IPv6 that should be addressed.
>=20
>=20
> >
> >> I think that's an unreasonable expectation. A reasonable expectation
> >> is that middleboxes should identify the encapsulated packet as
> >> a payload that they cannot analyse, and let it go (unless they
> >> have a policy setting to drop tunnelled packets, which is a
> >> different discussion).
> > But why? If headers beyond the first IPv6 encapsulation header are
> > available in the clear, the middlebox should be able to parse them
> > if it wants to. Wireshark already does exactly that - it keeps on
> > parsing beyond the first encapsulation header up to and including
> > the true ULP header. And, if Wireshark can do it, so can any other
> > middlebox that believes security would be improved by continuing
> > to parse the entire chain - whether or not there is a standard
> > saying it must not do so.
>=20
> Because it leaves open the possibility for an attacker to apply the
> obfuscation we seek to limit.
>=20
>=20
> > Parsing the additional headers beyond the first encapsulation header
> > provides defense-in-depth. Perimeter middleboxes can then weed out
> > the bad stuff without either allowing the bad stuff to penetrate more
> > deeply into the organization or dropping good stuff that should be
> > allowed through.
>=20
>=20
> There's also a myriad of tunneling technology out there.
>=20
> Again, what is an ULP? Where do you stop parsing?

The middlebox stops parsing when it decides it has seen enough. With
Wireshark at least, it blasts right through encapsulating IP headers
and continues up to and including the ultimate TCP/UDP/ICMP etc.
header inserted by the original host. The goal is to give the
middlebox enough information so that it can parse as deeply into
the headers as it wants to.

> Is GRE a tunnel or an ULP? (GRE can run over almost anything)
> Is SSH an ULP or a tunnel? (port tunneling)
> Is Teredo a tunnel or is it an ULP (UDP) or both?
> GRE/ LT2P over HTTP anyone?
>=20
> The notion of "perimeter" is moveable in the presence of such tunnels.

We will want for middleboxes at outer perimeters to be able to parse
as many headers as they want to before releasing the packet to
middleboxes at inner perimenters. Otherwise, bad stuff can get past
the outermost perimeters and waste bandwidth and/or cause havoc
within the protected zone.=20

> Presumably there comes a point where the tunnel is terminated and the
> transported packet is de-encapsulated, and that IMHO forms another
> perimeter where you'd anyway have to apply further security checks.

Nested tunnels give you perimeters within perimeters, yes. But, we
will want the outer perimeters to be able to parse as deeply as
they want to before passing on to an inner perimeter.

> I think the draft does what it can in a pragmatic manner, but might
> benefit from some acknowledgement that this security approach of
> applying parsing at a single perimeter can never ever catch all
> variants
> of transporting FOO over BAR.
>=20
> IMHO It's only at the moment of de-encapsulation that the full
> semantics
> of the payload are revealed in these modern times of "everything
> transported over HTTP".
>=20
>=20
>=20
>=20
> >> Since the problem recurses as we tunnel tunnels, I don't see how any
> >> finite limit can solve the problem. 1280 itself is a pragmatic
> choice
> >> of "a bit shorter than 1500".
>=20
> Agreed.

I guess I will have to repeat myself from what I said several
months ago. The 1280 came from a desire to have multiple nested
tunnels without requiring the tunnels to fragment since the
underlying links presumably all configure a 1500 MTU. But, what
would that look like in real life?

- The first tunnel would have to configure a 1280 MTU so that its
  encapsulated packets emerged as 1320
- the second tunnel would have to configure a 1320 MTU so that its
  encapsulated  packets emerged as 1360
- the third tunnel would have to configure a 1360 MTU so that its
  encapsulated packets emerged as 1400
- etc.

But, in real life, it is not possible to assume that we can lay
hands on all tunnel endpoints so as to carefully set MTUs that
satisfy the nesting level - and, when multiple administrative
domains are involved, it can't be done at all.

Please go back in the archives to where I posted the derivation
of the 1280 minMTU (circa 1997):

http://www.ietf.org/mail-archive/web/ipv6/current/msg18462.html

My conclusion is that the 1280/1500 was well intentioned, but
unfortunately not very well thought out.

Thanks - Fred
fred.l.templin@boeing.com

> > The 1280 is assuming that all links in the path have a 1500 MTU and
> > so RFC2460 allowed (1500 - 1280) =3D 220 bytes for additional IPv6
> > headers added by nested tunnels without incurring fragmentation.
> > I am asserting instead that we have to allow for paths that include
> > links with a 1280 MTU and so tunnels will have to fragment over
> > such paths.
> >
> > That means that the first fragmenting tunnel would have room for
> > 1240 in the first fragment, the second fragmenting tunnel would
> > have room for 1200 in the first fragment, etc. That is why I would
> > prefer that hosts limit the size of their header chains to 1024; so
> > that nested tunnels that fragment will still be highly likely to
> > have the entire header chain in the first fragment.
> >
> >> I understood that to be the basis on which the WG reached consensus.
> > Maybe the WG didn't understand that such a consensus would make
> > tunnels less reliable and less secure.
> >
> > Thanks - Fred
> > fred.l.templin@boeing.com
> >
> >>     Brian
> >
>=20
>=20
> --
> Regards,
> RayH


From Fred.L.Templin@boeing.com  Fri Oct 11 08:36:11 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DB0B11E8235; Fri, 11 Oct 2013 08:36:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.388
X-Spam-Level: 
X-Spam-Status: No, score=-6.388 tagged_above=-999 required=5 tests=[AWL=0.211,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XQQCUfrh1Zty; Fri, 11 Oct 2013 08:36:05 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) by ietfa.amsl.com (Postfix) with ESMTP id EFF8011E821F; Fri, 11 Oct 2013 08:36:04 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9BFa3O7009490; Fri, 11 Oct 2013 10:36:04 -0500
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9BFZu2i009356 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 11 Oct 2013 10:36:03 -0500
Received: from XCH-BLV-305.nw.nos.boeing.com (130.247.25.217) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Fri, 11 Oct 2013 08:36:00 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-BLV-305.nw.nos.boeing.com ([169.254.5.85]) with mapi id 14.03.0158.001; Fri, 11 Oct 2013 08:36:00 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Fernando Gont <fgont@si6networks.com>, Ray Hunter <v6ops@globis.net>, "brian.e.carpenter@gmail.com" <brian.e.carpenter@gmail.com>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOxlzzebc9KTehbEGO6mhunuAlj5nvofSw
Date: Fri, 11 Oct 2013 15:36:00 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com>
In-Reply-To: <5257B870.1060003@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Oct 2013 15:36:11 -0000

Hi Fernando,

> -----Original Message-----
> From: Fernando Gont [mailto:fgont@si6networks.com]
> Sent: Friday, October 11, 2013 1:36 AM
> To: Ray Hunter; Templin, Fred L; brian.e.carpenter@gmail.com
> Cc: 6man Mailing List; ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> On 10/11/2013 04:48 AM, Ray Hunter wrote:
> >
> > I think the draft does what it can in a pragmatic manner, but might
> > benefit from some acknowledgement that this security approach of
> > applying parsing at a single perimeter can never ever catch all
> variants
> > of transporting FOO over BAR.
>=20
> FWIW, my idea of the I-D is that it says "look, if you don't put all
> this info into the first fragment, it's extremely likely that your
> packets will be dropped". That doesn't mean that a middle-box may want
> to look further. But looking further might imply
> reassemble-inspect-and-refragment... or even reassemble the TCP stream
> (e.g. think about a SSL/TCP-based VPN...)

We definitely don't want that. That is why we would prefer for
the entire header chain (starting from the outermost IP header
up to and including the headers inserted by the original host)
to fit within the first fragment even if there are multiple
encapsulations on the path.

Thanks - Fred
fred.l.templin@boeing.com

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


From Fred.L.Templin@boeing.com  Fri Oct 11 08:55:18 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87C3A21F9E9F for <ipv6@ietfa.amsl.com>; Fri, 11 Oct 2013 08:55:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.407
X-Spam-Level: 
X-Spam-Status: No, score=-6.407 tagged_above=-999 required=5 tests=[AWL=0.192,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fdkKaR1YoAnj for <ipv6@ietfa.amsl.com>; Fri, 11 Oct 2013 08:55:12 -0700 (PDT)
Received: from blv-mbsout-01.boeing.com (blv-mbsout-01.boeing.com [130.76.32.231]) by ietfa.amsl.com (Postfix) with ESMTP id 6AE0D21F9CF3 for <ipv6@ietf.org>; Fri, 11 Oct 2013 08:55:06 -0700 (PDT)
Received: from blv-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9BFt3nq030655 for <ipv6@ietf.org>; Fri, 11 Oct 2013 08:55:03 -0700
Received: from XCH-PHX-512.sw.nos.boeing.com (xch-phx-512.sw.nos.boeing.com [10.57.37.29]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9BFt2JO030649 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Fri, 11 Oct 2013 08:55:02 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-PHX-512.sw.nos.boeing.com ([169.254.12.124]) with mapi id 14.03.0158.001; Fri, 11 Oct 2013 08:55:02 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: Adrian Farrel's No Objection on draft-ietf-6man-ext-transmit-04: (with COMMENT)
Thread-Topic: Adrian Farrel's No Objection on draft-ietf-6man-ext-transmit-04: (with COMMENT)
Thread-Index: AQHOxjiFIvFLssN0lkiTRxOL+qsuc5nvpuMQ
Date: Fri, 11 Oct 2013 15:55:01 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812C178@XCH-BLV-504.nw.nos.boeing.com>
References: <20131007144327.16131.88173.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1310070914240.13173@shell4.bayarea.net> <52530921.3060202@gmail.com> <Pine.LNX.4.64.1310071315370.13828@shell4.bayarea.net> <52534F31.2020906@gmail.com> <2134F8430051B64F815C691A62D9831811DA86@XCH-BLV-504.nw.nos.boeing.com> <52577B48.8030901@gmail.com>
In-Reply-To: <52577B48.8030901@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "C. M. Heard" <heard@pobox.com>, "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, "draft-ietf-6man-ext-transmit@tools.ietf.org" <draft-ietf-6man-ext-transmit@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, Adrian Farrel <adrian@olddog.co.uk>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Oct 2013 15:55:18 -0000

SGkgQnJpYW4sDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogQnJpYW4g
RSBDYXJwZW50ZXIgW21haWx0bzpicmlhbi5lLmNhcnBlbnRlckBnbWFpbC5jb21dDQo+IFNlbnQ6
IFRodXJzZGF5LCBPY3RvYmVyIDEwLCAyMDEzIDk6MTUgUE0NCj4gVG86IFRlbXBsaW4sIEZyZWQg
TA0KPiBDYzogQy4gTS4gSGVhcmQ7IDZtYW4tY2hhaXJzQHRvb2xzLmlldGYub3JnOyBBZHJpYW4g
RmFycmVsOyBkcmFmdC1pZXRmLQ0KPiA2bWFuLWV4dC10cmFuc21pdEB0b29scy5pZXRmLm9yZzsg
aXB2NkBpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTogQWRyaWFuIEZhcnJlbCdzIE5vIE9iamVjdGlv
biBvbiBkcmFmdC1pZXRmLTZtYW4tZXh0LQ0KPiB0cmFuc21pdC0wNDogKHdpdGggQ09NTUVOVCkN
Cj4gDQo+IEZyZWQsDQo+IA0KPiBPbiAwOS8xMC8yMDEzIDA0OjI4LCBUZW1wbGluLCBGcmVkIEwg
d3JvdGU6DQo+IC4uLg0KPiA+IFdoZW4gV2lyZXNoYXJrIGVuY291bnRlcnMgYSBoZWFkZXIgdHlw
ZSAyNTMgb3IgMjU0LCBpdCBhc3N1bWVzIGl0IGlzDQo+ID4gYW4gdW5rbm93biBleHRlbnNpb24g
aGVhZGVyIG9mIGxlbmd0aCA4IGJ5dGVzLCB0aGVuIHNraXBzIGFoZWFkIGFuZA0KPiA+IGF0dGVt
cHRzIHRvIHBhcnNlIGFueXRoaW5nIHRoYXQgZm9sbG93cyBhcyBhZGRpdGlvbmFsIGhlYWRlcnMu
DQo+IA0KPiBUaGV5IG11c3QgaGF2ZSBqdXN0IG1hZGUgdGhhdCB1cDsgdGhlcmUncyBubyBqdXN0
aWZpY2F0aW9uIGZvciBpdC4NCj4gSXQgY291bGQgYmUgYW4gdW5rbm93biBleHRlbnNpb24gaGVh
ZGVyIG9mIHVua25vd24gbGVuZ3RoLCBvciBpdA0KPiBjb3VsZCBiZSBhbiB1bmtub3duIHBheWxv
YWQgb2YgdW5rbm93biBsZW5ndGguIEluIHJlYWwgbGlmZQ0KPiBJJ2QgZXhwZWN0IGZpcmV3YWxs
cyB0byBkZWZhdWx0LWRyb3Agc3VjaCBwYWNrZXRzLg0KDQpJdCBjb3VsZCBiZSB0aGF0IFdpcmVz
aGFyayBoYXMgc29tZSBraW5kIG9mIGluZmVyZW5jZSBlbmdpbmUgdGhhdA0Kc2F5czogImxldCdz
IGxvb2sgYWhlYWQgYW5kIHNlZSBpZiB0aGUgbmV4dCBvY3RldCBsb29rcyBsaWtlIGFub3RoZXIN
Ck5FWFRIRFIgZmllbGQsIGFuZCBpZiBzbyBrZWVwIG9uIHBsb3dpbmcgdGhyb3VnaCIuIEl0IGNl
cnRhaW5seQ0Kc3VycHJpc2VkIG1lLiBJdCBtaWdodCBhbHNvIGJlIHdvcnRoIG5vdGluZyB0aGF0
IHRjcGR1bXAgZG9lcyBub3QNCnRha2UgdGhpcyBsZWFwIG9mIGZhaXRoIGFuZCBzdG9wcyB3aGVu
IGl0IGhpdHMgdGhlIGZpcnN0IDI1My8yNTQuDQoNCj4gV2UnbGwgbm90ZSB0aGlzIGlzc3VlIGlu
IHRoZSBTZWN1cml0eSBDb25zaWRlcmF0aW9ucy4NCg0KT0sgLSB0aGFua3MuDQoNCkZyZWQNCmZy
ZWQubC50ZW1wbGluQGJvZWluZy5jb20NCg0KPiAgICAgQnJpYW4NCg==

From Fred.L.Templin@boeing.com  Fri Oct 11 09:33:40 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7271621E805D for <ipv6@ietfa.amsl.com>; Fri, 11 Oct 2013 09:33:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.423
X-Spam-Level: 
X-Spam-Status: No, score=-6.423 tagged_above=-999 required=5 tests=[AWL=0.176,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iqxfVwqU5DfL for <ipv6@ietfa.amsl.com>; Fri, 11 Oct 2013 09:33:34 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (stl-mbsout-01.boeing.com [130.76.96.169]) by ietfa.amsl.com (Postfix) with ESMTP id A1FF421E809B for <ipv6@ietf.org>; Fri, 11 Oct 2013 09:33:28 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9BGXPfF010895 for <ipv6@ietf.org>; Fri, 11 Oct 2013 11:33:25 -0500
Received: from XCH-PHX-409.sw.nos.boeing.com (xch-phx-409.sw.nos.boeing.com [10.57.37.40]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9BGXOcX010872 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Fri, 11 Oct 2013 11:33:24 -0500
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-PHX-409.sw.nos.boeing.com ([169.254.9.131]) with mapi id 14.03.0158.001; Fri, 11 Oct 2013 09:33:23 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: Adrian Farrel's No Objection on draft-ietf-6man-ext-transmit-04: (with COMMENT)
Thread-Topic: Adrian Farrel's No Objection on draft-ietf-6man-ext-transmit-04: (with COMMENT)
Thread-Index: AQHOxjiFIvFLssN0lkiTRxOL+qsuc5nvpuMQgAAJ0xA=
Date: Fri, 11 Oct 2013 16:33:23 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812C229@XCH-BLV-504.nw.nos.boeing.com>
References: <20131007144327.16131.88173.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1310070914240.13173@shell4.bayarea.net> <52530921.3060202@gmail.com> <Pine.LNX.4.64.1310071315370.13828@shell4.bayarea.net> <52534F31.2020906@gmail.com> <2134F8430051B64F815C691A62D9831811DA86@XCH-BLV-504.nw.nos.boeing.com> <52577B48.8030901@gmail.com> <2134F8430051B64F815C691A62D9831812C178@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831812C178@XCH-BLV-504.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "C. M. Heard" <heard@pobox.com>, "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, "draft-ietf-6man-ext-transmit@tools.ietf.org" <draft-ietf-6man-ext-transmit@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, Adrian Farrel <adrian@olddog.co.uk>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Oct 2013 16:33:40 -0000

Sorry Brian; here is the correct explanation:

> > They must have just made that up; there's no justification for it.
> > It could be an unknown extension header of unknown length, or it
> > could be an unknown payload of unknown length. In real life
> > I'd expect firewalls to default-drop such packets.
>=20
> It could be that Wireshark has some kind of inference engine that
> says: "let's look ahead and see if the next octet looks like another
> NEXTHDR field, and if so keep on plowing through". It certainly
> surprised me. It might also be worth noting that tcpdump does not
> take this leap of faith and stops when it hits the first 253/254.

What is actually happening is that Wireshark assumes that the octet
that follows the NEXTHDR field that encodes 253/254 is a length field
and then seeks ahead by the number of octa-words indicated by the
"length".

In the case of my experimental protocol (SEAL, of course), the octet
that follows the NEXTHDR is *not* a length field, i.e., the same as
for the IPv6 fragment header. It just so happened that the octet
encoded the value 0 making the experimental header look like an
8-octet field. When I change the value to something other than 0,
Wireshark fails.

But, in the final analysis, there is no justification for assuming
that the field that follows the NEXTHDR field is a length field.
It's just that you might get lucky once in a while.

Thanks - Fred
fred.l.templin@boeing.com


From iesg-secretary@ietf.org  Fri Oct 11 09:38:44 2013
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6D0021E8082; Fri, 11 Oct 2013 09:38:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.427
X-Spam-Level: 
X-Spam-Status: No, score=-102.427 tagged_above=-999 required=5 tests=[AWL=0.173, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iejqOQpVmTYB; Fri, 11 Oct 2013 09:38:44 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BAF421F9E5E; Fri, 11 Oct 2013 09:38:32 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: WG Review: IPv6 Maintenance (6man)
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131011163832.4882.45248.idtracker@ietfa.amsl.com>
Date: Fri, 11 Oct 2013 09:38:32 -0700
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Oct 2013 16:38:44 -0000

The IPv6 Maintenance (6man) working group in the Internet Area of the
IETF is undergoing rechartering. The IESG has not made any determination
yet. The following draft charter was submitted, and is provided for
informational purposes only. Please send your comments to the IESG
mailing list (iesg at ietf.org) by 2013-10-21.

IPv6 Maintenance (6man)
------------------------------------------------
Current Status: Active WG

Chairs:
  Robert Hinden <bob.hinden@gmail.com>
  Ole Troan <otroan@employees.org>

Assigned Area Director:
  Brian Haberman <brian@innovationslab.net>

Mailing list
  Address: ipv6@ietf.org
  To Subscribe: https://www.ietf.org/mailman/listinfo/ipv6
  Archive: http://www.ietf.org/mail-archive/web/ipv6

Charter:

The 6man working group is responsible for the maintenance, upkeep, and
advancement of the IPv6 protocol specifications and addressing
architecture. It is not chartered to develop major changes or additions
to the IPv6 specifications. The working group will address protocol
limitations/issues discovered during deployment and operation.  It will
also serve as a venue for discussing the proper location for working on
IPv6-related issues within the IETF.

6man is the design authority for extensions and modifications to the IPv6
protocol. The working group may at its discretion, review any document
extending or modifying the protocol, carried out in another working
group, and may determine that 6man working group consensus is needed
before any of those documents can progress for publication.


Milestones:
  Done     - Submit RH0 Deprecation specification to IESG as a Proposed
Standard
  Done     - Submit PPP Compression Negotiation specification to IESG as
a Proposed Standard
  Done     - Determine way forward for ULA-C specification
  Nov 2013 - Resolve open issues with "U/G" bits in Interface Identifiers
  Mar 2014 - Develop approach for IPv6 Fragmentation
  Mar 2014 - Develop approaches for IPv6 Extension Headers (Hop-by-Hop
and Destination)
  Jul 2014 - Advance IPv6 core specifications to Internet standard



From v6ops@globis.net  Fri Oct 11 09:59:02 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DAB421F9E9F; Fri, 11 Oct 2013 09:59:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l8Pc0PoXEmdv; Fri, 11 Oct 2013 09:59:01 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id C29F811E8143; Fri, 11 Oct 2013 09:58:46 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 73114870085; Fri, 11 Oct 2013 18:58:35 +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 AiIKfe4VVWVu; Fri, 11 Oct 2013 18:58:35 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 3AF11870077; Fri, 11 Oct 2013 18:58:35 +0200 (CEST)
Message-ID: <52582E39.6030109@globis.net>
Date: Fri, 11 Oct 2013 18:58:33 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <2134F8430051B64F815C691A62D9831812C105@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831812C105@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Oct 2013 16:59:02 -0000

> Templin, Fred L <mailto:Fred.L.Templin@boeing.com>
> 11 October 2013 17:33
> Hi Ray,
>
>> -----Original Message-----
>> From: Ray Hunter [mailto:v6ops@globis.net]
>> Sent: Friday, October 11, 2013 12:49 AM
>> To: Templin, Fred L; brian.e.carpenter@gmail.com
>> Cc: ietf@ietf.org; 6man Mailing List
>> Subject: Re: RE: Last Call: <draft-ietf-6man-oversized-header-chain-
>> 08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed
>> Standard
>>
>> Templin, Fred L wrote:
>>> Hi Brian,
>>>
>>> Responding in a slightly re-arranged order:
>>>
>>>> The problem is that you are asserting that middleboxes that a tunnel
>>>> passes through are expected to examine the complete header chain of
>>>> the encapsulated packet even if the encapsulated packet is a
>> fragment.
>>> Yes, but change "are expected to" to "should be able to".
>> I personally don't see this going anywhere.
>>
>> Unless you specifically define what is a "tunnel" and you specifically
>> define a maximum depth of nesting.
>>
>> The term Upper-Layer Protocol (ULP) is also itself a vague term IMHO
>> since the value of the "IPv6 next header" is taken from the same code
>> space as the ULP header values, and there's no specific marker or
>> "header length" field in IPv6 that explicitly marks a point as "This is
>> the end of the IPv6 header chain in all circumstances: stop header
>> parsing here."
>>
>> Ok, there's a bunch of current code-points that are today considered as
>> valid ULP's or next-header values, but that is neither time invariant
>> nor exhaustive, so solving this issue via a registry means there will
>> always be middlebox code in the wild that lags any updates.
>>
>> These middleboxes won't be able to differentiate between an unknown
>> ULP,
>> and an unknown IPv6 next-header. That potentially makes a default pass
>> or drop decision awkward.
>>
>> If it's so important to be able to differentiate between what is an ULP
>> and what is a next header, and we can't reliably do that today, maybe
>> that's a fundamental flaw in IPv6 that should be addressed.
>>
>>
>>>> I think that's an unreasonable expectation. A reasonable expectation
>>>> is that middleboxes should identify the encapsulated packet as
>>>> a payload that they cannot analyse, and let it go (unless they
>>>> have a policy setting to drop tunnelled packets, which is a
>>>> different discussion).
>>> But why? If headers beyond the first IPv6 encapsulation header are
>>> available in the clear, the middlebox should be able to parse them
>>> if it wants to. Wireshark already does exactly that - it keeps on
>>> parsing beyond the first encapsulation header up to and including
>>> the true ULP header. And, if Wireshark can do it, so can any other
>>> middlebox that believes security would be improved by continuing
>>> to parse the entire chain - whether or not there is a standard
>>> saying it must not do so.
>> Because it leaves open the possibility for an attacker to apply the
>> obfuscation we seek to limit.
>>
>>
>>> Parsing the additional headers beyond the first encapsulation header
>>> provides defense-in-depth. Perimeter middleboxes can then weed out
>>> the bad stuff without either allowing the bad stuff to penetrate more
>>> deeply into the organization or dropping good stuff that should be
>>> allowed through.
>> There's also a myriad of tunneling technology out there.
>>
>> Again, what is an ULP? Where do you stop parsing?
>
> The middlebox stops parsing when it decides it has seen enough.

Which AFAIK is undefined in practical terms. Especially in the presence
of jumbo payload extension headers or fragments.

So are you saying the current draft has no value?

>  With
> Wireshark at least, it blasts right through encapsulating IP headers
> and continues up to and including the ultimate TCP/UDP/ICMP etc.
> header inserted by the original host.

I like wireshark.

But how would that parsing model work in a live network without
maintaining state between frames (and leaving your middlebox open to DoS
or other resource depletion abuse)?

IMHO "ultimate TCP/UDP/ICMP etc." is not defined. The IETF does not
define standard protocol stacks as a totality. HTTP over TCP over IPv6
over L2TP over GRE over PPTP VPN over IPv6 over IPv6 is not illegal. So
this would seem to require far tighter specs on packet formats than the
IETF would ever publish (and rightly so).



>  The goal is to give the
> middlebox enough information so that it can parse as deeply into
> the headers as it wants to.

If that is the goal then we probably need to deprecate IPv6
fragmentation as well as a whole bunch of tunnel / encryption protocols
IMHO, and specify that the entire packet has to fit in a single frame.
Which I feel is unrealistic.
>> Is GRE a tunnel or an ULP? (GRE can run over almost anything)
>> Is SSH an ULP or a tunnel? (port tunneling)
>> Is Teredo a tunnel or is it an ULP (UDP) or both?
>> GRE/ LT2P over HTTP anyone?
>>
>> The notion of "perimeter" is moveable in the presence of such tunnels.
>
> We will want for middleboxes at outer perimeters to be able to parse
> as many headers as they want to before releasing the packet to
> middleboxes at inner perimenters. Otherwise, bad stuff can get past
> the outermost perimeters and waste bandwidth and/or cause havoc
> within the protected zone. 

Right. But if your firewall (which now has to maintain state, or which
is forced to parse right to the end of a packet) itself becomes the
bottleneck and the DoS target, what have you gained?

>> Presumably there comes a point where the tunnel is terminated and the
>> transported packet is de-encapsulated, and that IMHO forms another
>> perimeter where you'd anyway have to apply further security checks.
>
> Nested tunnels give you perimeters within perimeters, yes. But, we
> will want the outer perimeters to be able to parse as deeply as
> they want to before passing on to an inner perimeter.

I think my customers will have to start thinking in terms of an onion
skin model, rather than a single outer perimeter and a single "trusted"
zone.
Maintaining state, or full-packet-depth parsing, at the point where the
enterprise hits the Internet is probably not going to fly.
>
>> I think the draft does what it can in a pragmatic manner, but might
>> benefit from some acknowledgement that this security approach of
>> applying parsing at a single perimeter can never ever catch all
>> variants
>> of transporting FOO over BAR.
>>
>> IMHO It's only at the moment of de-encapsulation that the full
>> semantics
>> of the payload are revealed in these modern times of "everything
>> transported over HTTP".
>>
>>
>>
>>
>>>> Since the problem recurses as we tunnel tunnels, I don't see how any
>>>> finite limit can solve the problem. 1280 itself is a pragmatic
>> choice
>>>> of "a bit shorter than 1500".
>> Agreed.
>
> I guess I will have to repeat myself from what I said several
> months ago. The 1280 came from a desire to have multiple nested
> tunnels without requiring the tunnels to fragment since the
> underlying links presumably all configure a 1500 MTU. But, what
> would that look like in real life?
>
> - The first tunnel would have to configure a 1280 MTU so that its
>   encapsulated packets emerged as 1320
> - the second tunnel would have to configure a 1320 MTU so that its
>   encapsulated  packets emerged as 1360
> - the third tunnel would have to configure a 1360 MTU so that its
>   encapsulated packets emerged as 1400
> - etc.
>
> But, in real life, it is not possible to assume that we can lay
> hands on all tunnel endpoints so as to carefully set MTUs that
> satisfy the nesting level - and, when multiple administrative
> domains are involved, it can't be done at all.
>
> Please go back in the archives to where I posted the derivation
> of the 1280 minMTU (circa 1997):
>
> http://www.ietf.org/mail-archive/web/ipv6/current/msg18462.html
>
> My conclusion is that the 1280/1500 was well intentioned, but
> unfortunately not very well thought out.
>
> Thanks - Fred
> fred.l.templin@boeing.com

It doesn't matter what number you pick, and 1280 is probably as good as
it gets. The point from Brian (if I understood it correctly) was that
any fixed number can never be sufficient, as there's no dedicated
portion of the IPv6 MTU specifically assigned to tunneling, and no
defined max tunnel nesting depth.
>>> The 1280 is assuming that all links in the path have a 1500 MTU and
>>> so RFC2460 allowed (1500 - 1280) = 220 bytes for additional IPv6
>>> headers added by nested tunnels without incurring fragmentation.
>>> I am asserting instead that we have to allow for paths that include
>>> links with a 1280 MTU and so tunnels will have to fragment over
>>> such paths.
>>>
>>> That means that the first fragmenting tunnel would have room for
>>> 1240 in the first fragment, the second fragmenting tunnel would
>>> have room for 1200 in the first fragment, etc. That is why I would
>>> prefer that hosts limit the size of their header chains to 1024; so
>>> that nested tunnels that fragment will still be highly likely to
>>> have the entire header chain in the first fragment.
>>>
>>>> I understood that to be the basis on which the WG reached consensus.
>>> Maybe the WG didn't understand that such a consensus would make
>>> tunnels less reliable and less secure.
>>>
>>> Thanks - Fred
>>> fred.l.templin@boeing.com
>>>
>>>>     Brian
>> --
>> Regards,
>> RayH
>
> ------------------------------------------------------------------------


-- 
Regards,
RayH


From fgont@si6networks.com  Fri Oct 11 10:04:24 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A76B421E80E2; Fri, 11 Oct 2013 10:04:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CcVze5dbSgqo; Fri, 11 Oct 2013 10:04:24 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 0183821E80F1; Fri, 11 Oct 2013 10:04:23 -0700 (PDT)
Received: from 17-153-16-190.fibertel.com.ar ([190.16.153.17] helo=[192.168.1.193]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1VUg8O-0002s1-G2; Fri, 11 Oct 2013 19:04:17 +0200
Message-ID: <52582F8B.8040306@si6networks.com>
Date: Fri, 11 Oct 2013 14:04:11 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>,  Ray Hunter <v6ops@globis.net>, "brian.e.carpenter@gmail.com" <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com>	<2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com>	<2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com>	<9300F272-E282-41C3-9DA8-59134B975FC7@employees.org>	<9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com>	<2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com>	<D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org>	<2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com>	<E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org>	<2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com>	<5255D6EE.4050300@gmail.com>	<2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Oct 2013 17:04:24 -0000

On 10/11/2013 12:36 PM, Templin, Fred L wrote:
>> FWIW, my idea of the I-D is that it says "look, if you don't put all
>> this info into the first fragment, it's extremely likely that your
>> packets will be dropped". That doesn't mean that a middle-box may want
>> to look further. But looking further might imply
>> reassemble-inspect-and-refragment... or even reassemble the TCP stream
>> (e.g. think about a SSL/TCP-based VPN...)
> 
> We definitely don't want that. That is why we would prefer for
> the entire header chain (starting from the outermost IP header
> up to and including the headers inserted by the original host)
> to fit within the first fragment even if there are multiple
> encapsulations on the path.

The problem is that if you have multiple encapsulations, you can always
hit the MTU limit and fail to comply with this requirement.

That's why this I-D says what it says.

P.S.: Reegarding enforcing a limit on the length of the header chain, I
must say I symphatize with that (for instance, check the last individual
version of this I-D, and you'll find exactly that). But the wg didn't
want that in -- and I did raise the issue a few times. So what we have
is what the 6man wg had consensus on.

Thanks!

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





From Fred.L.Templin@boeing.com  Fri Oct 11 10:35:55 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B93821E80ED; Fri, 11 Oct 2013 10:35:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.437
X-Spam-Level: 
X-Spam-Status: No, score=-6.437 tagged_above=-999 required=5 tests=[AWL=0.162,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R7zckJrfdfcg; Fri, 11 Oct 2013 10:35:49 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) by ietfa.amsl.com (Postfix) with ESMTP id CC82221E8090; Fri, 11 Oct 2013 10:35:49 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9BHZmfE005894; Fri, 11 Oct 2013 10:35:49 -0700
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9BHZkm7005378 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 11 Oct 2013 10:35:48 -0700
Received: from XCH-BLV-308.nw.nos.boeing.com (130.247.25.220) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Fri, 11 Oct 2013 10:35:47 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-BLV-308.nw.nos.boeing.com ([169.254.8.40]) with mapi id 14.03.0158.001; Fri, 11 Oct 2013 10:35:46 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ray Hunter <v6ops@globis.net>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOxqMeebc9KTehbEGO6mhunuAlj5nvvDEg
Date: Fri, 11 Oct 2013 17:35:46 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812C36A@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <2134F8430051B64F815C691A62D9831812C105@XCH-BLV-504.nw.nos.boeing.com> <52582E39.6030109@globis.net>
In-Reply-To: <52582E39.6030109@globis.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Oct 2013 17:35:55 -0000

Hi Ray,

> -----Original Message-----
> From: Ray Hunter [mailto:v6ops@globis.net]
> Sent: Friday, October 11, 2013 9:59 AM
> To: Templin, Fred L
> Cc: brian.e.carpenter@gmail.com; ietf@ietf.org; 6man Mailing List
> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> > Templin, Fred L <mailto:Fred.L.Templin@boeing.com>
> > 11 October 2013 17:33
> > Hi Ray,
> >
> >> -----Original Message-----
> >> From: Ray Hunter [mailto:v6ops@globis.net]
> >> Sent: Friday, October 11, 2013 12:49 AM
> >> To: Templin, Fred L; brian.e.carpenter@gmail.com
> >> Cc: ietf@ietf.org; 6man Mailing List
> >> Subject: Re: RE: Last Call: <draft-ietf-6man-oversized-header-chain-
> >> 08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed
> >> Standard
> >>
> >> Templin, Fred L wrote:
> >>> Hi Brian,
> >>>
> >>> Responding in a slightly re-arranged order:
> >>>
> >>>> The problem is that you are asserting that middleboxes that a
> tunnel
> >>>> passes through are expected to examine the complete header chain
> of
> >>>> the encapsulated packet even if the encapsulated packet is a
> >> fragment.
> >>> Yes, but change "are expected to" to "should be able to".
> >> I personally don't see this going anywhere.
> >>
> >> Unless you specifically define what is a "tunnel" and you
> specifically
> >> define a maximum depth of nesting.
> >>
> >> The term Upper-Layer Protocol (ULP) is also itself a vague term IMHO
> >> since the value of the "IPv6 next header" is taken from the same
> code
> >> space as the ULP header values, and there's no specific marker or
> >> "header length" field in IPv6 that explicitly marks a point as "This
> is
> >> the end of the IPv6 header chain in all circumstances: stop header
> >> parsing here."
> >>
> >> Ok, there's a bunch of current code-points that are today considered
> as
> >> valid ULP's or next-header values, but that is neither time
> invariant
> >> nor exhaustive, so solving this issue via a registry means there
> will
> >> always be middlebox code in the wild that lags any updates.
> >>
> >> These middleboxes won't be able to differentiate between an unknown
> >> ULP,
> >> and an unknown IPv6 next-header. That potentially makes a default
> pass
> >> or drop decision awkward.
> >>
> >> If it's so important to be able to differentiate between what is an
> ULP
> >> and what is a next header, and we can't reliably do that today,
> maybe
> >> that's a fundamental flaw in IPv6 that should be addressed.
> >>
> >>
> >>>> I think that's an unreasonable expectation. A reasonable
> expectation
> >>>> is that middleboxes should identify the encapsulated packet as
> >>>> a payload that they cannot analyse, and let it go (unless they
> >>>> have a policy setting to drop tunnelled packets, which is a
> >>>> different discussion).
> >>> But why? If headers beyond the first IPv6 encapsulation header are
> >>> available in the clear, the middlebox should be able to parse them
> >>> if it wants to. Wireshark already does exactly that - it keeps on
> >>> parsing beyond the first encapsulation header up to and including
> >>> the true ULP header. And, if Wireshark can do it, so can any other
> >>> middlebox that believes security would be improved by continuing
> >>> to parse the entire chain - whether or not there is a standard
> >>> saying it must not do so.
> >> Because it leaves open the possibility for an attacker to apply the
> >> obfuscation we seek to limit.
> >>
> >>
> >>> Parsing the additional headers beyond the first encapsulation
> header
> >>> provides defense-in-depth. Perimeter middleboxes can then weed out
> >>> the bad stuff without either allowing the bad stuff to penetrate
> more
> >>> deeply into the organization or dropping good stuff that should be
> >>> allowed through.
> >> There's also a myriad of tunneling technology out there.
> >>
> >> Again, what is an ULP? Where do you stop parsing?
> >
> > The middlebox stops parsing when it decides it has seen enough.
>=20
> Which AFAIK is undefined in practical terms. Especially in the presence
> of jumbo payload extension headers or fragments.

Middleboxes should be able to parse as far as they want to
without hitting a hard stop as is the case if the header
chain extends into multiple packets.

> So are you saying the current draft has no value?

I am saying that it is unfriendly to tunnels that fragment, and a
simple fix is for the host to limit its header chain length to
1024 bytes.

> >  With
> > Wireshark at least, it blasts right through encapsulating IP headers
> > and continues up to and including the ultimate TCP/UDP/ICMP etc.
> > header inserted by the original host.
>=20
> I like wireshark.
>=20
> But how would that parsing model work in a live network without
> maintaining state between frames (and leaving your middlebox open to
> DoS
> or other resource depletion abuse)?

I don't understand the "maintaining state between frames". I am
talking about examining individual header chains within a single
packet independently of any other packets.

We may not yet know how smart middleboxes may become in this
regards. But, they will certainly never become smart enough if
they don't have the entire header chain in the first fragment.=20

> IMHO "ultimate TCP/UDP/ICMP etc." is not defined. The IETF does not
> define standard protocol stacks as a totality. HTTP over TCP over IPv6
> over L2TP over GRE over PPTP VPN over IPv6 over IPv6 is not illegal. So
> this would seem to require far tighter specs on packet formats than the
> IETF would ever publish (and rightly so).

Not at all. This is about allowing middleboxes to parse through all
of the headers included by the host and any tunnel endpoints that
may have interposed themselves between the host and the middlebox.
How the middlebox parses is its own business.
=20
> >  The goal is to give the
> > middlebox enough information so that it can parse as deeply into
> > the headers as it wants to.
>=20
> If that is the goal then we probably need to deprecate IPv6
> fragmentation as well as a whole bunch of tunnel / encryption protocols
> IMHO, and specify that the entire packet has to fit in a single frame.
> Which I feel is unrealistic.

Not at all. The proposal is to ask the host to limit its header
chain to 1024 bytes to allow for up to 256 bytes of encapsulation
headers before the header chain would be susceptible to
fragmentation.

> >> Is GRE a tunnel or an ULP? (GRE can run over almost anything)
> >> Is SSH an ULP or a tunnel? (port tunneling)
> >> Is Teredo a tunnel or is it an ULP (UDP) or both?
> >> GRE/ LT2P over HTTP anyone?
> >>
> >> The notion of "perimeter" is moveable in the presence of such
> tunnels.
> >
> > We will want for middleboxes at outer perimeters to be able to parse
> > as many headers as they want to before releasing the packet to
> > middleboxes at inner perimenters. Otherwise, bad stuff can get past
> > the outermost perimeters and waste bandwidth and/or cause havoc
> > within the protected zone.
>=20
> Right. But if your firewall (which now has to maintain state, or which
> is forced to parse right to the end of a packet) itself becomes the
> bottleneck and the DoS target, what have you gained?

No inter-packet state - I never said or implied that. And, no one
is *forcing* the middlebox to do anything. This is about *allowing*
the middlebox to do whatever it wants.
=20
> >> Presumably there comes a point where the tunnel is terminated and
> the
> >> transported packet is de-encapsulated, and that IMHO forms another
> >> perimeter where you'd anyway have to apply further security checks.
> >
> > Nested tunnels give you perimeters within perimeters, yes. But, we
> > will want the outer perimeters to be able to parse as deeply as
> > they want to before passing on to an inner perimeter.
>=20
> I think my customers will have to start thinking in terms of an onion
> skin model, rather than a single outer perimeter and a single "trusted"
> zone.
> Maintaining state, or full-packet-depth parsing, at the point where the
> enterprise hits the Internet is probably not going to fly.

Onion skin, yes, with each layer of the onion doing what it can
to enhance security. That is what I mean by defense in depth.

> >> I think the draft does what it can in a pragmatic manner, but might
> >> benefit from some acknowledgement that this security approach of
> >> applying parsing at a single perimeter can never ever catch all
> >> variants
> >> of transporting FOO over BAR.
> >>
> >> IMHO It's only at the moment of de-encapsulation that the full
> >> semantics
> >> of the payload are revealed in these modern times of "everything
> >> transported over HTTP".
> >>
> >>
> >>
> >>
> >>>> Since the problem recurses as we tunnel tunnels, I don't see how
> any
> >>>> finite limit can solve the problem. 1280 itself is a pragmatic
> >> choice
> >>>> of "a bit shorter than 1500".
> >> Agreed.
> >
> > I guess I will have to repeat myself from what I said several
> > months ago. The 1280 came from a desire to have multiple nested
> > tunnels without requiring the tunnels to fragment since the
> > underlying links presumably all configure a 1500 MTU. But, what
> > would that look like in real life?
> >
> > - The first tunnel would have to configure a 1280 MTU so that its
> >   encapsulated packets emerged as 1320
> > - the second tunnel would have to configure a 1320 MTU so that its
> >   encapsulated  packets emerged as 1360
> > - the third tunnel would have to configure a 1360 MTU so that its
> >   encapsulated packets emerged as 1400
> > - etc.
> >
> > But, in real life, it is not possible to assume that we can lay
> > hands on all tunnel endpoints so as to carefully set MTUs that
> > satisfy the nesting level - and, when multiple administrative
> > domains are involved, it can't be done at all.
> >
> > Please go back in the archives to where I posted the derivation
> > of the 1280 minMTU (circa 1997):
> >
> > http://www.ietf.org/mail-archive/web/ipv6/current/msg18462.html
> >
> > My conclusion is that the 1280/1500 was well intentioned, but
> > unfortunately not very well thought out.
> >
> > Thanks - Fred
> > fred.l.templin@boeing.com
>=20
> It doesn't matter what number you pick, and 1280 is probably as good as
> it gets. The point from Brian (if I understood it correctly) was that
> any fixed number can never be sufficient, as there's no dedicated
> portion of the IPv6 MTU specifically assigned to tunneling, and no
> defined max tunnel nesting depth.

A fixed number does not limit the number of tunnel nestings, but
it does limit how many nestings can be applied before the header
chain might wrap into a second fragment. But, how many nestings
do you want? If you want up to 6 or so, then the 1024 gives adequate
space. If you want something like 10 or more, then the extension
header chain could theoretically wrap into second fragments.

Remember that the 1280/1500 was to "allow extra room" for tunnels
to add encapsulation headers without causing fragmentation. That
goal also had a fixed upper bound of 220 bytes of room so the
number of nested tunnels was limited by that action as well
(even assuming you could get the tunnel endpoints to cooperate
and make efficient use of the 220). For better or worse, 1280
gave us a fixed number that we will be stuck with forever.

Thanks - Fred
fred.l.templin@boeing.com

> >>> The 1280 is assuming that all links in the path have a 1500 MTU and
> >>> so RFC2460 allowed (1500 - 1280) =3D 220 bytes for additional IPv6
> >>> headers added by nested tunnels without incurring fragmentation.
> >>> I am asserting instead that we have to allow for paths that include
> >>> links with a 1280 MTU and so tunnels will have to fragment over
> >>> such paths.
> >>>
> >>> That means that the first fragmenting tunnel would have room for
> >>> 1240 in the first fragment, the second fragmenting tunnel would
> >>> have room for 1200 in the first fragment, etc. That is why I would
> >>> prefer that hosts limit the size of their header chains to 1024; so
> >>> that nested tunnels that fragment will still be highly likely to
> >>> have the entire header chain in the first fragment.
> >>>
> >>>> I understood that to be the basis on which the WG reached
> consensus.
> >>> Maybe the WG didn't understand that such a consensus would make
> >>> tunnels less reliable and less secure.
> >>>
> >>> Thanks - Fred
> >>> fred.l.templin@boeing.com
> >>>
> >>>>     Brian
> >> --
> >> Regards,
> >> RayH
> >
> > ---------------------------------------------------------------------
> ---
>=20
>=20
> --
> Regards,
> RayH


From Fred.L.Templin@boeing.com  Fri Oct 11 10:51:41 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D232E21E81A5; Fri, 11 Oct 2013 10:51:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.448
X-Spam-Level: 
X-Spam-Status: No, score=-6.448 tagged_above=-999 required=5 tests=[AWL=0.151,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oQUH2E8MAcPX; Fri, 11 Oct 2013 10:51:33 -0700 (PDT)
Received: from blv-mbsout-01.boeing.com (blv-mbsout-01.boeing.com [130.76.32.231]) by ietfa.amsl.com (Postfix) with ESMTP id 6C89E21E81E9; Fri, 11 Oct 2013 10:51:21 -0700 (PDT)
Received: from blv-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9BHpIJO020921; Fri, 11 Oct 2013 10:51:19 -0700
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9BHpHxC020869 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 11 Oct 2013 10:51:18 -0700
Received: from XCH-BLV-306.nw.nos.boeing.com (130.247.25.218) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Fri, 11 Oct 2013 10:51:13 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-BLV-306.nw.nos.boeing.com ([169.254.6.22]) with mapi id 14.03.0158.001; Fri, 11 Oct 2013 10:51:12 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Fernando Gont <fgont@si6networks.com>, Ray Hunter <v6ops@globis.net>, "brian.e.carpenter@gmail.com" <brian.e.carpenter@gmail.com>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOxqPnebc9KTehbEGO6mhunuAlj5nvxCJQ
Date: Fri, 11 Oct 2013 17:51:12 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812C3B9@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com>
In-Reply-To: <52582F8B.8040306@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Oct 2013 17:51:41 -0000

Hi Fernando,

> -----Original Message-----
> From: Fernando Gont [mailto:fgont@si6networks.com]
> Sent: Friday, October 11, 2013 10:04 AM
> To: Templin, Fred L; Ray Hunter; brian.e.carpenter@gmail.com
> Cc: 6man Mailing List; ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> On 10/11/2013 12:36 PM, Templin, Fred L wrote:
> >> FWIW, my idea of the I-D is that it says "look, if you don't put all
> >> this info into the first fragment, it's extremely likely that your
> >> packets will be dropped". That doesn't mean that a middle-box may
> want
> >> to look further. But looking further might imply
> >> reassemble-inspect-and-refragment... or even reassemble the TCP
> stream
> >> (e.g. think about a SSL/TCP-based VPN...)
> >
> > We definitely don't want that. That is why we would prefer for
> > the entire header chain (starting from the outermost IP header
> > up to and including the headers inserted by the original host)
> > to fit within the first fragment even if there are multiple
> > encapsulations on the path.
>=20
> The problem is that if you have multiple encapsulations, you can always
> hit the MTU limit and fail to comply with this requirement.

Yes you can, which is what I just said to Ray. But, I am not talking
about a *requirement* - I am talking about a best practice that works
in most cases.

The question is how many layers of encapsulation do you need? Let's
say you want 5 layers of encapsulation. That would still allow enough
room for all of the hosts headers to fit in the first fragment if the
host limits its header chain to 1024 bytes. But, now let's say that
you want 10 layers of encapsulation. That means that the first 5
middleboxes that examine the outermost encapsulations will not be
able to see the entire header chain, but the last 5 middleboxes that
examine the innermost encapsulations will. So, there is a limit to
the levels of defense-in-depth. But, that limit is greater than 1.

Remember also that the 1280/1500 also assumed that there would be
"just a few" layers of nested encapsulations. What I am suggesting
allows for endless recursion but limited (and reasonable) defense
in depth.=20
=20
> That's why this I-D says what it says.

I'm not sure this discussion was taken into account, and what the
draft says now is not friendly to tunnels.

> P.S.: Reegarding enforcing a limit on the length of the header chain, I
> must say I symphatize with that (for instance, check the last
> individual
> version of this I-D, and you'll find exactly that). But the wg didn't
> want that in -- and I did raise the issue a few times. So what we have
> is what the 6man wg had consensus on.

It is not too late to get this right, and to give reasonable
treatment to tunnels that the current draft does not give.

Thanks - Fred
fred.l.templin@boeing.com

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


From brian.e.carpenter@gmail.com  Fri Oct 11 12:49:43 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05EC111E8155; Fri, 11 Oct 2013 12:49:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.564
X-Spam-Level: 
X-Spam-Status: No, score=-102.564 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AMhE8My0nHFQ; Fri, 11 Oct 2013 12:49:42 -0700 (PDT)
Received: from mail-pd0-x22f.google.com (mail-pd0-x22f.google.com [IPv6:2607:f8b0:400e:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 3235511E8185; Fri, 11 Oct 2013 12:49:37 -0700 (PDT)
Received: by mail-pd0-f175.google.com with SMTP id q10so4729449pdj.34 for <multiple recipients>; Fri, 11 Oct 2013 12:49:36 -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=URymMGHE3n5kLFeBo5RXtIiIee/MtyM5fngcgsTMzuA=; b=TiTXVs2R7CoCdbwFih5Qo7VGp1cEqf763ZmcrBY4zC9+ssX2ZM6mi4mjEHcfiu470r o+PpN/8S3xjV2DPkgJjlOd8mcAsKkRbq2/qblgGvrgS1Ej+QtKhjl4e3ZoLbq3qfaVXG +8NZSLujS5lMr7A4b9WdwInoezdvS4vsNl3DfSZU9R3CljDd5hJHWzKjZ8AGmYDs1kSc 5hifaLRI2wg95nKC/r3vPp2fimFMMwIfxePLaMP4b4UeUfA5NX6TTmRARezqbCNKoajd +6LDMERx9WOOHycQvds8w0jtrgl7zcjbXeKE8Bu4iOOUZ1CQzgyvjv++y4ueJIN+qIP9 ANkQ==
X-Received: by 10.66.216.129 with SMTP id oq1mr23875322pac.75.1381520976796; Fri, 11 Oct 2013 12:49:36 -0700 (PDT)
Received: from [192.168.178.20] (164.195.69.111.dynamic.snap.net.nz. [111.69.195.164]) by mx.google.com with ESMTPSA id va8sm61654062pbc.16.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 11 Oct 2013 12:49:35 -0700 (PDT)
Message-ID: <52585658.50205@gmail.com>
Date: Sat, 12 Oct 2013 08:49:44 +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: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com>	<2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com>	<2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com>	<9300F272-E282-41C3-9DA8-59134B975FC7@employees.org>	<9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com>	<2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com>	<D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org>	<2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com>	<E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org>	<2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com>	<5255D6EE.4050300@gmail.com>	<2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com>
In-Reply-To: <52582F8B.8040306@si6networks.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Ray Hunter <v6ops@globis.net>, 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Oct 2013 19:49:43 -0000

On 12/10/2013 06:04, Fernando Gont wrote:
...
> P.S.: Reegarding enforcing a limit on the length of the header chain, I
> must say I symphatize with that (for instance, check the last individual
> version of this I-D, and you'll find exactly that). But the wg didn't
> want that in -- and I did raise the issue a few times. So what we have
> is what the 6man wg had consensus on.

I agree that this was the WG consensus after considerable discussion,
which included Fred, so I'm not sure why we're discussing it again
during IETF LC.

   Brian

From Fred.L.Templin@boeing.com  Fri Oct 11 12:57:39 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 664B421E808E; Fri, 11 Oct 2013 12:57:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.458
X-Spam-Level: 
X-Spam-Status: No, score=-6.458 tagged_above=-999 required=5 tests=[AWL=0.141,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NzpIQM1PU3SN; Fri, 11 Oct 2013 12:57:26 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (stl-mbsout-01.boeing.com [130.76.96.169]) by ietfa.amsl.com (Postfix) with ESMTP id A43FB11E818F; Fri, 11 Oct 2013 12:56:55 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9BJupbI025335; Fri, 11 Oct 2013 14:56:52 -0500
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9BJuOel024378 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 11 Oct 2013 14:56:51 -0500
Received: from XCH-BLV-202.nw.nos.boeing.com (10.57.37.69) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Fri, 11 Oct 2013 12:56:46 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-BLV-202.nw.nos.boeing.com ([169.254.2.10]) with mapi id 14.03.0158.001; Fri, 11 Oct 2013 12:56:45 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Fernando Gont <fgont@si6networks.com>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOxrsIebc9KTehbEGO6mhunuAlj5nv6Nlw
Date: Fri, 11 Oct 2013 19:56:44 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com>
In-Reply-To: <52585658.50205@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: Ray Hunter <v6ops@globis.net>, 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Oct 2013 19:57:40 -0000

SGkgQnJpYW4sDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogQnJpYW4g
RSBDYXJwZW50ZXIgW21haWx0bzpicmlhbi5lLmNhcnBlbnRlckBnbWFpbC5jb21dDQo+IFNlbnQ6
IEZyaWRheSwgT2N0b2JlciAxMSwgMjAxMyAxMjo1MCBQTQ0KPiBUbzogRmVybmFuZG8gR29udA0K
PiBDYzogVGVtcGxpbiwgRnJlZCBMOyBSYXkgSHVudGVyOyA2bWFuIE1haWxpbmcgTGlzdDsgaWV0
ZkBpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTogTGFzdCBDYWxsOiA8ZHJhZnQtaWV0Zi02bWFuLW92
ZXJzaXplZC1oZWFkZXItY2hhaW4tMDgudHh0Pg0KPiAoSW1wbGljYXRpb25zIG9mIE92ZXJzaXpl
ZCBJUHY2IEhlYWRlciBDaGFpbnMpIHRvIFByb3Bvc2VkIFN0YW5kYXJkDQo+IA0KPiBPbiAxMi8x
MC8yMDEzIDA2OjA0LCBGZXJuYW5kbyBHb250IHdyb3RlOg0KPiAuLi4NCj4gPiBQLlMuOiBSZWVn
YXJkaW5nIGVuZm9yY2luZyBhIGxpbWl0IG9uIHRoZSBsZW5ndGggb2YgdGhlIGhlYWRlciBjaGFp
biwNCj4gSQ0KPiA+IG11c3Qgc2F5IEkgc3ltcGhhdGl6ZSB3aXRoIHRoYXQgKGZvciBpbnN0YW5j
ZSwgY2hlY2sgdGhlIGxhc3QNCj4gaW5kaXZpZHVhbA0KPiA+IHZlcnNpb24gb2YgdGhpcyBJLUQs
IGFuZCB5b3UnbGwgZmluZCBleGFjdGx5IHRoYXQpLiBCdXQgdGhlIHdnIGRpZG4ndA0KPiA+IHdh
bnQgdGhhdCBpbiAtLSBhbmQgSSBkaWQgcmFpc2UgdGhlIGlzc3VlIGEgZmV3IHRpbWVzLiBTbyB3
aGF0IHdlDQo+IGhhdmUNCj4gPiBpcyB3aGF0IHRoZSA2bWFuIHdnIGhhZCBjb25zZW5zdXMgb24u
DQo+IA0KPiBJIGFncmVlIHRoYXQgdGhpcyB3YXMgdGhlIFdHIGNvbnNlbnN1cyBhZnRlciBjb25z
aWRlcmFibGUgZGlzY3Vzc2lvbiwNCj4gd2hpY2ggaW5jbHVkZWQgRnJlZCwgc28gSSdtIG5vdCBz
dXJlIHdoeSB3ZSdyZSBkaXNjdXNzaW5nIGl0IGFnYWluDQo+IGR1cmluZyBJRVRGIExDLg0KDQpU
ZWNobmljYWwgbWF0dGVycyBzaG91bGQgYmUgZGlzY3Vzc2VkIGFzIHRoZXkgY29tZSB0byBsaWdo
dDsgbm90DQpkaXNtaXNzZWQgYmVjYXVzZSBvZiBzb21lIHJlYWwgb3IgcGVyY2VpdmVkIGRlYWRs
aW5lLiBUaGF0IHdhcyB3aGF0DQpnb3QgdXMgdGhlIDEyODAgTVRVIGluIHRoZSBmaXJzdCBwbGFj
ZS4gUXVvdGluZyBmcm9tIFN0ZXZlIERlZXJpbmc6DQoNCiAgIiBXZSB3b3VsZCBsaWtlIHRvIGdl
dCB0aGlzIGlzc3VlIHNldHRsZWQgYXMNCiAgICBzb29uIGFzIHBvc3NpYmxlLCBzaW5jZSB0aGlz
IGlzIHRoZSBvbmx5IHRoaW5nIGhvbGRpbmcgdXAgdGhlIHB1YmxpY2F0aW9uDQogICAgb2YgdGhl
IHVwZGF0ZWQgUHJvcG9zZWQgU3RhbmRhcmQgSVB2NiBzcGVjICh0aGUgdmVyc2lvbiB3ZSBleHBl
Y3QgdG8gYWR2YW5jZQ0KICAgIHRvIERyYWZ0IFN0YW5kYXJkKSwgc28gbGV0J3Mgc2VlIGlmIHdl
IGNhbiBjb21lIHRvIGEgZGVjaXNpb24gYmVmb3JlIHRoZSBJRA0KICAgIGRlYWRsaW5lIGF0IHRo
ZSBlbmQgb2YgbmV4dCB3ZWVrIChob3BpbmcgdGhlcmUgaXNuJ3QgYW55IGNvbmZsaWN0IGJldHdl
ZW4NCiAgICAidGhvdWdodGZ1bCBhbmFseXNpcyIgYW5kICJsZXQncyBkZWNpZGUgcXVpY2tseSIg
Oi0pLiINCg0KU28sIGl0IHdhc24ndCBuZWNlc3NhcmlseSB0aGUgY2FzZSB0aGF0IDEyODAgd2Fz
IGEgcHJvZHVjdCBvZiAidGhvdWdodGZ1bA0KYW5hbHlzaXMiIHNvIG11Y2ggYXMgdGhlIGZhY3Qg
dGhhdCAqKnRoZXkgd2VyZSBydXNoaW5nIHRvIGdldCBhIHNwZWMgb3V0DQp0aGUgZG9vcioqLiBT
byBub3csIDE2IHllYXJzIGxhdGVyLCB3ZSBnZXQgdG8gcHV0IGl0IGJhY2sgb24gdGhlIDZtYW4N
CmNoYXJ0ZXIgbWlsZXN0b25lIGxpc3QuDQoNCg0KVGhhbmtzIC0gRnJlZA0KZnJlZC5sLnRlbXBs
aW5AYm9laW5nLmNvbQ0K

From brian.e.carpenter@gmail.com  Fri Oct 11 15:41:53 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B2AB21E80DE; Fri, 11 Oct 2013 15:41:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.565
X-Spam-Level: 
X-Spam-Status: No, score=-102.565 tagged_above=-999 required=5 tests=[AWL=0.034, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WgfES4c1ZEFN; Fri, 11 Oct 2013 15:41:52 -0700 (PDT)
Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 81AFD21E8095; Fri, 11 Oct 2013 15:41:52 -0700 (PDT)
Received: by mail-pa0-f45.google.com with SMTP id rd3so5025884pab.18 for <multiple recipients>; Fri, 11 Oct 2013 15:41: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=UYox1/C8ABBzIqlCaq2B0Syu+Li2UoNBsausiO4TVH0=; b=Yhbb2mbo7fofWghGuRYiNdx8vtmkO204sR06PXVAkI6iThmdTBjTYpaWOaGNHVS+UH PXjqZBcKRuWeR53PWFlRrnTm/aUVmLi4MdIspGSV2OULmlwPFM1NrKH1y/f7ZuLAqWSr O250rWx5Mxztc5z4BzJ0grGN97FuqrFA9MAdJKkehtRCCgkn5YY7Zx8+shL2s1LQYfxM bqq1/REyejyHV8M4cxP1YPoc66RGCJGbTZP+oES98w60f6KYoYkLTO8ROHGZluV5lCCL fZSw6baCpnYRkdusjqBAXJDV777mFawAGxe4b1ahl6vDcG0Wpoh8xUgxPwTo4nh7gOQI 0Scg==
X-Received: by 10.68.203.195 with SMTP id ks3mr22261289pbc.83.1381531312164; Fri, 11 Oct 2013 15:41:52 -0700 (PDT)
Received: from [192.168.178.20] (164.195.69.111.dynamic.snap.net.nz. [111.69.195.164]) by mx.google.com with ESMTPSA id xn12sm72900503pac.12.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 11 Oct 2013 15:41:51 -0700 (PDT)
Message-ID: <52587EB8.4020506@gmail.com>
Date: Sat, 12 Oct 2013 11:42:00 +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: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com>	<2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com>	<9300F272-E282-41C3-9DA8-59134B975FC7@employees.org>	<9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com>	<2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com>	<D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org>	<2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com>	<E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org>	<2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com>	<5255D6EE.4050300@gmail.com>	<2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Fernando Gont <fgont@si6networks.com>, 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Oct 2013 22:41:53 -0000

Fred,

On 12/10/2013 08:56, Templin, Fred L wrote:
> Hi Brian,
> 
>> -----Original Message-----
>> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
>> Sent: Friday, October 11, 2013 12:50 PM
>> To: Fernando Gont
>> Cc: Templin, Fred L; Ray Hunter; 6man Mailing List; ietf@ietf.org
>> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
>> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>>
>> On 12/10/2013 06:04, Fernando Gont wrote:
>> ...
>>> P.S.: Reegarding enforcing a limit on the length of the header chain,
>> I
>>> must say I symphatize with that (for instance, check the last
>> individual
>>> version of this I-D, and you'll find exactly that). But the wg didn't
>>> want that in -- and I did raise the issue a few times. So what we
>> have
>>> is what the 6man wg had consensus on.
>> I agree that this was the WG consensus after considerable discussion,
>> which included Fred, so I'm not sure why we're discussing it again
>> during IETF LC.
> 
> Technical matters should be discussed as they come to light; not
> dismissed because of some real or perceived deadline. That was what
> got us the 1280 MTU in the first place. Quoting from Steve Deering:
> 
>   " We would like to get this issue settled as
>     soon as possible, since this is the only thing holding up the publication
>     of the updated Proposed Standard IPv6 spec (the version we expect to advance
>     to Draft Standard), so let's see if we can come to a decision before the ID
>     deadline at the end of next week (hoping there isn't any conflict between
>     "thoughtful analysis" and "let's decide quickly" :-)."
> 
> So, it wasn't necessarily the case that 1280 was a product of "thoughtful
> analysis" so much as the fact that **they were rushing to get a spec out
> the door**. So now, 16 years later, we get to put it back on the 6man
> charter milestone list.

We could have that discussion in 6man, sure, but I don't believe that it's
relevant to the question of whether draft-ietf-6man-oversized-header-chain
is ready. This draft mitigates a known problem in terms of the current
IPv6 standards.

    Brian

From rbonica@juniper.net  Sat Oct 12 19:07:12 2013
Return-Path: <rbonica@juniper.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B39011E8106; Sat, 12 Oct 2013 19:07:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.699
X-Spam-Level: 
X-Spam-Status: No, score=-104.699 tagged_above=-999 required=5 tests=[AWL=1.900, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s6TIpIacj1jr; Sat, 12 Oct 2013 19:06:53 -0700 (PDT)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe005.messaging.microsoft.com [207.46.163.28]) by ietfa.amsl.com (Postfix) with ESMTP id 1981E11E80FE; Sat, 12 Oct 2013 19:06:52 -0700 (PDT)
Received: from mail220-co9-R.bigfish.com (10.236.132.242) by CO9EHSOBE009.bigfish.com (10.236.130.72) with Microsoft SMTP Server id 14.1.225.22; Sun, 13 Oct 2013 02:06:52 +0000
Received: from mail220-co9 (localhost [127.0.0.1])	by mail220-co9-R.bigfish.com (Postfix) with ESMTP id E54D62600B5; Sun, 13 Oct 2013 02:06:51 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT002.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: 1
X-BigFish: VPS1(zz1432Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzzz2fh2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1fe8h1ff5h9a9j1155h)
Received-SPF: pass (mail220-co9: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rbonica@juniper.net; helo=BL2PRD0510HT002.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(189002)(199002)(51704005)(69226001)(80022001)(66066001)(65816001)(63696002)(56816003)(77096001)(46102001)(74706001)(33646001)(74876001)(83072001)(51856001)(76482001)(53806001)(56776001)(54316002)(81816001)(54356001)(74366001)(4396001)(47446002)(74502001)(74662001)(59766001)(79102001)(77982001)(81686001)(81542001)(47976001)(50986001)(49866001)(85306002)(47736001)(31966008)(81342001)(80976001)(74316001)(76786001)(76796001)(83322001)(76576001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:CO1PR05MB441; H:CO1PR05MB442.namprd05.prod.outlook.com; CLIP:66.129.232.2; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Received: from mail220-co9 (localhost.localdomain [127.0.0.1]) by mail220-co9 (MessageSwitch) id 1381630010253315_13970; Sun, 13 Oct 2013 02:06:50 +0000 (UTC)
Received: from CO9EHSMHS014.bigfish.com (unknown [10.236.132.234])	by mail220-co9.bigfish.com (Postfix) with ESMTP id 2E90980040; Sun, 13 Oct 2013 02:06:50 +0000 (UTC)
Received: from BL2PRD0510HT002.namprd05.prod.outlook.com (157.56.240.101) by CO9EHSMHS014.bigfish.com (10.236.130.24) with Microsoft SMTP Server (TLS) id 14.16.227.3; Sun, 13 Oct 2013 02:06:49 +0000
Received: from CO1PR05MB441.namprd05.prod.outlook.com (10.141.73.147) by BL2PRD0510HT002.namprd05.prod.outlook.com (10.255.100.37) with Microsoft SMTP Server (TLS) id 14.16.371.2; Sun, 13 Oct 2013 02:06:48 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB441.namprd05.prod.outlook.com (10.141.73.147) with Microsoft SMTP Server (TLS) id 15.0.785.10; Sun, 13 Oct 2013 02:06:45 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.14]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.50]) with mapi id 15.00.0785.001; Sun, 13 Oct 2013 02:06:45 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Templin, Fred L" <Fred.L.Templin@boeing.com>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOxlz+2A8NgSbtr0yOE+fNSkVMX5nvonIAgAAYo4CAAC5BAIAAAfUAgAAuLACAAcruIA==
Date: Sun, 13 Oct 2013 02:06:44 +0000
Message-ID: <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com>
In-Reply-To: <52587EB8.4020506@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
x-forefront-prvs: 0998671D02
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: Fernando Gont <fgont@si6networks.com>, 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 13 Oct 2013 02:07:12 -0000

+1

Is there a way to decouple this discussion from draft-ietf-6man-oversized-h=
eader-chain? I would be glad to discuss it in the context of a separate dra=
ft.

                                                             Ron


> >
> > So, it wasn't necessarily the case that 1280 was a product of
> > "thoughtful analysis" so much as the fact that **they were rushing to
> > get a spec out the door**. So now, 16 years later, we get to put it
> > back on the 6man charter milestone list.
>=20
> We could have that discussion in 6man, sure, but I don't believe that
> it's relevant to the question of whether draft-ietf-6man-oversized-
> header-chain
> is ready. This draft mitigates a known problem in terms of the current
> IPv6 standards.
>=20



From arturo.servin@gmail.com  Sun Oct 13 06:35:26 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A77721F9DCA for <ipv6@ietfa.amsl.com>; Sun, 13 Oct 2013 06:35:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oAMFmPZlOubp for <ipv6@ietfa.amsl.com>; Sun, 13 Oct 2013 06:35:25 -0700 (PDT)
Received: from mail-yh0-x22f.google.com (mail-yh0-x22f.google.com [IPv6:2607:f8b0:4002:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 6632121F81FF for <ipv6@ietf.org>; Sun, 13 Oct 2013 06:35:20 -0700 (PDT)
Received: by mail-yh0-f47.google.com with SMTP id t59so1243027yho.20 for <ipv6@ietf.org>; Sun, 13 Oct 2013 06:35:17 -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=XFrZyVMvQRWagiXmn91TPuysBiEqpjNtoQ3XIQo8QzE=; b=nELCBjBfm6IJ5qJ71VHVS/YhF8brEdMpkCL2QPoP/VwaG/Vambt/6I7hG2rgSZ8946 Z80EuKif5qesIn3vOgeFFnDDLzE0lp8kMHs3oiKrnengoBVXcng3KZicl8aW3Tso0m5a TOMsui4cHF39kB6x52lDkeSoZ6mggtA9zceQOoqzUFOLSAcB7CxPbq1y4wGs+Z0u6IXq 9NX8MPeUOSFjKkCbwY0fK0TXMK++8PWq4LjBlmlrAqQzcXxk+5WflAqbvpL+dYYJ3BVT VA8uBdreo2yYajlA78WvQ2GVbS0czVaobtpRZv/nJo8yKB2bSg2LzUReWQZgn+HnmtjQ ZvEQ==
X-Received: by 10.236.122.239 with SMTP id t75mr616291yhh.57.1381671317321; Sun, 13 Oct 2013 06:35:17 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([2800:af:ba31:734:bc80:fb37:23ae:9619]) by mx.google.com with ESMTPSA id e39sm94944385yhq.15.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 13 Oct 2013 06:35:15 -0700 (PDT)
Message-ID: <525AA191.6070408@gmail.com>
Date: Sun, 13 Oct 2013 11:35:13 -0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: 6man WG <ipv6@ietf.org>
Subject: Re: WG Review: IPv6 Maintenance (6man)
References: <20131011163832.4882.45248.idtracker@ietfa.amsl.com>
In-Reply-To: <20131011163832.4882.45248.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 13 Oct 2013 13:35:27 -0000

	Would you expand a bit on this?

	 Jul 2014 - Advance IPv6 core specifications to Internet standard

	And after the discussions in Berlin about fragmentation, the dates of
the milestones look a bit ambitious to me.

Regards,
as

On 10/11/13 2:38 PM, The IESG wrote:
> The IPv6 Maintenance (6man) working group in the Internet Area of the
> IETF is undergoing rechartering. The IESG has not made any determination
> yet. The following draft charter was submitted, and is provided for
> informational purposes only. Please send your comments to the IESG
> mailing list (iesg at ietf.org) by 2013-10-21.
> 
> IPv6 Maintenance (6man)
> ------------------------------------------------
> Current Status: Active WG
> 
> Chairs:
>   Robert Hinden <bob.hinden@gmail.com>
>   Ole Troan <otroan@employees.org>
> 
> Assigned Area Director:
>   Brian Haberman <brian@innovationslab.net>
> 
> Mailing list
>   Address: ipv6@ietf.org
>   To Subscribe: https://www.ietf.org/mailman/listinfo/ipv6
>   Archive: http://www.ietf.org/mail-archive/web/ipv6
> 
> Charter:
> 
> The 6man working group is responsible for the maintenance, upkeep, and
> advancement of the IPv6 protocol specifications and addressing
> architecture. It is not chartered to develop major changes or additions
> to the IPv6 specifications. The working group will address protocol
> limitations/issues discovered during deployment and operation.  It will
> also serve as a venue for discussing the proper location for working on
> IPv6-related issues within the IETF.
> 
> 6man is the design authority for extensions and modifications to the IPv6
> protocol. The working group may at its discretion, review any document
> extending or modifying the protocol, carried out in another working
> group, and may determine that 6man working group consensus is needed
> before any of those documents can progress for publication.
> 
> 
> Milestones:
>   Done     - Submit RH0 Deprecation specification to IESG as a Proposed
> Standard
>   Done     - Submit PPP Compression Negotiation specification to IESG as
> a Proposed Standard
>   Done     - Determine way forward for ULA-C specification
>   Nov 2013 - Resolve open issues with "U/G" bits in Interface Identifiers
>   Mar 2014 - Develop approach for IPv6 Fragmentation
>   Mar 2014 - Develop approaches for IPv6 Extension Headers (Hop-by-Hop
> and Destination)
>   Jul 2014 - Advance IPv6 core specifications to Internet standard
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 

From Fred.L.Templin@boeing.com  Mon Oct 14 10:38:13 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 555BD21E8197; Mon, 14 Oct 2013 10:38:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.467
X-Spam-Level: 
X-Spam-Status: No, score=-6.467 tagged_above=-999 required=5 tests=[AWL=0.132,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dm1SBu8l9hs5; Mon, 14 Oct 2013 10:38:06 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) by ietfa.amsl.com (Postfix) with ESMTP id 6B5D821E8192; Mon, 14 Oct 2013 10:38:05 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9EHc4qV000711; Mon, 14 Oct 2013 12:38:04 -0500
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9EHbx4e000617 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 14 Oct 2013 12:38:03 -0500
Received: from XCH-BLV-302.nw.nos.boeing.com (130.247.25.214) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Mon, 14 Oct 2013 10:38:02 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-BLV-302.nw.nos.boeing.com ([169.254.2.227]) with mapi id 14.03.0158.001; Mon, 14 Oct 2013 10:38:01 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOxtMYebc9KTehbEGO6mhunuAlj5n0eZ8A
Date: Mon, 14 Oct 2013 17:38:00 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812D718@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com>
In-Reply-To: <52587EB8.4020506@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: Fernando Gont <fgont@si6networks.com>, 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 14 Oct 2013 17:38:13 -0000

SGkgQnJpYW4sDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogQnJpYW4g
RSBDYXJwZW50ZXIgW21haWx0bzpicmlhbi5lLmNhcnBlbnRlckBnbWFpbC5jb21dDQo+IFNlbnQ6
IEZyaWRheSwgT2N0b2JlciAxMSwgMjAxMyAzOjQyIFBNDQo+IFRvOiBUZW1wbGluLCBGcmVkIEwN
Cj4gQ2M6IEZlcm5hbmRvIEdvbnQ7IFJheSBIdW50ZXI7IDZtYW4gTWFpbGluZyBMaXN0OyBpZXRm
QGlldGYub3JnDQo+IFN1YmplY3Q6IFJlOiBMYXN0IENhbGw6IDxkcmFmdC1pZXRmLTZtYW4tb3Zl
cnNpemVkLWhlYWRlci1jaGFpbi0wOC50eHQ+DQo+IChJbXBsaWNhdGlvbnMgb2YgT3ZlcnNpemVk
IElQdjYgSGVhZGVyIENoYWlucykgdG8gUHJvcG9zZWQgU3RhbmRhcmQNCj4gDQo+IEZyZWQsDQo+
IA0KPiBPbiAxMi8xMC8yMDEzIDA4OjU2LCBUZW1wbGluLCBGcmVkIEwgd3JvdGU6DQo+ID4gSGkg
QnJpYW4sDQo+ID4NCj4gPj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gPj4gRnJvbTog
QnJpYW4gRSBDYXJwZW50ZXIgW21haWx0bzpicmlhbi5lLmNhcnBlbnRlckBnbWFpbC5jb21dDQo+
ID4+IFNlbnQ6IEZyaWRheSwgT2N0b2JlciAxMSwgMjAxMyAxMjo1MCBQTQ0KPiA+PiBUbzogRmVy
bmFuZG8gR29udA0KPiA+PiBDYzogVGVtcGxpbiwgRnJlZCBMOyBSYXkgSHVudGVyOyA2bWFuIE1h
aWxpbmcgTGlzdDsgaWV0ZkBpZXRmLm9yZw0KPiA+PiBTdWJqZWN0OiBSZTogTGFzdCBDYWxsOiA8
ZHJhZnQtaWV0Zi02bWFuLW92ZXJzaXplZC1oZWFkZXItY2hhaW4tDQo+IDA4LnR4dD4NCj4gPj4g
KEltcGxpY2F0aW9ucyBvZiBPdmVyc2l6ZWQgSVB2NiBIZWFkZXIgQ2hhaW5zKSB0byBQcm9wb3Nl
ZCBTdGFuZGFyZA0KPiA+Pg0KPiA+PiBPbiAxMi8xMC8yMDEzIDA2OjA0LCBGZXJuYW5kbyBHb250
IHdyb3RlOg0KPiA+PiAuLi4NCj4gPj4+IFAuUy46IFJlZWdhcmRpbmcgZW5mb3JjaW5nIGEgbGlt
aXQgb24gdGhlIGxlbmd0aCBvZiB0aGUgaGVhZGVyDQo+IGNoYWluLA0KPiA+PiBJDQo+ID4+PiBt
dXN0IHNheSBJIHN5bXBoYXRpemUgd2l0aCB0aGF0IChmb3IgaW5zdGFuY2UsIGNoZWNrIHRoZSBs
YXN0DQo+ID4+IGluZGl2aWR1YWwNCj4gPj4+IHZlcnNpb24gb2YgdGhpcyBJLUQsIGFuZCB5b3Un
bGwgZmluZCBleGFjdGx5IHRoYXQpLiBCdXQgdGhlIHdnDQo+IGRpZG4ndA0KPiA+Pj4gd2FudCB0
aGF0IGluIC0tIGFuZCBJIGRpZCByYWlzZSB0aGUgaXNzdWUgYSBmZXcgdGltZXMuIFNvIHdoYXQg
d2UNCj4gPj4gaGF2ZQ0KPiA+Pj4gaXMgd2hhdCB0aGUgNm1hbiB3ZyBoYWQgY29uc2Vuc3VzIG9u
Lg0KPiA+PiBJIGFncmVlIHRoYXQgdGhpcyB3YXMgdGhlIFdHIGNvbnNlbnN1cyBhZnRlciBjb25z
aWRlcmFibGUNCj4gZGlzY3Vzc2lvbiwNCj4gPj4gd2hpY2ggaW5jbHVkZWQgRnJlZCwgc28gSSdt
IG5vdCBzdXJlIHdoeSB3ZSdyZSBkaXNjdXNzaW5nIGl0IGFnYWluDQo+ID4+IGR1cmluZyBJRVRG
IExDLg0KPiA+DQo+ID4gVGVjaG5pY2FsIG1hdHRlcnMgc2hvdWxkIGJlIGRpc2N1c3NlZCBhcyB0
aGV5IGNvbWUgdG8gbGlnaHQ7IG5vdA0KPiA+IGRpc21pc3NlZCBiZWNhdXNlIG9mIHNvbWUgcmVh
bCBvciBwZXJjZWl2ZWQgZGVhZGxpbmUuIFRoYXQgd2FzIHdoYXQNCj4gPiBnb3QgdXMgdGhlIDEy
ODAgTVRVIGluIHRoZSBmaXJzdCBwbGFjZS4gUXVvdGluZyBmcm9tIFN0ZXZlIERlZXJpbmc6DQo+
ID4NCj4gPiAgICIgV2Ugd291bGQgbGlrZSB0byBnZXQgdGhpcyBpc3N1ZSBzZXR0bGVkIGFzDQo+
ID4gICAgIHNvb24gYXMgcG9zc2libGUsIHNpbmNlIHRoaXMgaXMgdGhlIG9ubHkgdGhpbmcgaG9s
ZGluZyB1cCB0aGUNCj4gcHVibGljYXRpb24NCj4gPiAgICAgb2YgdGhlIHVwZGF0ZWQgUHJvcG9z
ZWQgU3RhbmRhcmQgSVB2NiBzcGVjICh0aGUgdmVyc2lvbiB3ZSBleHBlY3QNCj4gdG8gYWR2YW5j
ZQ0KPiA+ICAgICB0byBEcmFmdCBTdGFuZGFyZCksIHNvIGxldCdzIHNlZSBpZiB3ZSBjYW4gY29t
ZSB0byBhIGRlY2lzaW9uDQo+IGJlZm9yZSB0aGUgSUQNCj4gPiAgICAgZGVhZGxpbmUgYXQgdGhl
IGVuZCBvZiBuZXh0IHdlZWsgKGhvcGluZyB0aGVyZSBpc24ndCBhbnkgY29uZmxpY3QNCj4gYmV0
d2Vlbg0KPiA+ICAgICAidGhvdWdodGZ1bCBhbmFseXNpcyIgYW5kICJsZXQncyBkZWNpZGUgcXVp
Y2tseSIgOi0pLiINCj4gPg0KPiA+IFNvLCBpdCB3YXNuJ3QgbmVjZXNzYXJpbHkgdGhlIGNhc2Ug
dGhhdCAxMjgwIHdhcyBhIHByb2R1Y3Qgb2YNCj4gInRob3VnaHRmdWwNCj4gPiBhbmFseXNpcyIg
c28gbXVjaCBhcyB0aGUgZmFjdCB0aGF0ICoqdGhleSB3ZXJlIHJ1c2hpbmcgdG8gZ2V0IGEgc3Bl
Yw0KPiBvdXQNCj4gPiB0aGUgZG9vcioqLiBTbyBub3csIDE2IHllYXJzIGxhdGVyLCB3ZSBnZXQg
dG8gcHV0IGl0IGJhY2sgb24gdGhlIDZtYW4NCj4gPiBjaGFydGVyIG1pbGVzdG9uZSBsaXN0Lg0K
PiANCj4gV2UgY291bGQgaGF2ZSB0aGF0IGRpc2N1c3Npb24gaW4gNm1hbiwgc3VyZSwgYnV0IEkg
ZG9uJ3QgYmVsaWV2ZSB0aGF0DQo+IGl0J3MNCj4gcmVsZXZhbnQgdG8gdGhlIHF1ZXN0aW9uIG9m
IHdoZXRoZXIgZHJhZnQtaWV0Zi02bWFuLW92ZXJzaXplZC1oZWFkZXItDQo+IGNoYWluDQo+IGlz
IHJlYWR5Lg0KDQpJZiBpdCBtZXNzZXMgdXAgdHVubmVscywgdGhlbiBpdCdzIG5vdCByZWFkeS4N
Cg0KPiBUaGlzIGRyYWZ0IG1pdGlnYXRlcyBhIGtub3duIHByb2JsZW0gaW4gdGVybXMgb2YgdGhl
IGN1cnJlbnQNCj4gSVB2NiBzdGFuZGFyZHMuDQoNCklmIHRoYXQgcHJvYmxlbSBpcyBhbHNvIG1p
dGlnYXRlZCBieSBhIG1lYXN1cmUgdGhhdCBkb2VzIG5vdCBtZXNzDQp1cCB0dW5uZWxzLCB0aGVu
IHdvdWxkbid0IHRoYXQgYmUgd29ydGggY29uc2lkZXJpbmcgYmVmb3JlDQpmaW5hbGl6aW5nIHRo
aXMgcHVibGljYXRpb24uDQoNClRoYW5rcyAtIEZyZWQNCmZyZWQubC50ZW1wbGluQGJvZWluZy5j
b20NCg0KPiAgICAgQnJpYW4NCg==

From Fred.L.Templin@boeing.com  Mon Oct 14 10:39:49 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A27C221F923D; Mon, 14 Oct 2013 10:39:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.475
X-Spam-Level: 
X-Spam-Status: No, score=-6.475 tagged_above=-999 required=5 tests=[AWL=0.124,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mgXh+3ftqz6l; Mon, 14 Oct 2013 10:39:41 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) by ietfa.amsl.com (Postfix) with ESMTP id C9BF321F8EC3; Mon, 14 Oct 2013 10:39:32 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9EHdV5H003302; Mon, 14 Oct 2013 12:39:32 -0500
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9EHdSoO003242 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 14 Oct 2013 12:39:31 -0500
Received: from XCH-EXCO-103.nw.nos.boeing.com (130.247.25.37) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Mon, 14 Oct 2013 10:39:30 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-EXCO-103.nw.nos.boeing.com ([fe80::7434:66d:a0ba:2234%15]) with mapi id 14.03.0158.001; Mon, 14 Oct 2013 10:39:29 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ronald Bonica <rbonica@juniper.net>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOx7jqJAvRrWBwLEyOc1cqWuOOX5n0dmTg
Date: Mon, 14 Oct 2013 17:39:29 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com>
In-Reply-To: <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: Fernando Gont <fgont@si6networks.com>, 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 14 Oct 2013 17:39:49 -0000

Hi Ron,

> -----Original Message-----
> From: Ronald Bonica [mailto:rbonica@juniper.net]
> Sent: Saturday, October 12, 2013 7:07 PM
> To: Brian E Carpenter; Templin, Fred L
> Cc: Fernando Gont; 6man Mailing List; ietf@ietf.org; Ray Hunter
> Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> +1
>=20
> Is there a way to decouple this discussion from draft-ietf-6man-
> oversized-header-chain? I would be glad to discuss it in the context of
> a separate draft.

I don't know if there is a way to decouple it. I believe I have shown
a way to not mess up tunnels while at the same time not messing up your
draft. That should be a win-win. In what way would imposing a 1K limit
on the IPv6 header chain not satisfy the general case?

Thanks - Fred
fred.l.templin@boeing.com
=20
>                                                              Ron
>=20
>=20
> > >
> > > So, it wasn't necessarily the case that 1280 was a product of
> > > "thoughtful analysis" so much as the fact that **they were rushing
> to
> > > get a spec out the door**. So now, 16 years later, we get to put it
> > > back on the 6man charter milestone list.
> >
> > We could have that discussion in 6man, sure, but I don't believe that
> > it's relevant to the question of whether draft-ietf-6man-oversized-
> > header-chain
> > is ready. This draft mitigates a known problem in terms of the
> current
> > IPv6 standards.
> >
>=20


From brian.e.carpenter@gmail.com  Mon Oct 14 12:34:25 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7200211E8185; Mon, 14 Oct 2013 12:34:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.57
X-Spam-Level: 
X-Spam-Status: No, score=-102.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d3PsYrB5lfAc; Mon, 14 Oct 2013 12:34:25 -0700 (PDT)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 09C5011E816D; Mon, 14 Oct 2013 12:34:24 -0700 (PDT)
Received: by mail-pa0-f53.google.com with SMTP id kq14so7895355pab.40 for <multiple recipients>; Mon, 14 Oct 2013 12:34: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=8ZoHiqL+wyDVPOVKRnhhHFDz8PWbpaFU2tS5d3owDxs=; b=j5ckgXsE/OtiFuyKNhIOCZtKFmbyk/Ylw/3wfsu614o1wgqGkcPvzge2cEKgy9wJHr yLU/dk4jJkKP1mP8EQKJwNo/CS4sorhQDQfZBesQQrZmRjkvILB+gKojHg874pkM/95+ HFM8IqZSMIY7c/1F77aSgyrrLDzSlx1zMQ3NrLZHANhqYBfcDauTnYMUq0X2IIY5CEUB iTUw31EA0d+LTiwqzq2bbSu7C4srmeqxXppyEQmRZLL+ig+SfxHZIJ1fIlE/5mm/UHjP YNA9+W1MB/Pmp7XXWz+F+hwOnIFl8SnbO++wRzoE9mgiDH8/rBftSoTQAnmMNY3v8aJp SN9w==
X-Received: by 10.68.134.133 with SMTP id pk5mr37696138pbb.89.1381779264762; Mon, 14 Oct 2013 12:34:24 -0700 (PDT)
Received: from [192.168.178.20] (19.202.69.111.dynamic.snap.net.nz. [111.69.202.19]) by mx.google.com with ESMTPSA id a6sm33043717pbr.17.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 14 Oct 2013 12:34:23 -0700 (PDT)
Message-ID: <525C473D.4080403@gmail.com>
Date: Tue, 15 Oct 2013 08:34:21 +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: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com>	<9300F272-E282-41C3-9DA8-59134B975FC7@employees.org>	<9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com>	<2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com>	<D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org>	<2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com>	<E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org>	<2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com>	<5255D6EE.4050300@gmail.com>	<2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <2134F8430051B64F815C691A62D9831812D718@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831812D718@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Fernando Gont <fgont@si6networks.com>, 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 14 Oct 2013 19:34:25 -0000

Fred,

On 15/10/2013 06:38, Templin, Fred L wrote:
...
>> We could have that discussion in 6man, sure, but I don't believe that
>> it's
>> relevant to the question of whether draft-ietf-6man-oversized-header-
>> chain
>> is ready.
> 
> If it messes up tunnels, then it's not ready.

That doesn't follow. See below.

>> This draft mitigates a known problem in terms of the current
>> IPv6 standards.
> 
> If that problem is also mitigated by a measure that does not mess
> up tunnels, then wouldn't that be worth considering before
> finalizing this publication.

The draft mitigates a known problem with communication paths that
do not include nested tunnels requiring nested fragmentation,
where the nested tunnel has to deal with an MTU <1280 *and* where
the nested tunnel goes through a firewall that wants to analyse
the complete header chain of the innermost packet.

No, I don't think it's worth considering that case before specifying
this mitigation.

     Brian

From Fred.L.Templin@boeing.com  Mon Oct 14 12:55:44 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B80311E81A3; Mon, 14 Oct 2013 12:55:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.482
X-Spam-Level: 
X-Spam-Status: No, score=-6.482 tagged_above=-999 required=5 tests=[AWL=0.117,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RJrnivfBp7yA; Mon, 14 Oct 2013 12:55:26 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) by ietfa.amsl.com (Postfix) with ESMTP id 179E611E816D; Mon, 14 Oct 2013 12:55:10 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9EJt5Eb001824; Mon, 14 Oct 2013 14:55:05 -0500
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9EJt4eX001804 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 14 Oct 2013 14:55:05 -0500
Received: from XCH-BLV-207.nw.nos.boeing.com (10.57.37.63) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Mon, 14 Oct 2013 12:55:04 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-BLV-207.nw.nos.boeing.com ([10.57.37.63]) with mapi id 14.03.0158.001; Mon, 14 Oct 2013 12:55:03 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOyRRhebc9KTehbEGO6mhunuAlj5n0mDGA
Date: Mon, 14 Oct 2013 19:55:02 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812D8F7@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <2134F8430051B64F815C691A62D9831812D718@XCH-BLV-504.nw.nos.boeing.com> <525C473D.4080403@gmail.com>
In-Reply-To: <525C473D.4080403@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: Fernando Gont <fgont@si6networks.com>, 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 14 Oct 2013 19:55:44 -0000

SGkgQnJpYW4sDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogQnJpYW4g
RSBDYXJwZW50ZXIgW21haWx0bzpicmlhbi5lLmNhcnBlbnRlckBnbWFpbC5jb21dDQo+IFNlbnQ6
IE1vbmRheSwgT2N0b2JlciAxNCwgMjAxMyAxMjozNCBQTQ0KPiBUbzogVGVtcGxpbiwgRnJlZCBM
DQo+IENjOiBGZXJuYW5kbyBHb250OyBSYXkgSHVudGVyOyA2bWFuIE1haWxpbmcgTGlzdDsgaWV0
ZkBpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTogTGFzdCBDYWxsOiA8ZHJhZnQtaWV0Zi02bWFuLW92
ZXJzaXplZC1oZWFkZXItY2hhaW4tMDgudHh0Pg0KPiAoSW1wbGljYXRpb25zIG9mIE92ZXJzaXpl
ZCBJUHY2IEhlYWRlciBDaGFpbnMpIHRvIFByb3Bvc2VkIFN0YW5kYXJkDQo+IA0KPiBGcmVkLA0K
PiANCj4gT24gMTUvMTAvMjAxMyAwNjozOCwgVGVtcGxpbiwgRnJlZCBMIHdyb3RlOg0KPiAuLi4N
Cj4gPj4gV2UgY291bGQgaGF2ZSB0aGF0IGRpc2N1c3Npb24gaW4gNm1hbiwgc3VyZSwgYnV0IEkg
ZG9uJ3QgYmVsaWV2ZQ0KPiB0aGF0DQo+ID4+IGl0J3MNCj4gPj4gcmVsZXZhbnQgdG8gdGhlIHF1
ZXN0aW9uIG9mIHdoZXRoZXIgZHJhZnQtaWV0Zi02bWFuLW92ZXJzaXplZC0NCj4gaGVhZGVyLQ0K
PiA+PiBjaGFpbg0KPiA+PiBpcyByZWFkeS4NCj4gPg0KPiA+IElmIGl0IG1lc3NlcyB1cCB0dW5u
ZWxzLCB0aGVuIGl0J3Mgbm90IHJlYWR5Lg0KPiANCj4gVGhhdCBkb2Vzbid0IGZvbGxvdy4gU2Vl
IGJlbG93Lg0KPiANCj4gPj4gVGhpcyBkcmFmdCBtaXRpZ2F0ZXMgYSBrbm93biBwcm9ibGVtIGlu
IHRlcm1zIG9mIHRoZSBjdXJyZW50DQo+ID4+IElQdjYgc3RhbmRhcmRzLg0KPiA+DQo+ID4gSWYg
dGhhdCBwcm9ibGVtIGlzIGFsc28gbWl0aWdhdGVkIGJ5IGEgbWVhc3VyZSB0aGF0IGRvZXMgbm90
IG1lc3MNCj4gPiB1cCB0dW5uZWxzLCB0aGVuIHdvdWxkbid0IHRoYXQgYmUgd29ydGggY29uc2lk
ZXJpbmcgYmVmb3JlDQo+ID4gZmluYWxpemluZyB0aGlzIHB1YmxpY2F0aW9uLg0KPiANCj4gVGhl
IGRyYWZ0IG1pdGlnYXRlcyBhIGtub3duIHByb2JsZW0gd2l0aCBjb21tdW5pY2F0aW9uIHBhdGhz
IHRoYXQNCj4gZG8gbm90IGluY2x1ZGUgbmVzdGVkIHR1bm5lbHMgcmVxdWlyaW5nIG5lc3RlZCBm
cmFnbWVudGF0aW9uLA0KPiB3aGVyZSB0aGUgbmVzdGVkIHR1bm5lbCBoYXMgdG8gZGVhbCB3aXRo
IGFuIE1UVSA8MTI4MCAqYW5kKiB3aGVyZQ0KPiB0aGUgbmVzdGVkIHR1bm5lbCBnb2VzIHRocm91
Z2ggYSBmaXJld2FsbCB0aGF0IHdhbnRzIHRvIGFuYWx5c2UNCj4gdGhlIGNvbXBsZXRlIGhlYWRl
ciBjaGFpbiBvZiB0aGUgaW5uZXJtb3N0IHBhY2tldC4NCg0KQnV0IHR1bm5lbHMgLSBhbmQgdHVu
bmVscyB3aXRoaW4gdHVubmVscyAtIG5lZWQgdG8gYmUgY29uc2lkZXJlZA0KYXMgcGFydCBvZiB0
aGUgYXJjaGl0ZWN0dXJlLiBJIGhhdmUgdmlzaWJpbGl0eSBpbnRvIHRoZSBuZXR3b3JrDQpvcGVy
YXRpb25zIG9mIGEgbWFqb3IgbXVsdGktbmF0aW9uYWwgY29ycG9yYXRpb24sIGFuZCBJIGNhbiB0
ZWxsDQp5b3UgdGhhdCBJIHNlZSB0dW5uZWxzIHdpdGhpbiB0dW5uZWxzIGluIG9wZXJhdGlvbmFs
IHByYWN0aWNlIHRvZGF5Lg0KSSBhbHNvIGhhdmUgdmlzaWJpbGl0eSBpbnRvIGNpdmlsIGF2aWF0
aW9uIGFuZCBEb0QgbmV0d29ya3MsIGFuZA0KSSBzZWUgYW4gZW1lcmdpbmcgdHJlbmQgZm9yIG1v
YmlsZSBuZXR3b3Jrcy4gQ29uc2lkZXIgYSBtb2JpbGUNCm5ldHdvcmsgQiB0aGF0IGNvbWVzIG9u
dG8gYSBsaW5rIG9mZmVyZWQgYnkgbW9iaWxlIG5ldHdvcmsgQS4NClRoZW4sIG1vYmlsZSBuZXR3
b3JrIEMgY29tZXMgb250byBhIGxpbmsgb2ZmZXJlZCBieSBCLiBUaGVuLCBldGMuDQpUaGVuLCB0
aGUgbmV4dCB0aGluZyB5b3Uga25vdywgaXQncyB0dXJ0bGVzIGFsbCB0aGUgd2F5IGRvd24uDQoN
CkZyYWdtZW50YXRpb24gaXMgdGhlIHRvb2wgdGhhdCBlbmFibGVzIGVuZGxlc3MgcmVjdXJzaW9u
LiBPciwgYXQNCmxlYXN0LCByZWN1cnNpb24gdXAgdG8gc29tZSBkZWZpbmVkIGxpbWl0LiBBdCBs
ZWFzdCBmb3IgdGhlIGZpcnN0DQpzZXZlcmFsIGxldmVscyBvZiByZWN1cnNpb24sIG1pZGRsZWJv
eGVzIHNob3VsZCBiZSBhYmxlIHRvIHNlZSBhbGwNCmhvc3QtaW5zZXJ0ZWQgaGVhZGVycyB3aXRo
aW4gdGhlIGZpcnN0IGZyYWdtZW50Lg0KDQpUaGFua3MgLSBGcmVkDQpmcmVkLmwudGVtcGxpbkBi
b2VpbmcuY29tDQoNCg0KPiBObywgSSBkb24ndCB0aGluayBpdCdzIHdvcnRoIGNvbnNpZGVyaW5n
IHRoYXQgY2FzZSBiZWZvcmUgc3BlY2lmeWluZw0KPiB0aGlzIG1pdGlnYXRpb24uDQo+IA0KPiAg
ICAgIEJyaWFuDQo=

From v6ops@globis.net  Mon Oct 14 14:06:48 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 547A621F9B21; Mon, 14 Oct 2013 14:06:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wuW21UDweU3Z; Mon, 14 Oct 2013 14:06:47 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id CA4E821E80F8; Mon, 14 Oct 2013 14:06:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 5F79C870098; Mon, 14 Oct 2013 23:06:40 +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 icorFUAm68iL; Mon, 14 Oct 2013 23:06:40 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 2513B87008A; Mon, 14 Oct 2013 23:06:40 +0200 (CEST)
Message-ID: <525C5CDE.3000604@globis.net>
Date: Mon, 14 Oct 2013 23:06:38 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>, 6man Mailing List <ipv6@ietf.org>, Fernando Gont <fgont@si6networks.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 14 Oct 2013 21:06:48 -0000

> Templin, Fred L <mailto:Fred.L.Templin@boeing.com>
> 14 October 2013 19:39
> Hi Ron,
>
>> -----Original Message-----
>> From: Ronald Bonica [mailto:rbonica@juniper.net]
>> Sent: Saturday, October 12, 2013 7:07 PM
>> To: Brian E Carpenter; Templin, Fred L
>> Cc: Fernando Gont; 6man Mailing List; ietf@ietf.org; Ray Hunter
>> Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
>> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>>
>> +1
>>
>> Is there a way to decouple this discussion from draft-ietf-6man-
>> oversized-header-chain? I would be glad to discuss it in the context of
>> a separate draft.
>
> I don't know if there is a way to decouple it. I believe I have shown
> a way to not mess up tunnels while at the same time not messing up your
> draft. That should be a win-win. In what way would imposing a 1K limit
> on the IPv6 header chain not satisfy the general case?
>
> Thanks - Fred
> fred.l.templin@boeing.com

This draft may not go as far as you'd like (e.g. specifying a hard limit
on header length as some proportion of MTU), and I'm also aware of the
issue of MTU fragmentation and nested tunnels, but I'm still not clear
on how this draft specifically "messes up tunnels."

Can you explain what specific text in the current draft you consider
harmful?

And why that couldn't be dealt with in a later draft (that imposes
additional limits on header chains in specific scenarios)?

Thanks.


>  
>>                                                              Ron
>>
>>
>>>> So, it wasn't necessarily the case that 1280 was a product of
>>>> "thoughtful analysis" so much as the fact that **they were rushing
>> to
>>>> get a spec out the door**. So now, 16 years later, we get to put it
>>>> back on the 6man charter milestone list.
>>> We could have that discussion in 6man, sure, but I don't believe that
>>> it's relevant to the question of whether draft-ietf-6man-oversized-
>>> header-chain
>>> is ready. This draft mitigates a known problem in terms of the
>> current
>>> IPv6 standards.
>>>
>
>

-- 
Regards,
RayH


From samita.chakrabarti@ericsson.com  Mon Oct 14 18:41:10 2013
Return-Path: <samita.chakrabarti@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B633D21E80A3; Mon, 14 Oct 2013 18:41:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sgiBEJtZ0HZS; Mon, 14 Oct 2013 18:41:05 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id B65CC11E8131; Mon, 14 Oct 2013 18:41:00 -0700 (PDT)
X-AuditID: c618062d-b7fda8e0000024c6-ca-525c9d294c4f
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id B7.91.09414.92D9C525; Tue, 15 Oct 2013 03:40:57 +0200 (CEST)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.02.0328.009; Mon, 14 Oct 2013 21:40:56 -0400
From: Samita Chakrabarti <samita.chakrabarti@ericsson.com>
To: "6man@ietf.org" <6man@ietf.org>, "6lo@ietf.org" <6lo@ietf.org>
Subject: FW: New Version Notification for draft-chakrabarti-nordmark-6man-efficient-nd-03.txt
Thread-Topic: New Version Notification for draft-chakrabarti-nordmark-6man-efficient-nd-03.txt
Thread-Index: AQHOyUXSwdYwXALTsUSF+vb3LrD5C5n0+VNQ
Date: Tue, 15 Oct 2013 01:40:56 +0000
Message-ID: <ECA43DA70480A3498E43C3471FB2E1F01C0E05DB@eusaamb103.ericsson.se>
References: <20131015012812.11455.31269.idtracker@ietfa.amsl.com>
In-Reply-To: <20131015012812.11455.31269.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.135]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrJLMWRmVeSWpSXmKPExsUyuXRPgq7m3Jggg3n7bSyapwhYrFxxl8mB yWPJkp9MAYxRXDYpqTmZZalF+nYJXBktjz+wFHTIVRybfJq5gXGJbBcjJ4eEgInEnFtzmCFs MYkL99azdTFycQgJHGWUmLX3ByOEs5xR4uTv8ywgVWwCVhIdvXvYQWwRASeJ+defgtnCAvES kzpuAdVwAMUTJJqO1kCUGEl8vDibCcRmEVCVePjyIZjNK+ArcfTHGbCRQgKOEj0XzjKC2JxA I09vnw12ECPQQd9PrQGrZxYQl7j1ZD4TxKECEkv2nIc6WlTi5eN/rBC2ssT3OY/ATmAW0JRY v0sfolVRYkr3Q3aItYISJ2c+YZnAKDoLydRZCB2zkHTMQtKxgJFlFSNHaXFqWW66kcEmRmDw H5Ng093BuOel5SFGaQ4WJXHeL2+dg4QE0hNLUrNTUwtSi+KLSnNSiw8xMnFwSjUwhqpdi7Vb 57HC53lU9Z+ZhrzLI5rETzkt0VvSzXtt1/Ib3x7VXfPoe9L+vbYqMCaITV2bveZp0uVlx2pY 2NRU2mJ0Dd4sDHlrZhcZ8i95Pvfqby8nbb60+iSLTrvlayvZTa5btD6/YWU+vPy6DqewphjD ykNvv/pcvFS/KjhM3cM/tFRsTXCYEktxRqKhFnNRcSIAXz53mUwCAAA=
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 15 Oct 2013 01:41:10 -0000

QW4gdXBkYXRlZCB2ZXJzaW9uKDAzKSBvZiBPcHRpbWl6ZWQgSVB2NiBORCAoV0lORCkgaGFzIGJl
ZW4gcHVibGlzaGVkLg0KDQpUaGlzIHZlcnNpb24gaGFzIGFkZHJlc3NlZCBtb3N0IG9mIHRoZSBj
b21tZW50cyB3ZSBkaXNjdXNzZWQgYW5kIGFncmVlZCBvbiB0aGUgY2hhbmdlcyBmb3IgdGhlIHVw
ZGF0ZS4NCg0KVGhhbmtzIHRvIEpvdW5pIEtvcmhvbmVuLCBBbmRyZXcgWW91cnRjaGVua2UsIExv
cmVuem8gQ29saXR0aSwgRGF2aWQgTWlsZXMsIEFuZGVycyBCcmFuZHQgZm9yIHlvdXIgdGhvcm91
Z2ggY29tbWVudHMuDQoNClBsZWFzZSByZXZpZXcgdGhpcyB2ZXJzaW9uICgwMykgYW5kIHdlIHBs
YW4gdG8gcHVibGlzaCBhbm90aGVyIHZlcnNpb24gYmVmb3JlIHRoZSBJRVRGIGN1dG9mZiBkYXRl
IG5leHQgd2Vlay4NCg0KDQpBIGZldyBjb21tZW50cyBhcmUgbm90IGFkZHJlc3NlZCBpbiB0aGlz
IHZlcnNpb24gYW5kIHdlJ2xsIGRpc2N1c3MgdGhlbSBzZXBhcmF0ZWx5IHRvIGNvbWUgdG8gYSBy
ZXNvbHV0aW9uLg0KDQpOb3RlIC0tIEkgdHJpZWQgdG8gZml4IG1hbnkgdHlwb3MsIGJ1dCBub3Qg
YWxsIG9mIHRoZW0gYXJlIGZpeGVkIGF0IHRoaXMgcG9pbnQuICANCg0KVGhhbmtzLA0KLVNhbWl0
YQ0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogaW50ZXJuZXQtZHJhZnRzQGll
dGYub3JnIFttYWlsdG86aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnXSANClNlbnQ6IE1vbmRheSwg
T2N0b2JlciAxNCwgMjAxMyA2OjI4IFBNDQpUbzogRXJpayBOb3JkbWFyazsgUGFzY2FsIFRodWJl
cnQ7IE1hcmdhcmV0IFdhc3Nlcm1hbjsgU2FtaXRhIENoYWtyYWJhcnRpDQpTdWJqZWN0OiBOZXcg
VmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIGRyYWZ0LWNoYWtyYWJhcnRpLW5vcmRtYXJrLTZtYW4t
ZWZmaWNpZW50LW5kLTAzLnR4dA0KDQoNCkEgbmV3IHZlcnNpb24gb2YgSS1ELCBkcmFmdC1jaGFr
cmFiYXJ0aS1ub3JkbWFyay02bWFuLWVmZmljaWVudC1uZC0wMy50eHQNCmhhcyBiZWVuIHN1Y2Nl
c3NmdWxseSBzdWJtaXR0ZWQgYnkgU2FtaXRhIENoYWtyYWJhcnRpIGFuZCBwb3N0ZWQgdG8gdGhl
IElFVEYgcmVwb3NpdG9yeS4NCg0KRmlsZW5hbWU6CSBkcmFmdC1jaGFrcmFiYXJ0aS1ub3JkbWFy
ay02bWFuLWVmZmljaWVudC1uZA0KUmV2aXNpb246CSAwMw0KVGl0bGU6CQkgV2lyZWQgYW5kIFdp
cmVsZXNzIElQdjYgTmVpZ2hib3IgRGlzY292ZXJ5IE9wdGltaXphdGlvbnMNCkNyZWF0aW9uIGRh
dGU6CSAyMDEzLTEwLTE1DQpHcm91cDoJCSBJbmRpdmlkdWFsIFN1Ym1pc3Npb24NCk51bWJlciBv
ZiBwYWdlczogMzINClVSTDogICAgICAgICAgICAgaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5l
dC1kcmFmdHMvZHJhZnQtY2hha3JhYmFydGktbm9yZG1hcmstNm1hbi1lZmZpY2llbnQtbmQtMDMu
dHh0DQpTdGF0dXM6ICAgICAgICAgIGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJh
ZnQtY2hha3JhYmFydGktbm9yZG1hcmstNm1hbi1lZmZpY2llbnQtbmQNCkh0bWxpemVkOiAgICAg
ICAgaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtY2hha3JhYmFydGktbm9yZG1hcmst
Nm1hbi1lZmZpY2llbnQtbmQtMDMNCkRpZmY6ICAgICAgICAgICAgaHR0cDovL3d3dy5pZXRmLm9y
Zy9yZmNkaWZmP3VybDI9ZHJhZnQtY2hha3JhYmFydGktbm9yZG1hcmstNm1hbi1lZmZpY2llbnQt
bmQtMDMNCg0KQWJzdHJhY3Q6DQogICBJUHY2IE5laWdoYm9yIERpc2NvdmVyeSAoUkZDIDQ4NjEp
IHByb3RvY29sIGhhcyBiZWVuIGRlc2lnbmVkIGZvcg0KICAgbmVpZ2hib3IncyBhZGRyZXNzIHJl
c29sdXRpb24sIHVucmVhY2hhYmlsaXR5IGRldGVjdGlvbiwgYWRkcmVzcw0KICAgYXV0b2NvbmZp
Z3VyYXRpb24sIHJvdXRlciBhZHZlcnRpc2VtZW50IGFuZCBzb2xpY2l0YXRpb24uICBXaXRoIHRo
ZQ0KICAgcHJvZ3Jlc3Mgb2YgSW50ZXJuZXQgYWRvcHRpb24gb24gdmFyaW91cyBpbmR1c3RyaWVz
IGluY2x1ZGluZyBob21lLA0KICAgd2lyZWxlc3MsIE0yTSBhbmQgY2VsbHVsYXIgbmV0d29ya3Mg
dGhlcmUgaXMgYSBkZXNpcmUgZm9yIG9wdGltaXppbmcNCiAgIHRoZSBsZWdhY3kgSVB2NiBOZWln
aGJvciBEaXNjb3ZlcnkgcHJvdG9jb2wuICBUaGlzIGRvY3VtZW50IGRlc2NyaWJlcw0KICAgYSBt
ZXRob2Qgb2Ygb3B0aW1pemF0aW9uIGJ5IHJlZHVjaW5nIG11bHRpY2FzdCBtZXNzYWdlcyBhbmQN
CiAgIGludHJvZHVjaW5nIGFuIElQdjYgYWRkcmVzcyBSZWdpc3RyYXRpb24gbWVjaGFuaXNtLiAg
VGhlIG9wdGltaXphdGlvbg0KICAgb2YgSVB2NiBOZWlnaGJvciBEaXNjb3ZlcnkgcHJvdG9jb2wg
aXMgdXNlZnVsIGZvciBXaXJsZXNzIGFuZCBsb3ctDQogICBwb3dlciBJUHY2IG5ldHdvcmtzIGFu
ZCBhcyB3ZWxsIGFzIERhdGEgQ2VudGVycyBhbmQgSG9tZSBOZXR3b3Jrcy4NCiAgIFRoZSBzb2x1
dGlvbiBpcyBjYXBhYmxlIG9mIGhhbmRsaW5nIGV4aXN0aW5nIGxlZ2FjeSBJUHY2IG5vZGVzIGlu
IHRoZQ0KICAgbmV0d29yayB3aXRoIGxvY2FsIG1vYmlsaXR5Lg0KDQogICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgDQoNCg0KUGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBhIGNvdXBsZSBvZiBt
aW51dGVzIGZyb20gdGhlIHRpbWUgb2Ygc3VibWlzc2lvbiB1bnRpbCB0aGUgaHRtbGl6ZWQgdmVy
c2lvbiBhbmQgZGlmZiBhcmUgYXZhaWxhYmxlIGF0IHRvb2xzLmlldGYub3JnLg0KDQpUaGUgSUVU
RiBTZWNyZXRhcmlhdA0KDQo=

From samita.chakrabarti@ericsson.com  Mon Oct 14 18:58:18 2013
Return-Path: <samita.chakrabarti@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BF1321E808F for <ipv6@ietfa.amsl.com>; Mon, 14 Oct 2013 18:58:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.556
X-Spam-Level: 
X-Spam-Status: No, score=-2.556 tagged_above=-999 required=5 tests=[AWL=0.043,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ORTnQ7Dv10dq for <ipv6@ietfa.amsl.com>; Mon, 14 Oct 2013 18:58:08 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 7782A21E80B0 for <ipv6@ietf.org>; Mon, 14 Oct 2013 18:58:08 -0700 (PDT)
X-AuditID: c6180641-b7fe28e000000d82-06-525ca12f1d3e
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 1A.70.03458.F21AC525; Tue, 15 Oct 2013 03:58:07 +0200 (CEST)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.02.0328.009; Mon, 14 Oct 2013 21:58:07 -0400
From: Samita Chakrabarti <samita.chakrabarti@ericsson.com>
To: Andrew Yourtchenko <ayourtch@cisco.com>, Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: RE: draft-chakrabarti-nordmark-6man-efficient-nd review
Thread-Topic: draft-chakrabarti-nordmark-6man-efficient-nd review
Thread-Index: AQHOkcnP4r4K+ymONk2WJnfIG/EPdJmfcESAgABS8ACAVavp4A==
Date: Tue, 15 Oct 2013 01:58:06 +0000
Message-ID: <ECA43DA70480A3498E43C3471FB2E1F01C0E0613@eusaamb103.ericsson.se>
References: <alpine.OSX.2.00.1308051246130.97248@ayourtch-mac> <52144475.9020101@ericsson.com> <alpine.OSX.2.00.1308211030250.44617@ayourtch-mac>
In-Reply-To: <alpine.OSX.2.00.1308211030250.44617@ayourtch-mac>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.135]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrCLMWRmVeSWpSXmKPExsUyuXRPoK7+wpggg1md+hZfm+exWbw8+57J YsHypSwWn17vZ7OYMeUdowOrx5TfG1k9liz5yeSxcfs6lgDmKC6blNSczLLUIn27BK6Mtcue sBd0cVf8a7jP1MDYyNnFyMkhIWAicXbyZyYIW0ziwr31bF2MXBxCAkcZJd5vWMQE4SxnlDj9 cwpYFZuAlURH7x52EFtEIFai7d0ddpAiZoEVjBIXPnWzgCSEBRwkvm1qYIMocpT4tnopVIOT xNybC8FqWARUJQ5sf8wIYvMK+Eos7ZzADrFtKqPE1VuHwJo5BewlPvdcA9vMCHTf91NrwGxm AXGJW0/mQ90tILFkz3lmCFtU4uXjf6wQtrLE9zmPWCDqdSQW7P7EBmFrSyxb+JoZYrGgxMmZ T1gmMIrNQjJ2FpKWWUhaZiFpWcDIsoqRo7Q4tSw33chwEyMwpo5JsDnuYFzwyfIQozQHi5I4 75e3zkFCAumJJanZqakFqUXxRaU5qcWHGJk4OKUaGP3mLl2kaZwr8/pW5P6K4CUf3ERfWHy9 Xme6T1x35YFKS4XUmsdrZvO12HK4T7yUplDpf6/jlvWJ5sC1DIUTNvnIdOVF/tp8OaZ4Itvq i/NkPaffX/DxGnucK6MY68TfHFXWu8WSxAtu3J9y1Id709rdi0JUtijkewjoVi9d/Oy1z0fu etNp9kosxRmJhlrMRcWJAJ6ucDV3AgAA
Cc: "nordmark@cisco.com" <nordmark@cisco.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "pthubert@cisco.com" <pthubert@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 15 Oct 2013 01:58:18 -0000

Suresh and Andrew:

 http://www.ietf.org/internet-drafts/draft-chakrabarti-nordmark-6man-effici=
ent-nd-03.txt

puts reference to the resilient RS draft and  says that the number of maxim=
um RS algorithm may be applicable in some scenarios.

Thanks for your valuable comments.
-Samita


-----Original Message-----
From: Andrew Yourtchenko [mailto:ayourtch@cisco.com]=20
Sent: Wednesday, August 21, 2013 2:36 AM
To: Suresh Krishnan
Cc: Samita Chakrabarti; nordmark@cisco.com; pthubert@cisco.com; mrw@lilacgl=
ade.org; ipv6@ietf.org
Subject: Re: draft-chakrabarti-nordmark-6man-efficient-nd review

Hi Suresh,

On Wed, 21 Aug 2013, Suresh Krishnan wrote:

> Hi Andrew,
>
> On 08/05/2013 06:51 AM, ayourtch wrote:
>> The RS sending mechanism will be resilient, I assume, such that the=20
>> node does get RA even in a high-loss environments, right  ? Maybe=20
>> useful to include a paragraph or two on the unreliability of this=20
>> mechanism. I think Suresh said he had something on this, probably worth =
referencing.
>
> Here is the draft I was talking about. The draft will go to WGLC soon.
>
> http://tools.ietf.org/html/draft-ietf-6man-resilient-rs-01

This is a much needed work, awesome, thanks!

I hope we see all hosts doing it soon.

(I've a couple of Qs on the resilient RS, I'll unicast them, to avoid the t=
hread pollution).

--a

>
> Thanks
> Suresh
>

From brian.e.carpenter@gmail.com  Mon Oct 14 19:03:04 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CF8B21E808C; Mon, 14 Oct 2013 19:03:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.57
X-Spam-Level: 
X-Spam-Status: No, score=-102.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j7o1GGz8klmR; Mon, 14 Oct 2013 19:03:03 -0700 (PDT)
Received: from mail-pd0-x236.google.com (mail-pd0-x236.google.com [IPv6:2607:f8b0:400e:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id C27A221E80E9; Mon, 14 Oct 2013 19:03:01 -0700 (PDT)
Received: by mail-pd0-f182.google.com with SMTP id r10so8241712pdi.27 for <multiple recipients>; Mon, 14 Oct 2013 19:03:01 -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=R0XWlNRTwUEBuwNNBlBHumok2bfQSgjxmjoFpl4trMw=; b=f/+9+eDI3erVttqb9jVe0vlCGrhWamNaTsovjMZY/qJJK0WzdbGMLWIPb4BnpDjV/F fnqSJWULyLg2bCcPy9LqOpLJFxFjxupe+Gl4Bh10YgThyRHzdnY+p4IVdIqUACHTpaSs LTMtkmjcZXYjDSFMGwModbneosC91aGvogNhZcWdGx9iKjSsV7moHb5ZLb3aK4yjvmvr iSL4YtBNQAPqrbBujtBvFio5zsA3qX0nxRis3BD7LjeTduqsHlpM+2XGJsMGRVUlqwPQ f1t03DkDz9ZZca2bgmMcG64wt6YRm8rGSiinDW403MyoMJ7s3vIr5luk86wXGKVtlIDH 1wIg==
X-Received: by 10.66.178.143 with SMTP id cy15mr41057806pac.105.1381802566351;  Mon, 14 Oct 2013 19:02:46 -0700 (PDT)
Received: from [192.168.178.20] (19.202.69.111.dynamic.snap.net.nz. [111.69.202.19]) by mx.google.com with ESMTPSA id ha10sm80901905pbc.23.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 14 Oct 2013 19:02:45 -0700 (PDT)
Message-ID: <525CA244.5010503@gmail.com>
Date: Tue, 15 Oct 2013 15:02:44 +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: IESG <iesg@ietf.org>
Subject: Re: WG Review: IPv6 Maintenance (6man)
References: <20131011163832.4882.45248.idtracker@ietfa.amsl.com>
In-Reply-To: <20131011163832.4882.45248.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 15 Oct 2013 02:03:04 -0000

On 12/10/2013 05:38, The IESG wrote:

>   Mar 2014 - Develop approach for IPv6 Fragmentation

Possibly ambitious, but it is the logical next step beyond
draft-ietf-6man-oversized-header-chain.

>   Mar 2014 - Develop approaches for IPv6 Extension Headers (Hop-by-Hop
> and Destination)

Shouldn't the first step be to develop a problem statement, once the
current drafts relevant to this topic are done and dusted?

>   Jul 2014 - Advance IPv6 core specifications to Internet standard

That date is ambitious.

I think there's a missing goal, something like

 - Define relationship and boundary between DHCPv6-based and RA/ND-based
   host configuration mechanisms. (This is partly an operational topic, but
   it lies behind a whole bunch of discussions in various WGs).

     Brian

From samita.chakrabarti@ericsson.com  Mon Oct 14 19:32:04 2013
Return-Path: <samita.chakrabarti@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59DA711E8167; Mon, 14 Oct 2013 19:32:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.561
X-Spam-Level: 
X-Spam-Status: No, score=-2.561 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AzfkZ1Uqy9HV; Mon, 14 Oct 2013 19:31:57 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id DFFCF11E816B; Mon, 14 Oct 2013 19:31:55 -0700 (PDT)
X-AuditID: c618062d-b7fda8e0000024c6-64-525ca91a1905
Received: from EUSAAHC002.ericsson.se (Unknown_Domain [147.117.188.78]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id A9.22.09414.B19AC525; Tue, 15 Oct 2013 04:31:55 +0200 (CEST)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC002.ericsson.se ([147.117.188.78]) with mapi id 14.02.0328.009; Mon, 14 Oct 2013 22:31:54 -0400
From: Samita Chakrabarti <samita.chakrabarti@ericsson.com>
To: Anders Brandt <Anders_Brandt@sigmadesigns.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "Pascal Thubert (pthubert)" <pthubert@cisco.com>, "Erik Nordmark (nordmark)" <nordmark@cisco.com>, "mrw@lilacglade.org" <mrw@lilacglade.org>, "6lo@ietf.org" <6lo@ietf.org>
Subject: RE: draft-chakrabarti-nordmark-6man-efficient-nd - Proposing new use case "Set-and-forget off-line network"
Thread-Topic: draft-chakrabarti-nordmark-6man-efficient-nd - Proposing new use case "Set-and-forget off-line network"
Thread-Index: Ac6nvfE2x6FkrNIjTOOkpcG1IHS+Pwhj/HTw
Date: Tue, 15 Oct 2013 02:31:53 +0000
Message-ID: <ECA43DA70480A3498E43C3471FB2E1F01C0E0665@eusaamb103.ericsson.se>
References: <03F31C213F2C6941BFDDBB4336E9E6CD41B5D26C@cph-ex1>
In-Reply-To: <03F31C213F2C6941BFDDBB4336E9E6CD41B5D26C@cph-ex1>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.135]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrDLMWRmVeSWpSXmKPExsUyuXSPn670ypgggxkvRC2apwhYHH12gtHi 5dn3TBYLli9lsfj0ej+bxYwp7xgd2Dym/N7I6rFkyU8mj43b17F47H1xhzmAJYrLJiU1J7Ms tUjfLoEr40bHV7aCG1IVXcuXsDUwrhbpYuTkkBAwkfh+4AkThC0mceHeerYuRg4OIYGjjBKT PLoYuYDM5YwSTTdPsoPUsAlYSXT07mEHSYgItDFJHPrZyQrSICxQJrH+FxOIKSJQLvHzjglI uYiAkUTH742MIDaLgKrEpD9rwGxeAV+JfVc3sYHYQgJ2Es96eplBbE4Be4mZM5pZQGxGoHO+ n1oDdhqzgLjErSfzoc4UkFiy5zwzhC0q8fLxP1YIW1ni+5xHLBD1OhILdn9ig7C1JZYtfM0M sVdQ4uTMJywTGEVnIRk7C0nLLCQts5C0LGBkWcXIUVqcWpabbmSwiREYQ8ck2HR3MO55aXmI UZqDRUmc98tb5yAhgfTEktTs1NSC1KL4otKc1OJDjEwcnFINjIxHHrRwslrKHXi35lzYDqct P1W2y8m/fNd3MHRBMK95W/x2rx8aJfsDLwc+kHgiPPvlpO+2AWZn3qk5SfJ76zaI3GU/rrjk Q3nMqrpvTkluehddxC33rLHLvN/QZ/ghm+exSNetm6+ePpT22Fd4L4jZfmXT/E5tW0c1qQqO c6FqrIvYfD+GKLEUZyQaajEXFScCAKpI2xtvAgAA
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 15 Oct 2013 02:32:04 -0000

Hi Anders,

Thanks for your detail comments -- those are quite useful!

Please see in-line.

-----Original Message-----
From: Anders Brandt [mailto:Anders_Brandt@sigmadesigns.com]=20
Sent: Monday, September 02, 2013 2:44 AM
To: ipv6@ietf.org; Pascal Thubert (pthubert); Samita Chakrabarti; Erik Nord=
mark (nordmark); mrw@lilacglade.org
Subject: draft-chakrabarti-nordmark-6man-efficient-nd - Proposing new use c=
ase "Set-and-forget off-line network"

[cross-posting 6man / 6lo]

Samita Chakrabarti et al,

Great draft which addresses important issues for low-power wireless network=
 technologies.

After reading the draft, it seems to me that you would benefit adding one m=
ore use case - and addressing the derived requirement(s).

Proposed use case:
-------
A.7.  Set-and-forget off-line networks
    Home control modules designed for networked environments may be deploye=
d =20
    in very simple settings like garden path lighting controlled by wireles=
s =20
    light and motion sensors. Once the network has been created and sensors=
 =20
    have been associated with the light modules, the installer takes away t=
he =20
    configuration tool which was used to set up the network. Most likely a =
ULA =20
    prefix is used, since multiple hops may be needed. None of the sensors =
and =20
    light modules has the capability of handing out fresh prefixes. Thus, f=
or =20
    a set-and-forget style off-line network to work, the nodes must be  abl=
e to
    operate forever without trying to refresh its address registration.

    In another instance of an off-line network, a key-fob style remote cont=
rol is paired
    to a few lamp modules. The controller creates its own small off-line ne=
twork.
    The controller is not only battery powered and sleeping. It is far away=
 in its owner's pocket.
    Address registration is not possible.
=20
     The manufacturer of the lamp module wants to sell exactly the same lam=
p
     module to large network deployments where address registration is used=
.
     Since this class of devices provide no local configuration interface, =
the behaviour needs
     to be controlled via some sort of auto-configuration.
-------
(end of proposed use case)=20

[SC>]  =3D=3D=3D> Added.

One solution could be to introduce a special interpretation of registration=
 lifetime 0xFFFF as infinite and stating that default routers SHOULD NOT ad=
vertise this value.

Such an approach would resemble existing text in RFC4861:

 Valid Lifetime
                      32-bit unsigned integer.  The length of time in
                      seconds (relative to the time the packet is sent)
                      that the prefix is valid for the purpose of on-link
                      determination.  A value of all one bits
                      (0xffffffff) represents infinity.  The Valid
                      Lifetime is also used by [ADDRCONF].


The authors may have other preferred solutions?
[SC>] =3D=3D=3D> As discussed off-line that , the valid lifetime for the pr=
efix is still valid and the ARO lifetime applies to the registration lifeti=
me.  We have discussed some of the issues with  allowing permanent registra=
tion (especially with NCE cache entries). So at this point we have agreed  =
to keep the ARO lifetime range as it is.

Best regards,
-Samita




From samita.chakrabarti@ericsson.com  Mon Oct 14 19:42:17 2013
Return-Path: <samita.chakrabarti@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0585C21E80B0 for <ipv6@ietfa.amsl.com>; Mon, 14 Oct 2013 19:42:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.565
X-Spam-Level: 
X-Spam-Status: No, score=-2.565 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dw6x6LczPXmj for <ipv6@ietfa.amsl.com>; Mon, 14 Oct 2013 19:42:10 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id AD08621E808F for <6man@ietf.org>; Mon, 14 Oct 2013 19:42:09 -0700 (PDT)
X-AuditID: c618062d-b7fda8e0000024c6-da-525cab7a0e7f
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 32.42.09414.A7BAC525; Tue, 15 Oct 2013 04:42:02 +0200 (CEST)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.02.0328.009; Mon, 14 Oct 2013 22:41:55 -0400
From: Samita Chakrabarti <samita.chakrabarti@ericsson.com>
To: "Lorenzo Colitti (lorenzo@google.com)" <lorenzo@google.com>, "David Miles (davidmiles@google.com)" <davidmiles@google.com>
Subject: Updated Optimized IPv6-ND (aka WIND)
Thread-Topic: Updated Optimized IPv6-ND (aka WIND)
Thread-Index: Ac7JTunMZLjGnM4lRImguwaEqMalhw==
Date: Tue, 15 Oct 2013 02:41:55 +0000
Message-ID: <ECA43DA70480A3498E43C3471FB2E1F01C0E068D@eusaamb103.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.135]
Content-Type: multipart/alternative; boundary="_000_ECA43DA70480A3498E43C3471FB2E1F01C0E068Deusaamb103erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrOLMWRmVeSWpSXmKPExsUyuXRPuG7V6pggg3VtRhYrV9xlstjUfoLV Yv3pd4wWLzs3sFnMmPKO0YHVY8rvjaweCzaVeixZ8pPJ42l3M0sASxSXTUpqTmZZapG+XQJX xszbh1gKDrpUfD82l7WBcZtNFyMnh4SAicSCSQeZIGwxiQv31rN1MXJxCAkcZZR41HeOESQh JLCcUeLPnHAQm03ASqKjdw87SJGIQAOjxPJ5V8E6mAW6GSVu/v7NBlIlLKArcWDaXXYQW0TA SOLklztsELaexOuZK8HiLAKqEmcPngBbzSvgK/H5XiuYzQh0xvdTa8BsZgFxiVtP5kOdJyCx ZM95ZghbVOLl43+sELayxPc5j1gg6vMlbl0+wwYxU1Di5MwnLBMYhWchGTULSdksJGUQcR2J Bbs/sUHY2hLLFr5mhrHPHHjMhCy+gJF9FSNHaXFqWW66kcEmRmBkHZNg093BuOel5SFGaQ4W JXHeL2+dg4QE0hNLUrNTUwtSi+KLSnNSiw8xMnFwSjUwBvyeX7D7wT+XsMjra0xvlx5/F+fF sUH12K6pOqkJzg7aPx81aYYvFmGT1k7xeaDstz9pu0PF1ikZNvYfA5hZ9cIdZrnULPf1uWG3 QFopziXhWvVr/3tz6nLMHl24dvtP8mqPfeLbeB4ttE3q+8jeHmzIPOFQedyLHfO+Hrl89+Sa vYnnZ7QHKLEUZyQaajEXFScCAI6lE0J6AgAA
Cc: "pthubert@cisco.com" <pthubert@cisco.com>, "6man@ietf.org" <6man@ietf.org>, "Erik Nordmark \(nordmark@sonic.net\)" <nordmark@sonic.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 15 Oct 2013 02:42:17 -0000

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

Hi Lorenzo and David,


Thanks for taking time to discuss   draft-chakrabarti-nordmark-6man-efficie=
nt-nd with us.

We have incorporated your comments in the version 03:


1)      Clarify problem statement and clarify the basic part of the optimiz=
ation

2)      Clarify that the registration supports multiple addresses (example:=
 privacy address)

3)      Talk to MSFT (Dave T.) and Apple (Stuart Cheshire) for their review

The following comment needs some more clarification:
1)      Think about supporting APs in mixed mode  network

Can you please clarify whether you would like to see an example case in the=
 usecase analysis section or you would like the co-authors to think about a=
ny protocol implications in the optimized-ND behavior in case of mixed-mode=
 AP.

I presume, it is the latter, however it'd be good if you can clarify the is=
sues you might be envisioning.

Thanks,
-Samita


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:67502091;
	mso-list-type:hybrid;
	mso-list-template-ids:-259203930 67698705 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:824971374;
	mso-list-type:hybrid;
	mso-list-template-ids:-259203930 67698705 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi Lorenzo and David,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks for taking time to discuss&nbsp; &nbsp;draft-=
chakrabarti-nordmark-6man-efficient-nd with us.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">We have incorporated your comments in the version 03=
:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">1)<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Clarify problem statement and clarify the basic par=
t of the optimization
<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">2)<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Clarify that the registration supports multiple add=
resses (example: privacy address)<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">3)<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Talk to MSFT (Dave T.) and Apple (Stuart Cheshire) =
for their review
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The following comment needs some more clarification:=
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in;text-indent:-.25in;mso-lis=
t:l0 level1 lfo3">
<![if !supportLists]><span style=3D"mso-list:Ignore">1)<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Think about supporting APs in mixed mode&nbsp; netw=
ork<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">Can you please clarify wh=
ether you would like to see an example case in the usecase analysis section=
 or you would like the co-authors to think about any protocol implications =
in the optimized-ND behavior in case
 of mixed-mode AP.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I presume, it is the latter, however it&#8217;d be g=
ood if you can clarify the issues you might be envisioning.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks,<o:p></o:p></p>
<p class=3D"MsoNormal">-Samita<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_ECA43DA70480A3498E43C3471FB2E1F01C0E068Deusaamb103erics_--

From leo.liubing@huawei.com  Mon Oct 14 20:02:57 2013
Return-Path: <leo.liubing@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD64221E8144; Mon, 14 Oct 2013 20:02:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZVYQ5yGqpl4q; Mon, 14 Oct 2013 20:02:53 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id F2E3821E813D; Mon, 14 Oct 2013 20:02:52 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AZC02790; Tue, 15 Oct 2013 03:02:52 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.146.0; Tue, 15 Oct 2013 04:02:02 +0100
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.146.0; Tue, 15 Oct 2013 04:02:50 +0100
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.141]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.03.0146.000; Tue, 15 Oct 2013 11:02:42 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, IESG <iesg@ietf.org>
Subject: RE: WG Review: IPv6 Maintenance (6man)
Thread-Topic: WG Review: IPv6 Maintenance (6man)
Thread-Index: AQHOxqBm4TnGDclWd0iQZV9FIU+J05n0gegAgACLYBA=
Date: Tue, 15 Oct 2013 03:02:42 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D7C97F4@nkgeml506-mbx.china.huawei.com>
References: <20131011163832.4882.45248.idtracker@ietfa.amsl.com> <525CA244.5010503@gmail.com>
In-Reply-To: <525CA244.5010503@gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.132]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 15 Oct 2013 03:02:57 -0000

Hi, Dear all

> -----Original Message-----
> From: Brian E Carpenter ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.o=
rg] On Behalf Of
> I think there's a missing goal, something like
>=20
>  - Define relationship and boundary between DHCPv6-based and
> RA/ND-based host configuration mechanisms. (This is partly an=20
> operational topic, but it lies behind a whole bunch of discussions in var=
ious WGs).

[Bing] I support this topic. Personally, I've got involved into a specific =
issue on this topic, which is regarding the ND/DHCPv6 interaction on host c=
onfiguration.=20

More specifically, one example is the variation of the host behavior of int=
erpreting the M/O flags. Different operating systems have followed differen=
t ways. This is because the M/O behaviors defined in current ND/SLAAC stand=
ards are ambiguous. This issue was firstly raised in [RFC5887] (See details=
 in Section 5.1.1, the 6th&7th paragraph), and then identified as a gap in =
[RFC7010] (See Section 5.1).=20
We also have raised a couple of times discussion in 6man, the most recent o=
ne was in IETF84 (http://www.ietf.org/proceedings/84/slides/slides-84-6man-=
3.pptx).=20

There were not a few people participated in the discussion of the above iss=
ue, IIRC, the majority of them agreed the problem. So I think it would be g=
ood to if it could be added in the charter.

Best regards,
Bing

From leo.liubing@huawei.com  Mon Oct 14 22:52:46 2013
Return-Path: <leo.liubing@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96F7A21E80AE; Mon, 14 Oct 2013 22:52:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.399
X-Spam-Level: 
X-Spam-Status: No, score=-6.399 tagged_above=-999 required=5 tests=[AWL=0.200,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 49SCZF6SshPd; Mon, 14 Oct 2013 22:52:42 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id E82ED11E80F5; Mon, 14 Oct 2013 22:52:41 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AZC10637; Tue, 15 Oct 2013 05:52:40 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.146.0; Tue, 15 Oct 2013 06:51:47 +0100
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.146.0; Tue, 15 Oct 2013 06:52:37 +0100
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.141]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0146.000; Tue, 15 Oct 2013 13:52:30 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: IESG <iesg@ietf.org>, 6man WG <ipv6@ietf.org>
Subject: RE: WG Review: IPv6 Maintenance (6man)
Thread-Topic: WG Review: IPv6 Maintenance (6man)
Thread-Index: AQHOxqBm4TnGDclWd0iQZV9FIU+J05n0gegAgACLYBCAADnOUA==
Date: Tue, 15 Oct 2013 05:52:28 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D7C9836@nkgeml506-mbx.china.huawei.com>
References: <20131011163832.4882.45248.idtracker@ietfa.amsl.com> <525CA244.5010503@gmail.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D7C97F4@nkgeml506-mbx.china.huawei.com>
In-Reply-To: <8AE0F17B87264D4CAC7DE0AA6C406F453D7C97F4@nkgeml506-mbx.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.132]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 15 Oct 2013 05:52:46 -0000

> More specifically, one example is the variation of the host behavior of
> interpreting the M/O flags. Different operating systems have followed
> different ways. This is because the M/O behaviors defined in current
> ND/SLAAC standards are ambiguous. This issue was firstly raised in [RFC58=
87]
> (See details in Section 5.1.1, the 6th&7th paragraph), and then identifie=
d as a
> gap in [RFC7010] (See Section 5.1).
> We also have raised a couple of times discussion in 6man, the most recent
> one was in IETF84
> (http://www.ietf.org/proceedings/84/slides/slides-84-6man-3.pptx).

[Bing] Sorry, above is the former one, the most recent one is in IETF86:=20
www.ietf.org/proceedings/86/slides/slides-86-6man-4.pdf

Best regards,
Bing

From Fred.L.Templin@boeing.com  Tue Oct 15 06:56:29 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E795211E8128; Tue, 15 Oct 2013 06:56:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.488
X-Spam-Level: 
X-Spam-Status: No, score=-6.488 tagged_above=-999 required=5 tests=[AWL=0.111,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 97SLGiOri6Wk; Tue, 15 Oct 2013 06:56:19 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (stl-mbsout-01.boeing.com [130.76.96.169]) by ietfa.amsl.com (Postfix) with ESMTP id BDD2F11E8138; Tue, 15 Oct 2013 06:55:41 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9FDtZU8027597; Tue, 15 Oct 2013 08:55:35 -0500
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9FDsT4b025711 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 15 Oct 2013 08:55:34 -0500
Received: from XCH-BLV-208.nw.nos.boeing.com (10.57.37.5) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Tue, 15 Oct 2013 06:55:24 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-BLV-208.nw.nos.boeing.com ([169.254.8.27]) with mapi id 14.03.0158.001; Tue, 15 Oct 2013 06:55:24 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ray Hunter <v6ops@globis.net>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOySFFebc9KTehbEGO6mhunuAlj5n1xs+A
Date: Tue, 15 Oct 2013 13:55:23 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812E34F@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com> <525C5CDE.3000604@globis.net>
In-Reply-To: <525C5CDE.3000604@globis.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "ietf@ietf.org" <ietf@ietf.org>, 6man Mailing List <ipv6@ietf.org>, Fernando Gont <fgont@si6networks.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 15 Oct 2013 13:56:29 -0000

Hi Ray,

> -----Original Message-----
> From: Ray Hunter [mailto:v6ops@globis.net]
> Sent: Monday, October 14, 2013 2:07 PM
> To: Templin, Fred L
> Cc: Ronald Bonica; Brian E Carpenter; Fernando Gont; 6man Mailing List;
> ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> > Templin, Fred L <mailto:Fred.L.Templin@boeing.com>
> > 14 October 2013 19:39
> > Hi Ron,
> >
> >> -----Original Message-----
> >> From: Ronald Bonica [mailto:rbonica@juniper.net]
> >> Sent: Saturday, October 12, 2013 7:07 PM
> >> To: Brian E Carpenter; Templin, Fred L
> >> Cc: Fernando Gont; 6man Mailing List; ietf@ietf.org; Ray Hunter
> >> Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-
> 08.txt>
> >> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
> >>
> >> +1
> >>
> >> Is there a way to decouple this discussion from draft-ietf-6man-
> >> oversized-header-chain? I would be glad to discuss it in the context
> of
> >> a separate draft.
> >
> > I don't know if there is a way to decouple it. I believe I have shown
> > a way to not mess up tunnels while at the same time not messing up
> your
> > draft. That should be a win-win. In what way would imposing a 1K
> limit
> > on the IPv6 header chain not satisfy the general case?
> >
> > Thanks - Fred
> > fred.l.templin@boeing.com
>=20
> This draft may not go as far as you'd like (e.g. specifying a hard
> limit
> on header length as some proportion of MTU), and I'm also aware of the
> issue of MTU fragmentation and nested tunnels, but I'm still not clear
> on how this draft specifically "messes up tunnels."
>
> Can you explain what specific text in the current draft you consider
> harmful?

That hosts would be permitted to send MTU-sized header chains.

> And why that couldn't be dealt with in a later draft (that imposes
> additional limits on header chains in specific scenarios)?

Once a spec says that a host is permitted to send MTU-sized header
chains the die is cast and no later draft will be able to undo it.
The host has no idea that there may be one or more tunnels in the
path, and so has no way of knowing to alter its behavior to be
kind to tunnels.

That, plus the fact that attackers will be able to craft packets
intended to fool middleboxes by sending a fragmented tunneled
packet with the "good" part of the header chain in the first
fragment and the "bad" part of the header chain in the second
fragment.

Thanks - Fred
fred.l.templin@boeing.com


> Thanks.
>=20
>=20
> >
> >>                                                              Ron
> >>
> >>
> >>>> So, it wasn't necessarily the case that 1280 was a product of
> >>>> "thoughtful analysis" so much as the fact that **they were rushing
> >> to
> >>>> get a spec out the door**. So now, 16 years later, we get to put
> it
> >>>> back on the 6man charter milestone list.
> >>> We could have that discussion in 6man, sure, but I don't believe
> that
> >>> it's relevant to the question of whether draft-ietf-6man-oversized-
> >>> header-chain
> >>> is ready. This draft mitigates a known problem in terms of the
> >> current
> >>> IPv6 standards.
> >>>
> >
> >
>=20
> --
> Regards,
> RayH


From Fred.L.Templin@boeing.com  Tue Oct 15 07:04:14 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B8E311E817B; Tue, 15 Oct 2013 07:04:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.494
X-Spam-Level: 
X-Spam-Status: No, score=-6.494 tagged_above=-999 required=5 tests=[AWL=0.105,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21RlHvLRm-0w; Tue, 15 Oct 2013 07:04:07 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) by ietfa.amsl.com (Postfix) with ESMTP id E234521F9E1A; Tue, 15 Oct 2013 07:04:07 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9FE47b1029286; Tue, 15 Oct 2013 07:04:07 -0700
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9FE3x8h029115 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 15 Oct 2013 07:04:07 -0700
Received: from XCH-BLV-301.nw.nos.boeing.com (130.247.25.213) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Tue, 15 Oct 2013 07:04:04 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-BLV-301.nw.nos.boeing.com ([169.254.1.164]) with mapi id 14.03.0158.001; Tue, 15 Oct 2013 07:04:04 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOyRRhebc9KTehbEGO6mhunuAlj5n1ypVw
Date: Tue, 15 Oct 2013 14:04:03 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812E381@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <2134F8430051B64F815C691A62D9831812D718@XCH-BLV-504.nw.nos.boeing.com> <525C473D.4080403@gmail.com>
In-Reply-To: <525C473D.4080403@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: Fernando Gont <fgont@si6networks.com>, 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 15 Oct 2013 14:04:14 -0000

SGkgQnJpYW4sDQoNCj4gVGhlIGRyYWZ0IG1pdGlnYXRlcyBhIGtub3duIHByb2JsZW0gd2l0aCBj
b21tdW5pY2F0aW9uIHBhdGhzIHRoYXQNCj4gZG8gbm90IGluY2x1ZGUgbmVzdGVkIHR1bm5lbHMg
cmVxdWlyaW5nIG5lc3RlZCBmcmFnbWVudGF0aW9uLA0KPiB3aGVyZSB0aGUgbmVzdGVkIHR1bm5l
bCBoYXMgdG8gZGVhbCB3aXRoIGFuIE1UVSA8MTI4MCAqYW5kKiB3aGVyZQ0KPiB0aGUgbmVzdGVk
IHR1bm5lbCBnb2VzIHRocm91Z2ggYSBmaXJld2FsbCB0aGF0IHdhbnRzIHRvIGFuYWx5c2UNCj4g
dGhlIGNvbXBsZXRlIGhlYWRlciBjaGFpbiBvZiB0aGUgaW5uZXJtb3N0IHBhY2tldC4NCg0KSSB3
YW50IHRvIHNheSBvbmUgbW9yZSB3b3JkIG9uIHRoaXMuIFlvdSBzZWVtIHRvIGJlIGluZGljYXRp
bmcgdGhhdA0KeW91IHNlZSB3aGF0IEkgaGF2ZSBiZWVuIGV4cGxhaW5pbmcgYXMgYSBjb3JuZXIg
Y2FzZS4gQnV0LCBJIGJlbGlldmUNCnRoYXQgaW4gb3JkZXIgdG8gZml4IHRoZSB0dW5uZWwgTVRV
IGlzc3VlIHdlIHdpbGwgbmVlZCBTRUFMIG9yDQpzb21ldGhpbmcgdmVyeSBtdWNoIGxpa2UgaXQu
DQoNClNFQUwgdXNlcyBmcmFnbWVudGF0aW9uIG9uIHRoZSBmaXJzdCBmZXcgcGFja2V0cyByZWdh
cmRsZXNzIG9mIHRoZQ0KcGF0aCBNVFUgdG8gZW5zdXJlIHRoYXQgIm1pZGRsZSBzaXplZCIgcGFj
a2V0cyBiZXR3ZWVuIDEyODAtMTUwMA0KZ2V0IHRocm91Z2guIEl0IHRoZW4gdHVybnMgb2ZmIHRo
ZSBmcmFnbWVudGF0aW9uIHVzaW5nIGEgcHJvYmluZw0Kc2NoZW1lIGluIHRoZSBzcGlyaXQgb2Yg
UkZDNDgyMS4gU28sIHRob3NlIGZpcnN0IGZldyBwYWNrZXRzIHRoYXQNCmNvdWxkIGNvbnRhaW4g
YSBoZWFkZXIgY2hhaW4gdGhhdCBzcGlsbHMgb3ZlciBpbnRvIHRoZSBzZWNvbmQNCmZyYWdtZW50
IGFyZSB3aGF0IGNvbmNlcm5zIG1lLiBBbmQsIHRoaXMgd2lsbCBub3QgYmUgYSBjb3JuZXINCmNh
c2Ugd2hlbiBTRUFMIGlzIHVzZWQgaW4gd2lkZXIgZGVwbG95bWVudC4NCg0KVGhhbmtzIC0gRnJl
ZA0KZnJlZC5sLnRlbXBsaW5AYm9laW5nLmNvbQ0KDQo=

From v6ops@globis.net  Tue Oct 15 09:29:56 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98B1021F9D0C; Tue, 15 Oct 2013 09:29:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YB6AxTk-1dUq; Tue, 15 Oct 2013 09:29:56 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 46CA321F9E8D; Tue, 15 Oct 2013 09:29:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id B505187007E; Tue, 15 Oct 2013 18:29:45 +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 RjwgqsZjCcsl; Tue, 15 Oct 2013 18:29:45 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 66D34870076; Tue, 15 Oct 2013 18:29:45 +0200 (CEST)
Message-ID: <525D6D78.5040907@globis.net>
Date: Tue, 15 Oct 2013 18:29:44 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com> <525C5CDE.3000604@globis.net> <2134F8430051B64F815C691A62D9831812E34F@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831812E34F@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>, 6man Mailing List <ipv6@ietf.org>, Fernando Gont <fgont@si6networks.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 15 Oct 2013 16:29:56 -0000

> Templin, Fred L <mailto:Fred.L.Templin@boeing.com>
> 15 October 2013 15:55
> Hi Ray,
>
>> -----Original Message-----
>> From: Ray Hunter [mailto:v6ops@globis.net]
>> Sent: Monday, October 14, 2013 2:07 PM
>> To: Templin, Fred L
>> Cc: Ronald Bonica; Brian E Carpenter; Fernando Gont; 6man Mailing List;
>> ietf@ietf.org
>> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
>> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>>
>>> Templin, Fred L <mailto:Fred.L.Templin@boeing.com>
>>> 14 October 2013 19:39
>>> Hi Ron,
>>>
>>>> -----Original Message-----
>>>> From: Ronald Bonica [mailto:rbonica@juniper.net]
>>>> Sent: Saturday, October 12, 2013 7:07 PM
>>>> To: Brian E Carpenter; Templin, Fred L
>>>> Cc: Fernando Gont; 6man Mailing List; ietf@ietf.org; Ray Hunter
>>>> Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-
>> 08.txt>
>>>> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>>>>
>>>> +1
>>>>
>>>> Is there a way to decouple this discussion from draft-ietf-6man-
>>>> oversized-header-chain? I would be glad to discuss it in the context
>> of
>>>> a separate draft.
>>> I don't know if there is a way to decouple it. I believe I have shown
>>> a way to not mess up tunnels while at the same time not messing up
>> your
>>> draft. That should be a win-win. In what way would imposing a 1K
>> limit
>>> on the IPv6 header chain not satisfy the general case?
>>>
>>> Thanks - Fred
>>> fred.l.templin@boeing.com
>> This draft may not go as far as you'd like (e.g. specifying a hard
>> limit
>> on header length as some proportion of MTU), and I'm also aware of the
>> issue of MTU fragmentation and nested tunnels, but I'm still not clear
>> on how this draft specifically "messes up tunnels."
>>
>> Can you explain what specific text in the current draft you consider
>> harmful?
>
> That hosts would be permitted to send MTU-sized header chains.

They can do that today. In fact they can legally send n* MTU-sized
header chains, as long as the total length of an IPv6 packet is not
exceeded.
>> And why that couldn't be dealt with in a later draft (that imposes
>> additional limits on header chains in specific scenarios)?
>
> Once a spec says that a host is permitted to send MTU-sized header
> chains the die is cast and no later draft will be able to undo it.

Why not? If this is a "maximum", there may always be scenarios where
less than a maximum is appropriate.
> The host has no idea that there may be one or more tunnels in the
> path, and so has no way of knowing to alter its behavior to be
> kind to tunnels.

RFC 2473 is pretty explicit about how to handle fragmentation (in the
presence of nested IPv6 tunnels).

Once a packet is encapsulated in a tunnel it becomes a new "original
packet" for the next tunnel in any nested tunnel scenario.

And PMTUD on the originating host (whether that's the original host, or
the tunnel entry point at the previous nesting level) should receive a
signal if the current tunnel entry node cannot handle encapsulation due
to MTU issues (Section 7 of RFC 2473). So the originating host should
always be informed of the MTU issue, and be able to alter its behavior
accordingly.

So again, I don't see what's new in this draft.
> That, plus the fact that attackers will be able to craft packets
> intended to fool middleboxes by sending a fragmented tunneled
> packet with the "good" part of the header chain in the first
> fragment and the "bad" part of the header chain in the second
> fragment.
IMHO They can do that today (and worse).
> Thanks - Fred
> fred.l.templin@boeing.com
>
>
>> Thanks.
>>
>>
>>>>                                                              Ron
>>>>
>>>>
>>>>>> So, it wasn't necessarily the case that 1280 was a product of
>>>>>> "thoughtful analysis" so much as the fact that **they were rushing
>>>> to
>>>>>> get a spec out the door**. So now, 16 years later, we get to put
>> it
>>>>>> back on the 6man charter milestone list.
>>>>> We could have that discussion in 6man, sure, but I don't believe
>> that
>>>>> it's relevant to the question of whether draft-ietf-6man-oversized-
>>>>> header-chain
>>>>> is ready. This draft mitigates a known problem in terms of the
>>>> current
>>>>> IPv6 standards.
>>>>>
>> --
>> Regards,
>> RayH
>


From brian@innovationslab.net  Tue Oct 15 10:02:10 2013
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09DB411E8140; Tue, 15 Oct 2013 10:02:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.589
X-Spam-Level: 
X-Spam-Status: No, score=-102.589 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YOhZvioF8Z3J; Tue, 15 Oct 2013 10:02:03 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 0EF9911E80E3; Tue, 15 Oct 2013 10:01:57 -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 006DC880D1; Tue, 15 Oct 2013 10:01:56 -0700 (PDT)
Received: from 102520116.rudm1.ra.johnshopkins.edu (addr16212925014.ippl.jhmi.edu [162.129.250.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 8EFCB130003; Tue, 15 Oct 2013 10:01:55 -0700 (PDT)
Message-ID: <525D74F2.7050202@innovationslab.net>
Date: Tue, 15 Oct 2013 13:01:38 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: 6man WG <ipv6@ietf.org>, v6ops WG <v6ops@ietf.org>
Subject: Fwd: WG Review: Source Packet Routing in Networking (spring)
References: <20131015164653.2118.61260.idtracker@ietfa.amsl.com>
In-Reply-To: <20131015164653.2118.61260.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.5.2
X-Forwarded-Message-Id: <20131015164653.2118.61260.idtracker@ietfa.amsl.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="8qQ5o9WqOmwiKlskmpSnrOFEpA9sNWBkj"
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 15 Oct 2013 17:02:10 -0000

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

All,
     I know some of you will get this twice, but I want to make sure the
v6 community is fully aware of this proposed WG.  Specifically, you
should notice that they are proposing to work on source routing in IPv6.
 Please review the charter and provide your comments to the *IESG*.

Regards,
Brian


-------- Original Message --------
Subject: WG Review: Source Packet Routing in Networking (spring)
Date: Tue, 15 Oct 2013 09:46:53 -0700
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
CC: spring WG <status@ietf.org>

A new IETF working group has been proposed in the Routing Area. The IESG
has not made any determination yet. The following draft charter was
submitted, and is provided for informational purposes only. Please send
your comments to the IESG mailing list (iesg at ietf.org) by 2013-10-22.

Source Packet Routing in Networking (spring)
------------------------------------------------
Current Status: Proposed WG

Assigned Area Director:
  Stewart Bryant <stbryant@cisco.com>

Mailing list
  Address: status@ietf.org
  To Subscribe: https://www.ietf.org/mailman/listinfo/status
  Archive:
http://www.ietf.org/mail-archive/web/status/current/maillist.html

Charter:

The ability for a node to specify a forwarding path, other
than the normal shortest path, that a particular packet
will traverse, benefits a number of network functions,
for example:

o    Some types of network virtualization, including multi-
     topology networks and the partitioning of network
     resources for VPNs
o    Network path and node protection such as fast re-route
o    Network programmability
o    New OAM techniques
o    Simplification and reduction of network signalling
     components
o    Load balancing and traffic engineering

Source-based routing mechanisms have previously been
specified for network protocols, but have not seen
widespread adoption other than in MPLS traffic engineering.
These applications may require greater flexibility and
per packet source imposed routing than can be achieved
through the use of the previously defined methods.

The SPRING working group will define procedures that
will allow a node to steer a packet along an explicit
route using information attached to the packet and
without the need for per-path state information to be
held at transit nodes. Full explicit control (through loose
or strict path specification) can be achieved in a network
comprising only SPRING nodes, however SPRING must
inter-operate through loose routing in existing networks
and may find it advantageous to use loose routing for
for other network applications.

The initial data planes that will be considered are MPLS
and IPv6.

There is an assumed trust model such that any node
imposing an explicit route on a packet is assumed to
be allowed to do so, however administrative and trust
boundaries may strip explicit routes from a packet.
For each data plane technology that SPRING specifies,
a security analysis must be provided showing how protection
is provided against an attacker disrupting the network by
for example, maliciously injecting SPRING packets.
There are a number of serious security concerns with
source routing at the IP layer [RFC 5095].  As a part
of its work, the working group will define the new
IPv6-based routing header in way that blind attacks
are never possible, i.e., attackers will be unable to
send source routed packets that get successfully
processed, without being part of the negotiation for
setting up the source routes or being able to eavesdrop
legitimate source routed packets. In some networks
this base level security may be complemented with
other mechanisms, such as packet filtering,  cryptographic
security, etc.

Initial work will focus on SPRING within in a single AS,
however design decisions must not preclude operation
of SPRING across AS boundaries.

SPRING should support both centralised and distributed
path computation.

The SPRING WG should provide OAM and the
management needed to manage  SPRING enabled networks.
The SPRING protocol itself may also be used as a tool for OAM
in SPRING enabled networks.

SPRING should avoid modification to existing data
planes that would make them incompatible with
existing deployments. Where possible, existing control
and management plane protocols must be used within existing
architectures to implement the SPRING function. Any
modification of or extension to existing architectures,
data planes, or control or management plane protocols
must be carried out in the working groups responsible
for the architecture, data plane, or control or
management plane protocol being modified and in
co-ordination with this working group, but may be
done in this working group after agreement with
all the relevant WG chairs and responsible Area Directors.

The SPRING working group is chartered for the following
list of items:

o Identification and evaluation of use cases for SPRING.
   These use cases must include a definition of the
   data plane for the environment in which they are to be
   deployed.

o Definition of requirements and/or any new data plane
   encodings and procedures, required to implement
   the use cases. Such procedures must include the
   necessary security considerations.

o Definition of requirements and/or any new control plane
   mechanism needed to enable the use cases.

o Definition of requirements and/or management  plane
   mechanism needed to manage and operate a
   SPRING enabled network.

The SPRING working group will not work on any
mechanisms for use in networks that forward IPv4 packets.

[ Following to be replaced by milestones before final review]
The working group will develop the following documents:

o One or more documents describing SPRING use cases.

o Specification of a high-level abstract architecture for
   SPRING and requirements for modifications to existing
   architecture to support SPRING use cases.

o Specification of any required new procedures to support
   SPRING use cases.

o One or more data plane extension requirements documents,
   including documenting the impact on existing deployments
   of the existing data plane.

o One or more control protocol extensions requirements
   documents.

o Publish SPRING management requirements document.

o Specify the OAM mechanisms needed to support SPRING.

o Document inter-working and co-existence between the
   new procedures and the existing signalling and routing
   protocols.

o Inter-operability reports pertaining to the implementation
   of extensions supporting SPRING.


Milestones:

TBD




--8qQ5o9WqOmwiKlskmpSnrOFEpA9sNWBkj
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

iQEcBAEBCgAGBQJSXXT4AAoJEBOZRqCi7goqp6UIAKC9B8rWpuC1HMWvXCrQQv1u
jvGnAaMKzka0+iYywCtgtgNaH5Qie6zveOCMCGBwqYlAJuL+3q6gQ7/vSXOUmWTH
moC12/NaDi6duQfRlGzhbzEHipZxhFJpbzBEDojCtahuubplWpql82APctURjHgU
cXBDY4RwpqnIzR1WZXNDOqZUNlG67mSnZ6rFFebOBQkBEC5efz9SXe/j7cUdO0mW
2C0a4941xcBWAy94lQJxTMtWyiBXMGkEQUK5yvRFIqComX1EvMDUNPI1k2kPZeYM
gWffqfkAxkvMpV2f3L3SOC7PbkEAaq+8cmuvfuGjrkYPh+GNLHuIMLGPiF5S2eo=
=XkSQ
-----END PGP SIGNATURE-----

--8qQ5o9WqOmwiKlskmpSnrOFEpA9sNWBkj--

From Fred.L.Templin@boeing.com  Tue Oct 15 11:50:23 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F390921F9C05; Tue, 15 Oct 2013 11:50:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.499
X-Spam-Level: 
X-Spam-Status: No, score=-6.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lCsXckJmxtBB; Tue, 15 Oct 2013 11:50:16 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) by ietfa.amsl.com (Postfix) with ESMTP id 6074021F9E6B; Tue, 15 Oct 2013 11:50:15 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9FIoELC001350; Tue, 15 Oct 2013 11:50:14 -0700
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9FIoCPa001300 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 15 Oct 2013 11:50:14 -0700
Received: from XCH-BLV-201.nw.nos.boeing.com (10.57.37.66) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Tue, 15 Oct 2013 11:50:12 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-BLV-201.nw.nos.boeing.com ([169.254.1.140]) with mapi id 14.03.0158.001; Tue, 15 Oct 2013 11:50:12 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ray Hunter <v6ops@globis.net>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOycPBebc9KTehbEGO6mhunuAlj5n2GPgQ
Date: Tue, 15 Oct 2013 18:50:11 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812EA05@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com> <525C5CDE.3000604@globis.net> <2134F8430051B64F815C691A62D9831812E34F@XCH-BLV-504.nw.nos.boeing.com> <525D6D78.5040907@globis.net>
In-Reply-To: <525D6D78.5040907@globis.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "ietf@ietf.org" <ietf@ietf.org>, 6man Mailing List <ipv6@ietf.org>, Fernando Gont <fgont@si6networks.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 15 Oct 2013 18:50:23 -0000

Hi Ray,

> -----Original Message-----
> From: Ray Hunter [mailto:v6ops@globis.net]
> Sent: Tuesday, October 15, 2013 9:30 AM
> To: Templin, Fred L
> Cc: Ronald Bonica; Brian E Carpenter; Fernando Gont; 6man Mailing List;
> ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> > Templin, Fred L <mailto:Fred.L.Templin@boeing.com>
> > 15 October 2013 15:55
> > Hi Ray,
> >
> >> -----Original Message-----
> >> From: Ray Hunter [mailto:v6ops@globis.net]
> >> Sent: Monday, October 14, 2013 2:07 PM
> >> To: Templin, Fred L
> >> Cc: Ronald Bonica; Brian E Carpenter; Fernando Gont; 6man Mailing
> List;
> >> ietf@ietf.org
> >> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-
> 08.txt>
> >> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
> >>
> >>> Templin, Fred L <mailto:Fred.L.Templin@boeing.com>
> >>> 14 October 2013 19:39
> >>> Hi Ron,
> >>>
> >>>> -----Original Message-----
> >>>> From: Ronald Bonica [mailto:rbonica@juniper.net]
> >>>> Sent: Saturday, October 12, 2013 7:07 PM
> >>>> To: Brian E Carpenter; Templin, Fred L
> >>>> Cc: Fernando Gont; 6man Mailing List; ietf@ietf.org; Ray Hunter
> >>>> Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-
> >> 08.txt>
> >>>> (Implications of Oversized IPv6 Header Chains) to Proposed
> Standard
> >>>>
> >>>> +1
> >>>>
> >>>> Is there a way to decouple this discussion from draft-ietf-6man-
> >>>> oversized-header-chain? I would be glad to discuss it in the
> context
> >> of
> >>>> a separate draft.
> >>> I don't know if there is a way to decouple it. I believe I have
> shown
> >>> a way to not mess up tunnels while at the same time not messing up
> >> your
> >>> draft. That should be a win-win. In what way would imposing a 1K
> >> limit
> >>> on the IPv6 header chain not satisfy the general case?
> >>>
> >>> Thanks - Fred
> >>> fred.l.templin@boeing.com
> >> This draft may not go as far as you'd like (e.g. specifying a hard
> >> limit
> >> on header length as some proportion of MTU), and I'm also aware of
> the
> >> issue of MTU fragmentation and nested tunnels, but I'm still not
> clear
> >> on how this draft specifically "messes up tunnels."
> >>
> >> Can you explain what specific text in the current draft you consider
> >> harmful?
> >
> > That hosts would be permitted to send MTU-sized header chains.
>=20
> They can do that today. In fact they can legally send n* MTU-sized
> header chains, as long as the total length of an IPv6 packet is not
> exceeded.

Sure, but this draft is about setting healthy limits where there were
previously none.

> >> And why that couldn't be dealt with in a later draft (that imposes
> >> additional limits on header chains in specific scenarios)?
> >
> > Once a spec says that a host is permitted to send MTU-sized header
> > chains the die is cast and no later draft will be able to undo it.
>=20
> Why not? If this is a "maximum", there may always be scenarios where
> less than a maximum is appropriate.

This draft is intending to update RFC2460. Once updated, the
maximum header size requirements are cast in stone.

> > The host has no idea that there may be one or more tunnels in the
> > path, and so has no way of knowing to alter its behavior to be
> > kind to tunnels.
>=20
> RFC 2473 is pretty explicit about how to handle fragmentation (in the
> presence of nested IPv6 tunnels).
>=20
> Once a packet is encapsulated in a tunnel it becomes a new "original
> packet" for the next tunnel in any nested tunnel scenario.
>=20
> And PMTUD on the originating host (whether that's the original host, or
> the tunnel entry point at the previous nesting level) should receive a
> signal if the current tunnel entry node cannot handle encapsulation due
> to MTU issues (Section 7 of RFC 2473). So the originating host should
> always be informed of the MTU issue, and be able to alter its behavior
> accordingly.

We would have to go back into the long discussions on PMTUD brokenness
to show why you can't always rely on it. Hosts are *guaranteed* 1280,
but they *expect* 1500. Absent signaling from the network, that is
all they know.=20

> So again, I don't see what's new in this draft.
> > That, plus the fact that attackers will be able to craft packets
> > intended to fool middleboxes by sending a fragmented tunneled
> > packet with the "good" part of the header chain in the first
> > fragment and the "bad" part of the header chain in the second
> > fragment.
> IMHO They can do that today (and worse).

Sure. That's because there are currently no healthy limits set. This
draft is about setting healthy limits; I am saying that as long as
we are making the effort we should get it right.

Thanks - Fred
fred.l.templin@boeing.com

> > Thanks - Fred
> > fred.l.templin@boeing.com
> >
> >
> >> Thanks.
> >>
> >>
> >>>>                                                              Ron
> >>>>
> >>>>
> >>>>>> So, it wasn't necessarily the case that 1280 was a product of
> >>>>>> "thoughtful analysis" so much as the fact that **they were
> rushing
> >>>> to
> >>>>>> get a spec out the door**. So now, 16 years later, we get to put
> >> it
> >>>>>> back on the 6man charter milestone list.
> >>>>> We could have that discussion in 6man, sure, but I don't believe
> >> that
> >>>>> it's relevant to the question of whether draft-ietf-6man-
> oversized-
> >>>>> header-chain
> >>>>> is ready. This draft mitigates a known problem in terms of the
> >>>> current
> >>>>> IPv6 standards.
> >>>>>
> >> --
> >> Regards,
> >> RayH
> >


From nordmark@acm.org  Tue Oct 15 12:01:51 2013
Return-Path: <nordmark@acm.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0D6C11E8153; Tue, 15 Oct 2013 12:01:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mSdq6QymzZ3x; Tue, 15 Oct 2013 12:01:39 -0700 (PDT)
Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.50]) by ietfa.amsl.com (Postfix) with ESMTP id 149EF21F9A3D; Tue, 15 Oct 2013 12:01:34 -0700 (PDT)
Received: from a.mail.sonic.net (a.mail.sonic.net [64.142.16.245]) by d.mail.sonic.net (8.14.4/8.14.4) with ESMTP id r9FJ1RsN026517 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 15 Oct 2013 12:01:27 -0700
Received: from [172.22.215.94] ([162.210.130.3]) (authenticated bits=0) by a.mail.sonic.net (8.13.8.Beta0-Sonic/8.13.7) with ESMTP id r9FJ1Oip002189 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 15 Oct 2013 12:01:24 -0700
Message-ID: <525D9108.3000703@acm.org>
Date: Tue, 15 Oct 2013 12:01:28 -0700
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Samita Chakrabarti <samita.chakrabarti@ericsson.com>, Anders Brandt <Anders_Brandt@sigmadesigns.com>
Subject: Re: [6lo] draft-chakrabarti-nordmark-6man-efficient-nd - Proposing new use case "Set-and-forget off-line network"
References: <03F31C213F2C6941BFDDBB4336E9E6CD41B5D26C@cph-ex1> <ECA43DA70480A3498E43C3471FB2E1F01C0E0665@eusaamb103.ericsson.se>
In-Reply-To: <ECA43DA70480A3498E43C3471FB2E1F01C0E0665@eusaamb103.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Sonic-C-UUID: 3170D2A4-35CC-11E3-92FC-2EDDB31A3DED
X-Sonic-M-UUID: 31758B28-35CC-11E3-92FC-2EDDB31A3DED
Cc: "Pascal Thubert \(pthubert\)" <pthubert@cisco.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "6lo@ietf.org" <6lo@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 15 Oct 2013 19:01:52 -0000

Samita and Anders,

I guess I don't understand the correlation between the set-and-forget 
use case and address registrations in Anders' email.

Is the assertion that there can't be any additional nodes appearing in 
the network, hence there is no need to have DAD functionality after the 
initial setup?

Even if that was the case, there is typically a need for someone to send 
RAs to refresh the lifetime on the existing prefix, and some way for a 
host to discover link-layer addresses of other hosts.

Is the assumption that the nodes would take all of that (including the 
IPv6 and link-layer addresses of all the other hosts in the network) and 
save that to persistent storage?
If not, how would the nodes recover if they halt (due to a line power 
failure or running out of battery) and reboot?


For the home automation stuff I've seen a key benefit is to have a 
controller, which allows the user to reprogram the lights and sensors. 
That can be either a dedicated controller or a gateway plus a remote 
app/controller.

In those cases the dedicated controller or gateway would be a natural 
place to perform all the functions relation to address registrations and 
prefixes.

So I don't quite understand where this use case would appear in practice 
- a set of sensors and lights whose functional behavior is frozen in 
time doesn't match what I see in the home automation space.

Regards,
    Erik

On 10/14/13 7:31 PM, Samita Chakrabarti wrote:
> Hi Anders,
>
> Thanks for your detail comments -- those are quite useful!
>
> Please see in-line.
>
> -----Original Message-----
> From: Anders Brandt [mailto:Anders_Brandt@sigmadesigns.com]
> Sent: Monday, September 02, 2013 2:44 AM
> To: ipv6@ietf.org; Pascal Thubert (pthubert); Samita Chakrabarti; Erik Nordmark (nordmark); mrw@lilacglade.org
> Subject: draft-chakrabarti-nordmark-6man-efficient-nd - Proposing new use case "Set-and-forget off-line network"
>
> [cross-posting 6man / 6lo]
>
> Samita Chakrabarti et al,
>
> Great draft which addresses important issues for low-power wireless network technologies.
>
> After reading the draft, it seems to me that you would benefit adding one more use case - and addressing the derived requirement(s).
>
> Proposed use case:
> -------
> A.7.  Set-and-forget off-line networks
>      Home control modules designed for networked environments may be deployed
>      in very simple settings like garden path lighting controlled by wireless
>      light and motion sensors. Once the network has been created and sensors
>      have been associated with the light modules, the installer takes away the
>      configuration tool which was used to set up the network. Most likely a ULA
>      prefix is used, since multiple hops may be needed. None of the sensors and
>      light modules has the capability of handing out fresh prefixes. Thus, for
>      a set-and-forget style off-line network to work, the nodes must be  able to
>      operate forever without trying to refresh its address registration.
>
>      In another instance of an off-line network, a key-fob style remote control is paired
>      to a few lamp modules. The controller creates its own small off-line network.
>      The controller is not only battery powered and sleeping. It is far away in its owner's pocket.
>      Address registration is not possible.
>
>       The manufacturer of the lamp module wants to sell exactly the same lamp
>       module to large network deployments where address registration is used.
>       Since this class of devices provide no local configuration interface, the behaviour needs
>       to be controlled via some sort of auto-configuration.
> -------
> (end of proposed use case)
>
> [SC>]  ===> Added.
>
> One solution could be to introduce a special interpretation of registration lifetime 0xFFFF as infinite and stating that default routers SHOULD NOT advertise this value.
>
> Such an approach would resemble existing text in RFC4861:
>
>   Valid Lifetime
>                        32-bit unsigned integer.  The length of time in
>                        seconds (relative to the time the packet is sent)
>                        that the prefix is valid for the purpose of on-link
>                        determination.  A value of all one bits
>                        (0xffffffff) represents infinity.  The Valid
>                        Lifetime is also used by [ADDRCONF].
>
>
> The authors may have other preferred solutions?
> [SC>] ===> As discussed off-line that , the valid lifetime for the prefix is still valid and the ARO lifetime applies to the registration lifetime.  We have discussed some of the issues with  allowing permanent registration (especially with NCE cache entries). So at this point we have agreed  to keep the ARO lifetime range as it is.
>
> Best regards,
> -Samita
>
>
>
> _______________________________________________
> 6lo mailing list
> 6lo@ietf.org
> https://www.ietf.org/mailman/listinfo/6lo
>


From samita.chakrabarti@ericsson.com  Tue Oct 15 12:36:11 2013
Return-Path: <samita.chakrabarti@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 928F011E8156; Tue, 15 Oct 2013 12:36:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.569
X-Spam-Level: 
X-Spam-Status: No, score=-2.569 tagged_above=-999 required=5 tests=[AWL=0.030,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7vut9zTjekMw; Tue, 15 Oct 2013 12:36:06 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id B087711E8163; Tue, 15 Oct 2013 12:36:03 -0700 (PDT)
X-AuditID: c618062d-b7fda8e0000024c6-76-525d9922adf1
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 36.83.09414.2299D525; Tue, 15 Oct 2013 21:36:03 +0200 (CEST)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.02.0328.009; Tue, 15 Oct 2013 15:36:02 -0400
From: Samita Chakrabarti <samita.chakrabarti@ericsson.com>
To: Erik Nordmark <nordmark@acm.org>, Anders Brandt <Anders_Brandt@sigmadesigns.com>
Subject: RE: [6lo] draft-chakrabarti-nordmark-6man-efficient-nd - Proposing new use case "Set-and-forget off-line network"
Thread-Topic: [6lo] draft-chakrabarti-nordmark-6man-efficient-nd - Proposing new use case "Set-and-forget off-line network"
Thread-Index: AQHOydj8fqsX2B7ndU6TyqGuojA9hJn2IxdA
Date: Tue, 15 Oct 2013 19:36:01 +0000
Message-ID: <ECA43DA70480A3498E43C3471FB2E1F01C0E0B9C@eusaamb103.ericsson.se>
References: <03F31C213F2C6941BFDDBB4336E9E6CD41B5D26C@cph-ex1> <ECA43DA70480A3498E43C3471FB2E1F01C0E0665@eusaamb103.ericsson.se> <525D9108.3000703@acm.org>
In-Reply-To: <525D9108.3000703@acm.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.135]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPLMWRmVeSWpSXmKPExsUyuXRPgq7yzNggg887+C2apwhYHH12gtHi 5dn3TBYLli9lseifupPJYsaUd4wObB6Xr3h7TPm9kdVjyZKfTB4bt69j8dj74g5zAGsUl01K ak5mWWqRvl0CV8br3VPZCx4ZVRw8/ZC1gXGXehcjJ4eEgInErUc/GCFsMYkL99azdTFycQgJ HGWUONh0hRHCWc4o8eHVHXaQKjYBK4mO3j1gtohAmMSNxmZ2kCJmgcWMEi27jrOBJIQFaiS2 bF/IBlFUK9H7fyPQJA4g20ii9WsFSJhFQFXi16IPzCBhXgFfiXOzfCB2zWeUWP53JitIDaeA usTB/83MIDYj0HXfT61hArGZBcQlbj2ZzwRxtYDEkj3nmSFsUYmXj/+xQtjKEt/nPGKBqNeR WLD7ExuErS2xbOFrsHpeAUGJkzOfsExgFJuFZOwsJC2zkLTMQtKygJFlFSNHaXFqWW66kcEm RmCkHZNg093BuOel5SFGaQ4WJXHeL2+dg4QE0hNLUrNTUwtSi+KLSnNSiw8xMnFwSjUw9l5k imrOcXxcF3t6W1DcLN+gJ5UWppp9dXkpWltjIjcLpJvtdMrY7r6n0NM3W8s/5kzAbh7OtNNX fq7MD9Q7FPKePXjHx6hwIZWVAlz5uw4qSr4S/1byQ12iYekX43JtuXxeLd2NHXwm/ubt1Y1X GmS/JFSw/jPp3zltsbCKz7cN/tYNk5RYijMSDbWYi4oTASFu6YiCAgAA
Cc: "Pascal Thubert \(pthubert\)" <pthubert@cisco.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "6lo@ietf.org" <6lo@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 15 Oct 2013 19:36:11 -0000

Hi Erik,

As far as I understand that the controller in Z-wave is not the same behavi=
or as in NEAR router.
The controller is quite specific to the application -- it seems it once con=
figures the network devices and forgets about the device and it is used for=
 one-time configuration. This seems quite product specific function.

I agree that having a controller function based on ND is quite useful where=
 the controller would be responsible for assigning addresses and managing t=
hem through registration and the controller may or may not have the routing=
 capabilities.

I am not quite clear why the controller in Ander's example would need the r=
egistration  for one time.
The use case was added in the appendix since the application partially uses=
 the efficient-ND mechanisms.

Anders can explain the reasons behind  the particular function and relation=
ship with registration.

Thanks for bringing it up.
-Samita

-----Original Message-----
From: Erik Nordmark [mailto:nordmark@acm.org]=20
Sent: Tuesday, October 15, 2013 12:01 PM
To: Samita Chakrabarti; Anders Brandt
Cc: ipv6@ietf.org; Pascal Thubert (pthubert); mrw@lilacglade.org; 6lo@ietf.=
org
Subject: Re: [6lo] draft-chakrabarti-nordmark-6man-efficient-nd - Proposing=
 new use case "Set-and-forget off-line network"


Samita and Anders,

I guess I don't understand the correlation between the set-and-forget use c=
ase and address registrations in Anders' email.

Is the assertion that there can't be any additional nodes appearing in the =
network, hence there is no need to have DAD functionality after the initial=
 setup?

Even if that was the case, there is typically a need for someone to send RA=
s to refresh the lifetime on the existing prefix, and some way for a host t=
o discover link-layer addresses of other hosts.

Is the assumption that the nodes would take all of that (including the
IPv6 and link-layer addresses of all the other hosts in the network) and sa=
ve that to persistent storage?
If not, how would the nodes recover if they halt (due to a line power failu=
re or running out of battery) and reboot?


For the home automation stuff I've seen a key benefit is to have a controll=
er, which allows the user to reprogram the lights and sensors.=20
That can be either a dedicated controller or a gateway plus a remote app/co=
ntroller.

In those cases the dedicated controller or gateway would be a natural place=
 to perform all the functions relation to address registrations and prefixe=
s.

So I don't quite understand where this use case would appear in practice
- a set of sensors and lights whose functional behavior is frozen in time d=
oesn't match what I see in the home automation space.

Regards,
    Erik

On 10/14/13 7:31 PM, Samita Chakrabarti wrote:
> Hi Anders,
>
> Thanks for your detail comments -- those are quite useful!
>
> Please see in-line.
>
> -----Original Message-----
> From: Anders Brandt [mailto:Anders_Brandt@sigmadesigns.com]
> Sent: Monday, September 02, 2013 2:44 AM
> To: ipv6@ietf.org; Pascal Thubert (pthubert); Samita Chakrabarti; Erik=20
> Nordmark (nordmark); mrw@lilacglade.org
> Subject: draft-chakrabarti-nordmark-6man-efficient-nd - Proposing new use=
 case "Set-and-forget off-line network"
>
> [cross-posting 6man / 6lo]
>
> Samita Chakrabarti et al,
>
> Great draft which addresses important issues for low-power wireless netwo=
rk technologies.
>
> After reading the draft, it seems to me that you would benefit adding one=
 more use case - and addressing the derived requirement(s).
>
> Proposed use case:
> -------
> A.7.  Set-and-forget off-line networks
>      Home control modules designed for networked environments may be depl=
oyed
>      in very simple settings like garden path lighting controlled by wire=
less
>      light and motion sensors. Once the network has been created and sens=
ors
>      have been associated with the light modules, the installer takes awa=
y the
>      configuration tool which was used to set up the network. Most likely=
 a ULA
>      prefix is used, since multiple hops may be needed. None of the senso=
rs and
>      light modules has the capability of handing out fresh prefixes. Thus=
, for
>      a set-and-forget style off-line network to work, the nodes must be  =
able to
>      operate forever without trying to refresh its address registration.
>
>      In another instance of an off-line network, a key-fob style remote c=
ontrol is paired
>      to a few lamp modules. The controller creates its own small off-line=
 network.
>      The controller is not only battery powered and sleeping. It is far a=
way in its owner's pocket.
>      Address registration is not possible.
>
>       The manufacturer of the lamp module wants to sell exactly the same =
lamp
>       module to large network deployments where address registration is u=
sed.
>       Since this class of devices provide no local configuration interfac=
e, the behaviour needs
>       to be controlled via some sort of auto-configuration.
> -------
> (end of proposed use case)
>
> [SC>]  =3D=3D=3D> Added.
>
> One solution could be to introduce a special interpretation of registrati=
on lifetime 0xFFFF as infinite and stating that default routers SHOULD NOT =
advertise this value.
>
> Such an approach would resemble existing text in RFC4861:
>
>   Valid Lifetime
>                        32-bit unsigned integer.  The length of time in
>                        seconds (relative to the time the packet is sent)
>                        that the prefix is valid for the purpose of on-lin=
k
>                        determination.  A value of all one bits
>                        (0xffffffff) represents infinity.  The Valid
>                        Lifetime is also used by [ADDRCONF].
>
>
> The authors may have other preferred solutions?
> [SC>] =3D=3D=3D> As discussed off-line that , the valid lifetime for the =
prefix is still valid and the ARO lifetime applies to the registration life=
time.  We have discussed some of the issues with  allowing permanent regist=
ration (especially with NCE cache entries). So at this point we have agreed=
  to keep the ARO lifetime range as it is.
>
> Best regards,
> -Samita
>
>
>
> _______________________________________________
> 6lo mailing list
> 6lo@ietf.org
> https://www.ietf.org/mailman/listinfo/6lo
>


From fgont@si6networks.com  Tue Oct 15 17:09:24 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 574F511E823A; Tue, 15 Oct 2013 17:09:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id awKjWJ4qmE2x; Tue, 15 Oct 2013 17:09:23 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 98A4111E8228; Tue, 15 Oct 2013 17:09:15 -0700 (PDT)
Received: from [186.134.32.156] (helo=[192.168.123.126]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1VWEfj-0002vv-FG; Wed, 16 Oct 2013 02:09:07 +0200
Message-ID: <525DCF12.9020804@si6networks.com>
Date: Tue, 15 Oct 2013 20:26:10 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>,  Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com>	<9300F272-E282-41C3-9DA8-59134B975FC7@employees.org>	<9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com>	<2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com>	<D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org>	<2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com>	<E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org>	<2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com>	<5255D6EE.4050300@gmail.com>	<2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <2134F8430051B64F815C691A62D9831812D718@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831812D718@XCH-BLV-504.nw.nos.boeing.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Ray Hunter <v6ops@globis.net>, 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 16 Oct 2013 00:09:24 -0000

On 10/14/2013 02:38 PM, Templin, Fred L wrote:
>>
>> We could have that discussion in 6man, sure, but I don't believe that
>> it's
>> relevant to the question of whether draft-ietf-6man-oversized-header-
>> chain
>> is ready.
> 
> If it messes up tunnels, then it's not ready.

FWIW I disagree with this statement. From this perspectie, you'd also
expect middleboxes (e.g. load-balancers) to get deep into any layers of
tunnelling to decide on which link packets should be forwarded. -- and
this is clearly unrealistic (if at all desirable).

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





From fgont@si6networks.com  Tue Oct 15 17:09:25 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0C7111E8228; Tue, 15 Oct 2013 17:09:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SGmMW+bAz0jG; Tue, 15 Oct 2013 17:09:24 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 8CE6111E8235; Tue, 15 Oct 2013 17:09:17 -0700 (PDT)
Received: from [186.134.32.156] (helo=[192.168.123.126]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1VWEfp-0002vz-HJ; Wed, 16 Oct 2013 02:09:13 +0200
Message-ID: <525DD007.8030100@si6networks.com>
Date: Tue, 15 Oct 2013 20:30:15 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>,  Ronald Bonica <rbonica@juniper.net>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com>	<2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com>	<D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org>	<2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com>	<E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org>	<2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com>	<5255D6EE.4050300@gmail.com>	<2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com>	<5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com>	<2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com>	<52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com>	<2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Ray Hunter <v6ops@globis.net>, 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 16 Oct 2013 00:09:25 -0000

On 10/14/2013 02:39 PM, Templin, Fred L wrote:
>
>> Is there a way to decouple this discussion from draft-ietf-6man-
>> oversized-header-chain? I would be glad to discuss it in the context of
>> a separate draft.
> 
> I don't know if there is a way to decouple it. I believe I have shown
> a way to not mess up tunnels while at the same time not messing up your
> draft. That should be a win-win. In what way would imposing a 1K limit
> on the IPv6 header chain not satisfy the general case?

6man had consensus multiple times on *not* to impose this sort of limits
in this document (that's why the original limit of 1280 bytes was
removed from earlier versions of this I-D in the first place).

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





From nalini.elkins@insidethestack.com  Tue Oct 15 17:10:51 2013
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC75521F9B0D for <ipv6@ietfa.amsl.com>; Tue, 15 Oct 2013 17:10:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.273
X-Spam-Level: 
X-Spam-Status: No, score=-2.273 tagged_above=-999 required=5 tests=[AWL=0.325,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PCgP-13XqY9X for <ipv6@ietfa.amsl.com>; Tue, 15 Oct 2013 17:10:50 -0700 (PDT)
Received: from nm10-vm4.access.bullet.mail.bf1.yahoo.com (nm10-vm4.access.bullet.mail.bf1.yahoo.com [216.109.114.211]) by ietfa.amsl.com (Postfix) with ESMTP id 9A05D21F9D18 for <ipv6@ietf.org>; Tue, 15 Oct 2013 17:10:33 -0700 (PDT)
Received: from [66.196.81.157] by nm10.access.bullet.mail.bf1.yahoo.com with NNFMP; 16 Oct 2013 00:10:32 -0000
Received: from [66.196.81.138] by tm3.access.bullet.mail.bf1.yahoo.com with NNFMP; 16 Oct 2013 00:10:32 -0000
Received: from [127.0.0.1] by omp1014.access.mail.bf1.yahoo.com with NNFMP; 16 Oct 2013 00:10:32 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 431601.27729.bm@omp1014.access.mail.bf1.yahoo.com
Received: (qmail 36317 invoked by uid 60001); 16 Oct 2013 00:03:51 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1381881831; bh=fWEKUkOZgD4Zal9Y72DMSPCZN1A7gGDD7lfajVd7uXk=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=3Ef3yP9O5Gz/8k4nbvSgtBgkuArZntlKDruFbXbJ/VIIq1qlYbfxIGIF1mq3FLHp2aR+ECbT5MB3KMd/dJh2KUCX5GXQLmVep7lpVvyzgWwo616kho3JMBUqJFyhqsH9uhGad+FgcT/BlSlq/i5TWxyfJw+7VNSO2pwDa2QWPOk=
X-YMail-OSG: jb6qHngVM1nl969yNLWv5KtQkQjGxcJ5ejs9_QcjmP3A0Xt lhGD51BCVMGejBqLHQyyU2eRIuYtV6imrlwMQ9QlmSAcSa3wCK18B00oEAN_ kKfLEXkTsHP28ax1XDO0594jGj_tLocy1eraLz3nogtuKx1cB9VaTymNTaJY 81BFEO7_1U8kTsqDrKWOL6Z46lf92NrOnnHoC7GzXa1Pv3AFxvCIFvNuRz_d QxqAHzXxZesfSAvgKVQTBW4Cl3XgDk2S6ynvf8DhZ2fHWouj0D2IwFZEB6cj uGukI7wceCC3mMwew1hHT8eVM61nMo8buPpvkYVizeFv.v.F55pQfmiR3orN P5HXL_YSfqYM_4_vrfm0TJpyVXHK7RHdKowFmhuq3uYwAEmHIn_7PRlyC9GY BTWjptrJu1VBnYEnfbucr2ZQPfIJMeTO8MrG6U3kgHuGvDR.D82tCNHTXbSL rim0gQA.mGHMIWociBFaY8BJ4J1io0Su8D3xC0edvrTjQ86c1ogXOm1EIYou 5qs2jjC3pPOZ362lw6YJ_qtUDz7kBWxlEMoKEBOweSX1hqe0I4WKYDhrTC2p x6K8Nu4h66CbUOirVtl.3BMP5Z_NKfrcvmAHdTO8V42t8N5O2JGCCJoPHRzt pzBP1V5WqPXeLgqkpZo6ud8npDgqb6e_.kjDt0iw-
Received: from [24.130.37.147] by web2801.biz.mail.ne1.yahoo.com via HTTP; Tue, 15 Oct 2013 17:03:51 PDT
X-Rocket-MIMEInfo: 002.001, QWxsLAoKSSBoYXZlIHVwZGF0ZWQgdGhlIFBETSBzcGVjaWZpY2F0aW9uIHRvIGFkZCBhIHNlY29uZCBQRE0gdHlwZSB3aGljaCByZXF1aXJlcyBOTyB0aW1lIHN5bmNocm9uaXphdGlvbi4gwqAgVGhlIGRyYWZ0IGZvciBJUFBNIHdoaWNoIGRlc2NyaWJlcyBob3cgdG8gY2FsY3VsYXRlIGFuZCB1c2UgdGhlIHZhbHVlcyBkZXNjcmliZWQgaW4gdGhlIFBETS4gwqAgVGhlIElQUE0gZHJhZnQgaXM6CgpodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1lbGtpbnMtaXBwbS1wZG0tbWV0cmljcy0wMQoKCkkBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.160.587
References: <20131015235832.2100.62094.idtracker@ietfa.amsl.com>
Message-ID: <1381881831.35197.YahooMailNeo@web2801.biz.mail.ne1.yahoo.com>
Date: Tue, 15 Oct 2013 17:03:51 -0700 (PDT)
From: Nalini Elkins <nalini.elkins@insidethestack.com>
Subject: Fw: New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-03.txt
To: v6ops WG <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>
In-Reply-To: <20131015235832.2100.62094.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="36908767-168568284-1381881831=:35197"
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Nalini Elkins <nalini.elkins@insidethestack.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: Wed, 16 Oct 2013 00:10:51 -0000

--36908767-168568284-1381881831=:35197
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

All,=0A=0AI have updated the PDM specification to add a second PDM type whi=
ch requires NO time synchronization. =A0 The draft for IPPM which describes=
 how to calculate and use the values described in the PDM. =A0 The IPPM dra=
ft is:=0A=0Ahttp://tools.ietf.org/html/draft-elkins-ippm-pdm-metrics-01=0A=
=0A=0AI would appreciate any comments or feedback.=A0=0A=0A=0AA new version=
 of I-D, draft-elkins-6man-ipv6-pdm-dest-option-03.txt=0Ahas been successfu=
lly submitted by Nalini Elkins and posted to the=0AIETF repository.=0A=0AFi=
lename:=A0=A0=A0  draft-elkins-6man-ipv6-pdm-dest-option=0ARevision:=A0=A0=
=A0  03=0ATitle:=A0=A0=A0 =A0=A0=A0  IPv6 Performance and Diagnostic Metric=
s Destination Option=0ACreation date:=A0=A0=A0  2013-10-15=0AGroup:=A0=A0=
=A0 =A0=A0=A0  Individual Submission=0ANumber of pages: 18=0AURL:=A0 =A0 =
=A0 =A0 =A0 =A0  http://www.ietf.org/internet-drafts/draft-elkins-6man-ipv6=
-pdm-dest-option-03.txt=0AStatus:=A0 =A0 =A0 =A0 =A0 http://datatracker.iet=
f.org/doc/draft-elkins-6man-ipv6-pdm-dest-option=0AHtmlized:=A0 =A0 =A0 =A0=
 http://tools.ietf.org/html/draft-elkins-6man-ipv6-pdm-dest-option-03=0ADif=
f:=A0 =A0 =A0 =A0 =A0 =A0 http://www.ietf.org/rfcdiff?url2=3Ddraft-elkins-6=
man-ipv6-pdm-dest-option-03=0A=0AAbstract:=0A=A0  To diagnose performance a=
nd connectivity problems, metrics on real=0A=A0  (non-synthetic) transmissi=
on are critical for timely end-to-end=0A=A0  problem resolution. Such diagn=
ostics may be real-time or after the=0A=A0  fact, but must not impact an op=
erational production network. The base=0A=A0  metrics are: packet sequence =
number and packet timestamp.=A0 Metrics=0A=A0  derived from these will be d=
escribed separately. This document solves=0A=A0  these problems with a new =
destination option, the Performance and=0A=A0  Diagnostic Metrics destinati=
on option (PDM).=0A=0A=0A=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =0A=0A=0APlease note that it may t=
ake a couple of minutes from the time of submission=0Auntil the htmlized ve=
rsion and diff are available at tools.ietf.org.=0A=0AThe IETF Secretariat
--36908767-168568284-1381881831=:35197
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:ar=
ial, helvetica, sans-serif;font-size:12pt"><div><span>All,</span></div><div=
 style=3D"color: rgb(0, 0, 0); font-size: 16px; font-family: arial, helveti=
ca, sans-serif; background-color: transparent; font-style: normal;"><span><=
br></span></div><div style=3D"color: rgb(0, 0, 0); font-size: 16px; font-fa=
mily: arial, helvetica, sans-serif; background-color: transparent; font-sty=
le: normal;"><span>I have updated the PDM specification to add a second PDM=
 type which requires NO time synchronization. &nbsp; The draft for IPPM whi=
ch describes how to calculate and use the values described in the PDM. &nbs=
p; The IPPM draft is:</span></div><div style=3D"color: rgb(0, 0, 0); font-s=
ize: 16px; font-family: arial, helvetica, sans-serif; background-color: tra=
nsparent; font-style: normal;"><span><br></span></div><div style=3D"color: =
rgb(0, 0, 0); font-size: 16px; font-family: arial, helvetica, sans-serif;
 background-color: transparent; font-style: normal;"><span><a href=3D"http:=
//tools.ietf.org/html/draft-elkins-ippm-pdm-metrics-01">http://tools.ietf.o=
rg/html/draft-elkins-ippm-pdm-metrics-01</a><br></span></div><div style=3D"=
color: rgb(0, 0, 0); font-size: 16px; font-family: arial, helvetica, sans-s=
erif; background-color: transparent; font-style: normal;"><br></div><div st=
yle=3D"color: rgb(0, 0, 0); font-size: 16px; font-family: arial, helvetica,=
 sans-serif; background-color: transparent; font-style: normal;">I would ap=
preciate any comments or feedback.<span style=3D"font-size: 12pt;">&nbsp;</=
span></div><div style=3D"font-family: arial, helvetica, sans-serif; font-si=
ze: 12pt;"><div style=3D"font-family: 'times new roman', 'new york', times,=
 serif; font-size: 12pt;"><div dir=3D"ltr"> </div> <div class=3D"y_msg_cont=
ainer"><br>=0A<br>A new version of I-D, draft-elkins-6man-ipv6-pdm-dest-opt=
ion-03.txt<br>has been successfully submitted by Nalini Elkins and posted t=
o the<br>IETF repository.<br><br>Filename:&nbsp;&nbsp;&nbsp;  draft-elkins-=
6man-ipv6-pdm-dest-option<br>Revision:&nbsp;&nbsp;&nbsp;  03<br>Title:&nbsp=
;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;  IPv6 Performance and Diagnostic Metrics D=
estination Option<br>Creation date:&nbsp;&nbsp;&nbsp;  2013-10-15<br>Group:=
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;  Individual Submission<br>Number of p=
ages: 18<br>URL:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  http://www.ietf.=
org/internet-drafts/draft-elkins-6man-ipv6-pdm-dest-option-03.txt<br>Status=
:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; http://datatracker.ietf.org/doc/draft-e=
lkins-6man-ipv6-pdm-dest-option<br>Htmlized:&nbsp; &nbsp; &nbsp; &nbsp; htt=
p://tools.ietf.org/html/draft-elkins-6man-ipv6-pdm-dest-option-03<br>Diff:&=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
 http://www.ietf.org/rfcdiff?url2=3Ddraft-elkins-6man-ipv6-pdm-dest-option-=
03<br><br>Abstract:<br>&nbsp;  To diagnose performance and connectivity pro=
blems, metrics on real<br>&nbsp;  (non-synthetic) transmission are critical=
 for timely end-to-end<br>&nbsp;  problem resolution. Such diagnostics may =
be real-time or after the<br>&nbsp;  fact, but must not impact an operation=
al production network. The base<br>&nbsp;  metrics are: packet sequence num=
ber and packet timestamp.&nbsp; Metrics<br>&nbsp;  derived from these will =
be described separately. This document solves<br>&nbsp;  these problems wit=
h a new destination option, the Performance and<br>&nbsp;  Diagnostic Metri=
cs destination option (PDM).<br><br><br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br><br><br>Please note that it may tak=
e a couple of minutes from the time of submission<br>until the htmlized ver=
sion and diff are available at <a target=3D"_blank" href=3D"http://tools.ie=
tf.org/">tools.ietf.org</a>.<br><br>The IETF Secretariat<br><br><br><br></d=
iv> </div> </div>  </div></body></html>
--36908767-168568284-1381881831=:35197--

From iesg-secretary@ietf.org  Wed Oct 16 00:11:01 2013
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0336A21F9CA9; Wed, 16 Oct 2013 00:10:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.436
X-Spam-Level: 
X-Spam-Status: No, score=-102.436 tagged_above=-999 required=5 tests=[AWL=0.164, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ohxb34y5+-+0; Wed, 16 Oct 2013 00:10:45 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 84BF521F9D18; Wed, 16 Oct 2013 00:10:34 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: DraftTracker Mail System <iesg-secretary@ietf.org>
To: iesg@ietf.org, 6man-chairs@tools.ietf.org, draft-ietf-6man-oversized-header-chain@tools.ietf.org, ipv6@ietf.org
Subject: Last Call Expired: <draft-ietf-6man-oversized-header-chain-08.txt>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131016071034.28967.10141.idtracker@ietfa.amsl.com>
Date: Wed, 16 Oct 2013 00:10:34 -0700
Cc: iesg-secretary@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 16 Oct 2013 07:11:01 -0000

Please DO NOT reply to this email.

I-D: <draft-ietf-6man-oversized-header-chain-08.txt>
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-6man-oversized-h=
eader-chain/

IETF Last Call has ended, and the state has been changed to
Waiting for Writeup.


From v6ops@globis.net  Wed Oct 16 06:15:10 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAC7F11E82A7; Wed, 16 Oct 2013 06:15:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h3cjMEz5564x; Wed, 16 Oct 2013 06:15:10 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id B3F7B11E82AB; Wed, 16 Oct 2013 06:15:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id DF19687007F; Wed, 16 Oct 2013 15:15:00 +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 4-eHjwW1gte4; Wed, 16 Oct 2013 15:15:00 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 915A9870073; Wed, 16 Oct 2013 15:15:00 +0200 (CEST)
Message-ID: <525E9152.60209@globis.net>
Date: Wed, 16 Oct 2013 15:14:58 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Nalini Elkins <nalini.elkins@insidethestack.com>
Subject: Re: Fw: New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-03.txt
References: <20131015235832.2100.62094.idtracker@ietfa.amsl.com> <1381881831.35197.YahooMailNeo@web2801.biz.mail.ne1.yahoo.com>
In-Reply-To: <1381881831.35197.YahooMailNeo@web2801.biz.mail.ne1.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: v6ops WG <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 16 Oct 2013 13:15:11 -0000

Nalini Elkins wrote:
> All,
>
> I have updated the PDM specification to add a second PDM type which requires NO time synchronization.   The draft for IPPM which describes how to calculate and use the values described in the PDM.   The IPPM draft is:
>
> http://tools.ietf.org/html/draft-elkins-ippm-pdm-metrics-01
>
>
> I would appreciate any comments or feedback. 
>
>
> A new version of I-D, draft-elkins-6man-ipv6-pdm-dest-option-03.txt
> has been successfully submitted by Nalini Elkins and posted to the
> IETF repository.
>
> Filename:     draft-elkins-6man-ipv6-pdm-dest-option
> Revision:     03
> Title:         IPv6 Performance and Diagnostic Metrics Destination Option
> Creation date:     2013-10-15
> Group:         Individual Submission
> Number of pages: 18
> URL:             http://www.ietf.org/internet-drafts/draft-elkins-6man-ipv6-pdm-dest-option-03.txt
> Status:          http://datatracker.ietf.org/doc/draft-elkins-6man-ipv6-pdm-dest-option
> Htmlized:        http://tools.ietf.org/html/draft-elkins-6man-ipv6-pdm-dest-option-03
> Diff:            http://www.ietf.org/rfcdiff?url2=draft-elkins-6man-ipv6-pdm-dest-option-03
>
> Abstract:
>    To diagnose performance and connectivity problems, metrics on real
>    (non-synthetic) transmission are critical for timely end-to-end
>    problem resolution. Such diagnostics may be real-time or after the
>    fact, but must not impact an operational production network. The base
>    metrics are: packet sequence number and packet timestamp.  Metrics
>    derived from these will be described separately. This document solves
>    these problems with a new destination option, the Performance and
>    Diagnostic Metrics destination option (PDM).
>
>
>                                                                                   
>
>
> 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

I have read this draft.

All in all it seems rather simplistic, and I can't help thinking that
there's much more to this than is expressed in the draft.

For example, the server time calculation seems to assume that a response
packet has to be sent immediately by every application as soon as data
has been processed: every response requires a response.

What additional processing is required to cater for cases where the
sender and the receiver simply have nothing to say to each other at that
point in time?

e.g. a simple poll response protocol that is triggered every minute
would seem to suggest that there's a minimum of a sixty second server
processing time in the poller, when in fact it's just not doing anything
at all for this process.

Likewise, the calculations for round trip time do not seem to take into
account any packet drops or duplicates, which would seem to suggest to
me that the protocol as described would report packet drops as
additional latency, rather than any sort of protocol recovery/
retransmission timers being triggered.

Wouldn't the PDM sequence numbers have to be linked to TCP sequence
numbers when calculating stats? And for UDP you'd have no indication (or
have to use some app specific sequence number or hash to detect forward
progression of the flow)?

-- 
Regards,
RayH


From nalini.elkins@insidethestack.com  Wed Oct 16 06:41:22 2013
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 476EB11E82A8 for <ipv6@ietfa.amsl.com>; Wed, 16 Oct 2013 06:41:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.339
X-Spam-Level: 
X-Spam-Status: No, score=-2.339 tagged_above=-999 required=5 tests=[AWL=0.260,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0yjukIZ7lRIC for <ipv6@ietfa.amsl.com>; Wed, 16 Oct 2013 06:41:13 -0700 (PDT)
Received: from nm20-vm8.access.bullet.mail.gq1.yahoo.com (nm20-vm8.access.bullet.mail.gq1.yahoo.com [216.39.63.228]) by ietfa.amsl.com (Postfix) with ESMTP id 08A2A11E81DF for <ipv6@ietf.org>; Wed, 16 Oct 2013 06:41:09 -0700 (PDT)
Received: from [216.39.60.165] by nm20.access.bullet.mail.gq1.yahoo.com with NNFMP; 16 Oct 2013 13:41:09 -0000
Received: from [216.39.60.163] by tm1.access.bullet.mail.gq1.yahoo.com with NNFMP; 16 Oct 2013 13:41:09 -0000
Received: from [127.0.0.1] by omp1029.access.mail.gq1.yahoo.com with NNFMP; 16 Oct 2013 13:41:09 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 487850.78158.bm@omp1029.access.mail.gq1.yahoo.com
Received: (qmail 81911 invoked by uid 60001); 16 Oct 2013 13:41:08 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1381930868; bh=PXTBaoBK2gyima4oe58XWR+6cc4gjXMt/q5XMgvfHWs=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=Y8wXcmn5ZATyCGplafZEXFiPGCxQHyU5RSh5zRMZho0PkTCinAbUgTBm81VmruPaZpcKhMa+qCwcAcSF68el9XAo6DQLHLwwmeDxL8ZLFzZgRL91QVyFUQTG9ityzMhHVITCDpRWp5kL985qakkFZZe5bHacY2TIB3YeQYQ/ypQ=
X-YMail-OSG: yPUi0tUVM1nlfy5zZ0Nqz5jVRtwJgJtxrCo7gdr_VOL5hq1 uiuJpgWHYYDs9AVZkxCZN0anvtPYDvG_mS_bMckAVgAuWOWZ3at5Jw5T8_Ll JpM8u8Mw7zXBm_WjFCkEfmkEIZOqRMTEoFtFpvuMxdMqEvhpORuZT27QRng2 rjCpiEAFa7tqZ.YdqvORIBmiVW.zsIiCW1I3MBNP2UcAU1UqtW4hBeCJz2rl mcyskhosTxLvuExgrl_GR4uvz4kAMIh5MntAGtAqQVdg.t4r0NDqnnbAI6f. OpoUgmpwnRFFH67UM.KiQW23eiwrC0LfmcfCVmVllYFGH22fXpzlBc97yrMj khH0TpRtLkah_STBDH5sRDy_ZizHvRZTvqwlz6aIFnp_pQv2zVWKxqzSLWna KCDLAVOmqbv7QV0BOmVbxfs3iEDNWr1h_3kkMr08nrFDOX0Cg8EVe.p4muHU 86p3pkOvhhVQxbyPs6cavM0Q_u.19_9qrJRquyta3EhIrg7MuHAoYKyUSVWO VQX7MsUuIPbuDaCI6.FHtbreCs1WZKUyybA5tC3fYEX8zEgwLtUcbMCngId0 f98uO3uTofRiqelam__tVz0U4kkBzwpJCIjF.4A--
Received: from [24.130.37.147] by web2803.biz.mail.ne1.yahoo.com via HTTP; Wed, 16 Oct 2013 06:41:08 PDT
X-Rocket-MIMEInfo: 002.001, PiBJIGhhdmUgcmVhZCB0aGlzIGRyYWZ0LgoKPkFsbCBpbiBhbGwgaXQgc2VlbXMgcmF0aGVyIHNpbXBsaXN0aWMsIGFuZCBJIGNhbid0IGhlbHAgdGhpbmtpbmcgdGhhdAo.dGhlcmUncyBtdWNoIG1vcmUgdG8gdGhpcyB0aGFuIGlzIGV4cHJlc3NlZCBpbiB0aGUgZHJhZnQuCgpZZXMuIMKgVGhlcmUgaXMuIMKgU2VlIGJlbG93LgoKPkZvciBleGFtcGxlLCB0aGUgc2VydmVyIHRpbWUgY2FsY3VsYXRpb24gc2VlbXMgdG8gYXNzdW1lIHRoYXQgYSByZXNwb25zZQo.cGFja2V0IGhhcyB0byBiZSBzZW50IGltbWUBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.160.587
References: <20131015235832.2100.62094.idtracker@ietfa.amsl.com> <1381881831.35197.YahooMailNeo@web2801.biz.mail.ne1.yahoo.com> <525E9152.60209@globis.net>
Message-ID: <1381930868.81291.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com>
Date: Wed, 16 Oct 2013 06:41:08 -0700 (PDT)
From: Nalini Elkins <nalini.elkins@insidethestack.com>
Subject: Re: Fw: New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-03.txt
To: Ray Hunter <v6ops@globis.net>
In-Reply-To: <525E9152.60209@globis.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: v6ops WG <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Nalini Elkins <nalini.elkins@insidethestack.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: Wed, 16 Oct 2013 13:41:22 -0000

> I have read this draft.=0A=0A>All in all it seems rather simplistic, and =
I can't help thinking that=0A>there's much more to this than is expressed i=
n the draft.=0A=0AYes. =C2=A0There is. =C2=A0See below.=0A=0A>For example, =
the server time calculation seems to assume that a response=0A>packet has t=
o be sent immediately by every application as soon as data=0A>has been proc=
essed: every response requires a response.=0A=0ANot at all.=0A=0A>What addi=
tional processing is required to cater for cases where the=0A>sender and th=
e receiver simply have nothing to say to each other at that=0A>point in tim=
e?=0A=0AFrankly, other than keep-alives, I have not seen this. =C2=A0Please=
 correct me if I am wrong.=0A=0AThe logic for processing and making 'sense'=
 of these metrics is much more complex than the fields to be sent. =C2=A0Th=
is is as it should be. =C2=A0 The OS needs to send packets quickly. =C2=A0A=
fter the fact, we can take our time and do analysis.=0A=0AWhat needs to be =
handled (at a minimum) are the following cases. =C2=A0You may have more.=0A=
=0A1. =C2=A0 Host clocks=C2=A0not synchronized - done=0A2. =C2=A0 IP fragme=
ntation=C2=A0=0A3. =C2=A0 Multiple=C2=A0sends from one side (multiple segme=
nts)=C2=A0=0A4. =C2=A0=C2=A0Out=C2=A0of order segments (PSN will go negativ=
e)=0A5. =C2=A0=C2=A0Retransmits=C2=A0(PSN will go negative)=0A6. =C2=A0 One=
=E2=80=93way transmit only (ex. FTP) =C2=A0(server delta will continually i=
ncrease)=0A7 =C2=A0 =C2=A0Delayed acks=0A8. =C2=A0 ACKs preceeding send for=
 another reason=0A9 =C2=A0 =C2=A0Proxy servers=0A10. Full=C2=A0duplex traff=
ic=0A11. Keep alive (0 / 1 byte segments, larger segments)=0A12. No respons=
e from other side (your case - which I believe to fall under Keep Alives) =
=C2=A0=0A,=0A=0AI have only provided the most basic case in this draft. =C2=
=A0 But, have thought a great deal about these others and how they would be=
 handled. =C2=A0I can provide packet flows for all these above to let you k=
now how these can be handled. =C2=A0Again, if you have more cases, I welcom=
e your input.=0A=0AAdditionally, I am in no way suggesting that this be the=
 ONLY metric that is used to calculate errors or performance. =C2=A0For exa=
mple, =C2=A0if you look at my definition of the "Retransmit Duplication" me=
tric, you will see that TCP sequence number is used in addition to the Pack=
et Sequence Number to good effect.=C2=A0=0A=C2=A0=0A=C2=A0=0ARegards,=0ARay=
H

From v6ops@globis.net  Wed Oct 16 07:14:28 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9B3B11E81D3; Wed, 16 Oct 2013 07:14:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2e4v9xPSUB-k; Wed, 16 Oct 2013 07:14:28 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 2322C11E81DB; Wed, 16 Oct 2013 07:14:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id E4D05870074; Wed, 16 Oct 2013 16:14:24 +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 ucbpHUt47nty; Wed, 16 Oct 2013 16:14:24 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id C2E69870073; Wed, 16 Oct 2013 16:14:24 +0200 (CEST)
Message-ID: <525E9F3F.2020600@globis.net>
Date: Wed, 16 Oct 2013 16:14:23 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Nalini Elkins <nalini.elkins@insidethestack.com>
Subject: Re: Fw: New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-03.txt
References: <20131015235832.2100.62094.idtracker@ietfa.amsl.com> <1381881831.35197.YahooMailNeo@web2801.biz.mail.ne1.yahoo.com> <525E9152.60209@globis.net> <1381930868.81291.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com>
In-Reply-To: <1381930868.81291.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Cc: v6ops WG <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 16 Oct 2013 14:14:28 -0000

> Nalini Elkins <mailto:nalini.elkins@insidethestack.com>
> 16 October 2013 15:41
>> I have read this draft.
>
>> All in all it seems rather simplistic, and I can't help thinking that
>> there's much more to this than is expressed in the draft.
>
> Yes.  There is.  See below.

Then I would humbly suggest that you consider keeping this as a clean
standards track draft just defining the message formats for the
transport (in 6man WG) = Section 1 & 2, and leave the use cases,
architecture, and calculations to other informational drafts (e.g. in
ippm) = Section 3,4. c.f. SNMP
>> For example, the server time calculation seems to assume that a response
>> packet has to be sent immediately by every application as soon as data
>> has been processed: every response requires a response.
>
> Not at all.
>
>> What additional processing is required to cater for cases where the
>> sender and the receiver simply have nothing to say to each other at that
>> point in time?
>
> Frankly, other than keep-alives, I have not seen this.  Please correct me if I am wrong.
>
> The logic for processing and making 'sense' of these metrics is much more complex than the fields to be sent.  This is as it should be.   The OS needs to send packets quickly.  After the fact, we can take our time and do analysis.
>
> What needs to be handled (at a minimum) are the following cases.  You may have more.
>
> 1.   Host clocks not synchronized - done
> 2.   IP fragmentation 
> 3.   Multiple sends from one side (multiple segments) 
> 4.   Out of order segments (PSN will go negative)
> 5.   Retransmits (PSN will go negative)
> 6.   Oneâ€“way transmit only (ex. FTP)  (server delta will continually increase)
> 7    Delayed acks
> 8.   ACKs preceeding send for another reason
> 9    Proxy servers
> 10. Full duplex traffic
> 11. Keep alive (0 / 1 byte segments, larger segments)
> 12. No response from other side (your case - which I believe to fall under Keep Alives)  
> ,
>
> I have only provided the most basic case in this draft.   But, have thought a great deal about these others and how they would be handled.  I can provide packet flows for all these above to let you know how these can be handled.  Again, if you have more cases, I welcome your input.

6. one way transmit only (e.g.real time transports and streaming
protocols, although RTP has it's own timestamps based on NTP)

13. Drop without retransmit (real time transports)
14. Looped packets (where the same packet may pass the same point
multiple times without duplication)
15. Multihoming via Shim6
> Additionally, I am in no way suggesting that this be the ONLY metric that is used to calculate errors or performance.  For example,  if you look at my definition of the "Retransmit Duplication" metric, you will see that TCP sequence number is used in addition to the Packet Sequence Number to good effect. 
>  
>

-- 
Regards,
RayH


From nalini.elkins@insidethestack.com  Wed Oct 16 07:28:03 2013
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6704F11E81DB for <ipv6@ietfa.amsl.com>; Wed, 16 Oct 2013 07:28:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.436
X-Spam-Level: 
X-Spam-Status: No, score=-2.436 tagged_above=-999 required=5 tests=[AWL=0.163,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CVqUWE3x4gg6 for <ipv6@ietfa.amsl.com>; Wed, 16 Oct 2013 07:28:03 -0700 (PDT)
Received: from nm27.access.bullet.mail.bf1.yahoo.com (nm27.access.bullet.mail.bf1.yahoo.com [216.109.114.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4FD8211E82A5 for <ipv6@ietf.org>; Wed, 16 Oct 2013 07:27:56 -0700 (PDT)
Received: from [66.196.81.158] by nm27.access.bullet.mail.bf1.yahoo.com with NNFMP; 16 Oct 2013 14:27:55 -0000
Received: from [66.196.81.126] by tm4.access.bullet.mail.bf1.yahoo.com with NNFMP; 16 Oct 2013 14:27:55 -0000
Received: from [127.0.0.1] by omp1002.access.mail.bf1.yahoo.com with NNFMP; 16 Oct 2013 14:27:55 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 747758.40628.bm@omp1002.access.mail.bf1.yahoo.com
Received: (qmail 16838 invoked by uid 60001); 16 Oct 2013 14:27:55 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1381933675; bh=vyXxIzfBO5pxgoDZyas51ZQJGK5zOWp8DDcQs6NzN9E=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=OvJMIay+Lsv/T9vmYTrMqx759OxrWSXupHh3M0w7p1OHKjMrpkjDf28l0AqCzI3Btkd3++I5YugAGB8tU4bmbSJdUpXXsiLyNbohPylT+pLaOWgmMKPdRHwTCBqJP5b2udyzUinxrPDmIiE+IvCLZO3XfG33KSyS0v5gKx++PkM=
X-YMail-OSG: hY5N5ykVM1mHmqJizrmjHCT4oNTk7BAoILWiQ9ltii1GVqr SlP_EdbfG6it6nleU6mGYTwTpIJFmlZopS.oOGeNTKDG625v9m5v2k1ia4dp 7ilhmU69MZ_lx_CHfc2svhwOF4w2t7YrU.TTgvalckqrAtuNUO479gdJ2GjV tBgSgwmdT1SQIC1q1._qLl09PdwfWRBs.kXPgPWcZ.od6a0VhfcxIwoVt51t iSgJ7p9pFF3xJbfy5O2nIxnKOtsm_ofjd3v.h1LuPQ2AaVtbD9AGsnF7iIgY rfqxH5d9iDm.xpCfqFWpI8KnoqiHg.B6uLjIIpNnt2PBuKFKIzpYwpqwdNc9 E640KTnXK1GhpzCza1vAbdSuznLiHnm3OUiuAAtjB5qwVFr_5PJdo7QB8BMj mMzwuOT.CNZt3fg4MCEUlEZzS5jphERZphOaY9Z9jfT2aiYC2ayuhCYj1Slg QYEbwyksTCtd6HDxvbtPoZ7TXVPkZi3qPoe.mkH9zZrFvD0600yWkXvbw5Iv LIOP4SYoF3Pn067qyRUINLQcq6rRbg54OjDAUMGOM17_r4HF6Ua9LQfL_MPa 0Px24YjF67TSw0a8x_C4F3dhdlw8PmRTlMln0dw--
Received: from [24.130.37.147] by web2803.biz.mail.ne1.yahoo.com via HTTP; Wed, 16 Oct 2013 07:27:55 PDT
X-Rocket-MIMEInfo: 002.001, UmF5LAoKVGhhbmsgeW91IHZlcnkgbXVjaCBmb3IgeW91ciBjb21tZW50cyBhbmQgeW91ciBncmVhdCB1c2UgY2FzZXMuCsKgCj4.PiBJIGhhdmUgcmVhZCB0aGlzIGRyYWZ0LgoKPj4KPj4.IEFsbCBpbiBhbGwgaXQgc2VlbXMgcmF0aGVyIHNpbXBsaXN0aWMsIGFuZCBJIGNhbid0IGhlbHAgdGhpbmtpbmcgdGhhdAo.Pj4gdGhlcmUncyBtdWNoIG1vcmUgdG8gdGhpcyB0aGFuIGlzIGV4cHJlc3NlZCBpbiB0aGUgZHJhZnQuCj4.Cj4.IFllcy7CoCBUaGVyZSBpcy7CoCBTZWUgYmVsb3cuCgo.wqBUaGVuIEkgd28BMAEBAQE-
X-Mailer: YahooMailWebService/0.8.160.587
References: <20131015235832.2100.62094.idtracker@ietfa.amsl.com> <1381881831.35197.YahooMailNeo@web2801.biz.mail.ne1.yahoo.com> <525E9152.60209@globis.net> <1381930868.81291.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com> <525E9F3F.2020600@globis.net>
Message-ID: <1381933675.16692.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com>
Date: Wed, 16 Oct 2013 07:27:55 -0700 (PDT)
From: Nalini Elkins <nalini.elkins@insidethestack.com>
Subject: Re: Fw: New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-03.txt
To: Ray Hunter <v6ops@globis.net>
In-Reply-To: <525E9F3F.2020600@globis.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: v6ops WG <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Nalini Elkins <nalini.elkins@insidethestack.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: Wed, 16 Oct 2013 14:28:03 -0000

Ray,=0A=0AThank you very much for your comments and your great use cases.=
=0A=A0=0A>>> I have read this draft.=0A=0A>>=0A>>> All in all it seems rath=
er simplistic, and I can't help thinking that=0A>>> there's much more to th=
is than is expressed in the draft.=0A>>=0A>> Yes.=A0 There is.=A0 See below=
.=0A=0A>=A0Then I would humbly suggest that you consider keeping this as a =
clean=0A>standards track draft just defining the message formats for the=0A=
>transport (in 6man WG) =3D Section 1 & 2, and leave the use cases,=0A>arch=
itecture, and calculations to other informational drafts (e.g. in=0A>ippm) =
=3D Section 3,4. c.f. SNMP=0A=A0=0AI will do this and provide an updated ve=
rsion of both IPPM and 6Man documents by end of day today. =A0I will also a=
dd use cases to the IPPM document.=0A=0AIf any others have use cases or com=
ments, I would very much appreciate hearing from you.=0A=0AThanks,=0ANalini

From Fred.L.Templin@boeing.com  Wed Oct 16 08:08:35 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D01B611E82B0; Wed, 16 Oct 2013 08:08:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.503
X-Spam-Level: 
X-Spam-Status: No, score=-6.503 tagged_above=-999 required=5 tests=[AWL=0.096,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4FO6ia-QcJ2a; Wed, 16 Oct 2013 08:08:27 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (stl-mbsout-01.boeing.com [130.76.96.169]) by ietfa.amsl.com (Postfix) with ESMTP id 7C0C511E8138; Wed, 16 Oct 2013 08:08:24 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9GF8Jpr010244; Wed, 16 Oct 2013 10:08:19 -0500
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9GF8Bnn009660 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Wed, 16 Oct 2013 10:08:18 -0500
Received: from XCH-BLV-404.nw.nos.boeing.com (130.247.25.157) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Wed, 16 Oct 2013 08:08:13 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-BLV-404.nw.nos.boeing.com ([130.247.25.157]) with mapi id 14.03.0158.001; Wed, 16 Oct 2013 08:08:12 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Fernando Gont <fgont@si6networks.com>, Ronald Bonica <rbonica@juniper.net>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOyf6Aebc9KTehbEGO6mhunuAlj5n3bUGg
Date: Wed, 16 Oct 2013 15:08:11 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812F4CA@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com> <525DD007.8030100@si6networks.com>
In-Reply-To: <525DD007.8030100@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Ray Hunter <v6ops@globis.net>, 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 16 Oct 2013 15:08:35 -0000

Hi Fernando,

To repeat what has already been said many times (and hopefully for
just one final time), if the host is permitted to include an MTU-sized
header chain and if there is a tunnel on the path that needs to fragment
for whatever reason, then that header chain is going to spill into a
second fragment. Then, middleboxes that wish to examine the entire
header chain in the first fragment for whatever reason will be unable
to do so. Consensus or no, those are the facts.

Thanks - Fred
fred.l.templin@boeing.com

> -----Original Message-----
> From: Fernando Gont [mailto:fgont@si6networks.com]
> Sent: Tuesday, October 15, 2013 4:30 PM
> To: Templin, Fred L; Ronald Bonica; Brian E Carpenter
> Cc: 6man Mailing List; ietf@ietf.org; Ray Hunter; 6man-
> chairs@tools.ietf.org
> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> On 10/14/2013 02:39 PM, Templin, Fred L wrote:
> >
> >> Is there a way to decouple this discussion from draft-ietf-6man-
> >> oversized-header-chain? I would be glad to discuss it in the context
> of
> >> a separate draft.
> >
> > I don't know if there is a way to decouple it. I believe I have shown
> > a way to not mess up tunnels while at the same time not messing up
> your
> > draft. That should be a win-win. In what way would imposing a 1K
> limit
> > on the IPv6 header chain not satisfy the general case?
>=20
> 6man had consensus multiple times on *not* to impose this sort of
> limits
> in this document (that's why the original limit of 1280 bytes was
> removed from earlier versions of this I-D in the first place).
>=20
> Thanks,
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>=20
>=20
>=20


From otroan@employees.org  Wed Oct 16 08:28:58 2013
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BC4A11E82D9; Wed, 16 Oct 2013 08:28:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sb7eTdJmPvaH; Wed, 16 Oct 2013 08:28:57 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) by ietfa.amsl.com (Postfix) with ESMTP id 8291711E813A; Wed, 16 Oct 2013 08:28:57 -0700 (PDT)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id F41D35F68; Wed, 16 Oct 2013 08:28:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; s=selector1; bh=X3Ps8OuUulRCNLuJRt0OK Q88N+8=; b=WMFbI56VSPZrlcpiKgQM7N0yz5xtr+WQprYCJeN+8e0dzci4CV+bb 0odAokdVrXGqSwBGRjNLDDM3S2+sOHZ9dJS5yVmWkdRWM37Xhi3xvDR3O4J+rwhd FDG89KbcT5zKKxquGxnuC4oKXxAO7OWsqtJrAZ4qJDcICE7KBKhN9U=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; q=dns; s=selector1; b=oWy2Bfko4cK5QPY X2cUHLiQeM2i1/c1As3M3qJIDlDldFdcfkiCRGBMj4AQe8quouVRYlcRySh7qK7P si5e0qPCEHkZsNjz6QBWXvOYilXfHAIJFd5F3sUJlFkjP+3jmGBmwn4iChKbBvtf 8qSqYUCmOCVn2d1ux8MRlHAejGEI=
Received: from dhcp-10-61-106-123.cisco.com (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 16CB75F46; Wed, 16 Oct 2013 08:28:54 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_D90E7994-AC9C-4D8C-8234-D377D47CD6B4"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
From: Ole Troan <otroan@employees.org>
In-Reply-To: <2134F8430051B64F815C691A62D9831812F4CA@XCH-BLV-504.nw.nos.boeing.com>
Date: Wed, 16 Oct 2013 17:28:52 +0200
Message-Id: <57E5A58E-0DAF-4545-8580-ACDB59475F46@employees.org>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com> <525DD007.8030100@si6networks.com> <2134F8430051B64F815C691A62 D9831812 F4CA@XCH-BLV-504.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.1510)
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.net>, Fernando Gont <fgont@si6networks.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 16 Oct 2013 15:28:58 -0000

--Apple-Mail=_D90E7994-AC9C-4D8C-8234-D377D47CD6B4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Fred,

> To repeat what has already been said many times (and hopefully for
> just one final time), if the host is permitted to include an MTU-sized
> header chain and if there is a tunnel on the path that needs to =
fragment
> for whatever reason, then that header chain is going to spill into a
> second fragment. Then, middleboxes that wish to examine the entire
> header chain in the first fragment for whatever reason will be unable
> to do so. Consensus or no, those are the facts.

absolutely.

the outer IPv6 header is a new datalink for the inner IPv6 header. there =
is no architectural difference if that L2 is IPv6, IPv4 or PPP. take =
IPv4 or PPP as an example, if PPP provides fragmentation, then there is =
no expectation that the PPP or IPv4 layer keeps the payload IPv6 header =
chain in one PPP or IPv4 fragment.

the rules in this document are not recursive. the header chain =
terminates as soon as another IPv6 header is encountered.

does that clarification help?
I'm not quite sure if the document is clear enough on this point.

Best regards,
Ole

--Apple-Mail=_D90E7994-AC9C-4D8C-8234-D377D47CD6B4
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

iQEcBAEBCgAGBQJSXrC0AAoJEFuJXizso86gtm4H/3KRIsq5161t/jzpNQR2CC+O
fLGl8vC57ntMjXbv0NR72DI6F83HtX5cLgVimCYJF+bne+KJQwqVufedqnk/iANS
irxBnhdWWBHXU53KZpfIxKS0opxLN90W5u1IEja+0DLWSOQ8S39rvbxbDJOXXSFw
DL/kkrX/h9kyEjHJgFxWx9EKp+xShGsqza1cbkb6kM1rDTAm3QLJkcc4AC6ZNnw+
M0xeseBHdz5VNQ2B/hm25X9T2BzNygJJDc6gvJPAxOyIqer096xLKsVs4Q35bWo3
5kpqy0LW16DId2neGITNAkt29vCucQrV2L65E6pp5j1JcwPiC8Hsj6invzwaowA=
=+4kr
-----END PGP SIGNATURE-----

--Apple-Mail=_D90E7994-AC9C-4D8C-8234-D377D47CD6B4--

From Fred.L.Templin@boeing.com  Wed Oct 16 08:45:38 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4347A11E8318; Wed, 16 Oct 2013 08:45:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.507
X-Spam-Level: 
X-Spam-Status: No, score=-6.507 tagged_above=-999 required=5 tests=[AWL=0.092,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NSNxkJotu5im; Wed, 16 Oct 2013 08:45:29 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) by ietfa.amsl.com (Postfix) with ESMTP id D414F11E82B3; Wed, 16 Oct 2013 08:45:29 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9GFjL75011680; Wed, 16 Oct 2013 08:45:22 -0700
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9GFjJtO011633 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Wed, 16 Oct 2013 08:45:19 -0700
Received: from XCH-BLV-208.nw.nos.boeing.com (10.57.37.5) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Wed, 16 Oct 2013 08:45:09 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-BLV-208.nw.nos.boeing.com ([169.254.8.27]) with mapi id 14.03.0158.001; Wed, 16 Oct 2013 08:45:08 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ole Troan <otroan@employees.org>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOyoRrebc9KTehbEGO6mhunuAlj5n3duEg
Date: Wed, 16 Oct 2013 15:45:07 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812F69E@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com> <525DD007.8030100@si6networks.com> <2134F8430051B64F815C691A6! 2D9831812 F4CA@XCH-BLV-504.nw.nos.boeing.com> <57E5A58E-0DAF-4545-8580-ACDB59475F46@employees.org>
In-Reply-To: <57E5A58E-0DAF-4545-8580-ACDB59475F46@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.net>, Fernando Gont <fgont@si6networks.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 16 Oct 2013 15:45:38 -0000

Hi Ole,

> -----Original Message-----
> From: Ole Troan [mailto:otroan@employees.org]
> Sent: Wednesday, October 16, 2013 8:29 AM
> To: Templin, Fred L
> Cc: Fernando Gont; Ronald Bonica; Brian E Carpenter; 6man-
> chairs@tools.ietf.org; Ray Hunter; 6man Mailing List; ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> Fred,
>=20
> > To repeat what has already been said many times (and hopefully for
> > just one final time), if the host is permitted to include an MTU-
> sized
> > header chain and if there is a tunnel on the path that needs to
> fragment
> > for whatever reason, then that header chain is going to spill into a
> > second fragment. Then, middleboxes that wish to examine the entire
> > header chain in the first fragment for whatever reason will be unable
> > to do so. Consensus or no, those are the facts.
>=20
> absolutely.
>=20
> the outer IPv6 header is a new datalink for the inner IPv6 header.
> there is no architectural difference if that L2 is IPv6, IPv4 or PPP.
> take IPv4 or PPP as an example, if PPP provides fragmentation, then
> there is no expectation that the PPP or IPv4 layer keeps the payload
> IPv6 header chain in one PPP or IPv4 fragment.
>=20
> the rules in this document are not recursive. the header chain
> terminates as soon as another IPv6 header is encountered.

I disagree with the header chain terminating as soon as another IPv6
header is encounter. That defeats defense-in-depth, since outer
perimeter middleboxes would be forced to admit packets with unexamined
header chains inward to inner perimeter middleboxes. And, if the
unexamined header chains contain bad stuff inserted by an attacker,
the attack is successful.

That requirement is also not observed by common middlebox systems
such as Wireshark and tcpdump. Both will blast past encapsulating
IPv6 headers through to the header chain inserted by the original
host without stopping at the outermost IPv6 header.

Thanks - Fred
fred.l.templin@boeing.com
=20
> does that clarification help?
> I'm not quite sure if the document is clear enough on this point.
>=20
> Best regards,
> Ole

From fernando.gont.netbook@gmail.com  Wed Oct 16 09:09:07 2013
Return-Path: <fernando.gont.netbook@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85BE511E82FE; Wed, 16 Oct 2013 09:09:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qothIjMHhAiO; Wed, 16 Oct 2013 09:09:06 -0700 (PDT)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 1CC6C21F9FC3; Wed, 16 Oct 2013 09:09:06 -0700 (PDT)
Received: by mail-pd0-f172.google.com with SMTP id z10so1143906pdj.17 for <multiple recipients>; Wed, 16 Oct 2013 09:09:05 -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=3hwUh9nA2FaR+Z+wtkJxmZfwtOtH+aswk8l22UbGYuQ=; b=wBbkqxpxw2R98dLotN/l6UAqqPoDUKwFoYYgCE/FY+yEzatk/mxbsXveXfcTpSdbFy B4qGboYAm39QHxYXQ5L5DSJKhgWf50n5hTTp7h6f53vi7P50mgO1Rhyy5liY3WbFVZMY u5BEjH8nGpAR0HDynoywwqkJUOHM37pSbXkcffHrLdzj28Fx8+TiReBBac0z3xmpKB0v F6XV0xvvEWT0stdYyae31q6ZsINTxDn3tXDDMyQ2xxTbolJoG4234mzQsfvnwUVPnTzO 4b+BHMHgdu3AdHyqahMeoUvUmOFhUoQXkofW7aIxv6t4nx0Iqe1wB+NFK0q5EgSmUL/C 10YQ==
MIME-Version: 1.0
X-Received: by 10.68.197.129 with SMTP id iu1mr3628345pbc.139.1381939745742; Wed, 16 Oct 2013 09:09:05 -0700 (PDT)
Sender: fernando.gont.netbook@gmail.com
Received: by 10.70.119.38 with HTTP; Wed, 16 Oct 2013 09:09:05 -0700 (PDT)
In-Reply-To: <2134F8430051B64F815C691A62D9831812F69E@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com> <525DD007.8030100@si6networks.com> <57E5A58E-0DAF-4545-8580-ACDB59475F46@employees.org> <2134F8430051B64F815C691A62D9831812F69E@XCH-BLV-504.nw.nos.boeing.com>
Date: Wed, 16 Oct 2013 13:09:05 -0300
X-Google-Sender-Auth: TjNstjMBIgbkP_Z1hFM-w3kpeqc
Message-ID: <CANej4=jeYpEm89n6mTzv+vEdhOrXjG9Da3XMgtPp7eS+oa+jDg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
From: Fernando Gont <fernando@gont.com.ar>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Content-Type: multipart/alternative; boundary=e89a8ff1cce4a568e204e8ddeb7d
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.net>, Fernando Gont <fgont@si6networks.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 16 Oct 2013 16:09:07 -0000

--e89a8ff1cce4a568e204e8ddeb7d
Content-Type: text/plain; charset=ISO-8859-1

Hi, Fred,

On Wed, Oct 16, 2013 at 12:45 PM, Templin, Fred L <Fred.L.Templin@boeing.com
> wrote:

> I disagree with the header chain terminating as soon as another IPv6
> header is encounter. That defeats defense-in-depth, since outer
> perimeter middleboxes would be forced to admit packets with unexamined
> header chains inward to inner perimeter middleboxes. And, if the
> unexamined header chains contain bad stuff inserted by an attacker,
> the attack is successful.
>

The same is true if the underlying encapsulation layer is IPv4. Once you're
encapsulating, all bets are off in that respect. You should do
defense-in-depth at the tunnel ingress or egress points. Or, if you wish, a
middle-box could reassemble-inspect/filter-re-fragment

Note that no matter what hardcoded limit you enforce, an attacker willing
to evade you're security controls can always add an extra-layer of
encapsulation (assuming he controls that). Also, common security policy is
"default deny" -- so if the attacker plays dirty, his packets will be
dropped.



> That requirement is also not observed by common middlebox systems
> such as Wireshark and tcpdump. Both will blast past encapsulating
> IPv6 headers through to the header chain inserted by the original
> host without stopping at the outermost IPv6 header.
>

They do what a middle-box would do in this case: whatever part of the
header chain is there, it's up to you to inspect it. As noted by Ole, when
you tunnel over IP, IP becomes a link layer... so whatever "defense in
depth" techniques you're using, they should be prepared to deal with
scenarios in which a tunneled packet does not contain the entire IPv6
header chain, since not all "link layers" (as IPv4 when IPv6 is tuneled
over IPv4) guarantee a minimum MTU of 1280 bytes.

Thanks,
Fernando

--e89a8ff1cce4a568e204e8ddeb7d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra">Hi, Fred,<br></div><div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Oct 16, 2013 at 12:=
45 PM, Templin, Fred L <span dir=3D"ltr">&lt;<a href=3D"mailto:Fred.L.Templ=
in@boeing.com" target=3D"_blank">Fred.L.Templin@boeing.com</a>&gt;</span> w=
rote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I disagree with the header chain terminating=
 as soon as another IPv6<br>
header is encounter. That defeats defense-in-depth, since outer<br>
perimeter middleboxes would be forced to admit packets with unexamined<br>
header chains inward to inner perimeter middleboxes. And, if the<br>
unexamined header chains contain bad stuff inserted by an attacker,<br>
the attack is successful.<br></blockquote><div><br></div><div>The same is t=
rue if the underlying encapsulation layer is IPv4. Once you&#39;re encapsul=
ating, all bets are off in that respect. You should do defense-in-depth at =
the tunnel ingress or egress points. Or, if you wish, a middle-box could re=
assemble-inspect/filter-re-fragment<br>
<br></div><div>Note that no matter what hardcoded limit you enforce, an att=
acker willing to evade you&#39;re security controls can always add an extra=
-layer of encapsulation (assuming he controls that). Also, common security =
policy is &quot;default deny&quot; -- so if the attacker plays dirty, his p=
ackets will be dropped.<br>
<br>=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">

That requirement is also not observed by common middlebox systems<br>
such as Wireshark and tcpdump. Both will blast past encapsulating<br>
IPv6 headers through to the header chain inserted by the original<br>
host without stopping at the outermost IPv6 header.<br></blockquote><div>=
=A0</div>They do what a middle-box would do in this case: whatever part of =
the header chain is there, it&#39;s up to you to inspect it. As noted by Ol=
e, when you tunnel over IP, IP becomes a link layer... so whatever &quot;de=
fense in depth&quot; techniques you&#39;re using, they should be prepared t=
o deal with scenarios in which a tunneled packet does not contain the entir=
e IPv6 header chain, since not all &quot;link layers&quot; (as IPv4 when IP=
v6 is tuneled over IPv4) guarantee a minimum MTU of 1280 bytes.<br>
<br></div><div class=3D"gmail_quote">Thanks,<br></div><div class=3D"gmail_q=
uote">Fernando<br><br><br><br><br></div></div></div>

--e89a8ff1cce4a568e204e8ddeb7d--

From Fred.L.Templin@boeing.com  Wed Oct 16 09:20:31 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46F4511E8304; Wed, 16 Oct 2013 09:20:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.511
X-Spam-Level: 
X-Spam-Status: No, score=-6.511 tagged_above=-999 required=5 tests=[AWL=0.087,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id se3QiwC1zaMV; Wed, 16 Oct 2013 09:20:25 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) by ietfa.amsl.com (Postfix) with ESMTP id 9DC7411E8146; Wed, 16 Oct 2013 09:20:24 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9GGKMfi000676; Wed, 16 Oct 2013 11:20:23 -0500
Received: from XCH-PHX-211.sw.nos.boeing.com (xch-phx-211.sw.nos.boeing.com [130.247.25.140]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9GGKLFu000665 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Wed, 16 Oct 2013 11:20:21 -0500
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-PHX-211.sw.nos.boeing.com ([169.254.11.248]) with mapi id 14.03.0158.001; Wed, 16 Oct 2013 09:20:20 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Fernando Gont <fernando@gont.com.ar>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOyooJebc9KTehbEGO6mhunuAlj5n3gcJg
Date: Wed, 16 Oct 2013 16:20:19 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812F7BD@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net>	<5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com>	<52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com> <525DD007.8030100@si6networks.com> <57E5A58E-0DAF-4545-8580-ACDB59475F46@employees.org> <2134F8430051B64F815C691A62D9831812F69E@XCH-BLV-504.nw.nos.boeing.com> <CANej4=jeYpEm89n6mTzv+vEdhOrXjG9Da3XMgtPp7eS+oa+jDg@mail.gmail.com>
In-Reply-To: <CANej4=jeYpEm89n6mTzv+vEdhOrXjG9Da3XMgtPp7eS+oa+jDg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: multipart/alternative; boundary="_000_2134F8430051B64F815C691A62D9831812F7BDXCHBLV504nwnosboe_"
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.net>, Fernando Gont <fgont@si6networks.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 16 Oct 2013 16:20:31 -0000

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

Fernando,

Can you please re-send in plaintext, as all of the other messages in this t=
hread
have been? Richly formatted text makes annotation impossible.

Thanks - Fred

From: fernando.gont.netbook@gmail.com [mailto:fernando.gont.netbook@gmail.c=
om] On Behalf Of Fernando Gont
Sent: Wednesday, October 16, 2013 9:09 AM
To: Templin, Fred L
Cc: Ole Troan; 6man-chairs@tools.ietf.org; 6man Mailing List; ietf@ietf.org=
; Ray Hunter; Fernando Gont
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Im=
plications of Oversized IPv6 Header Chains) to Proposed Standard

Hi, Fred,

On Wed, Oct 16, 2013 at 12:45 PM, Templin, Fred L <Fred.L.Templin@boeing.co=
m<mailto:Fred.L.Templin@boeing.com>> wrote:
I disagree with the header chain terminating as soon as another IPv6
header is encounter. That defeats defense-in-depth, since outer
perimeter middleboxes would be forced to admit packets with unexamined
header chains inward to inner perimeter middleboxes. And, if the
unexamined header chains contain bad stuff inserted by an attacker,
the attack is successful.

The same is true if the underlying encapsulation layer is IPv4. Once you're=
 encapsulating, all bets are off in that respect. You should do defense-in-=
depth at the tunnel ingress or egress points. Or, if you wish, a middle-box=
 could reassemble-inspect/filter-re-fragment
Note that no matter what hardcoded limit you enforce, an attacker willing t=
o evade you're security controls can always add an extra-layer of encapsula=
tion (assuming he controls that). Also, common security policy is "default =
deny" -- so if the attacker plays dirty, his packets will be dropped.


That requirement is also not observed by common middlebox systems
such as Wireshark and tcpdump. Both will blast past encapsulating
IPv6 headers through to the header chain inserted by the original
host without stopping at the outermost IPv6 header.

They do what a middle-box would do in this case: whatever part of the heade=
r chain is there, it's up to you to inspect it. As noted by Ole, when you t=
unnel over IP, IP becomes a link layer... so whatever "defense in depth" te=
chniques you're using, they should be prepared to deal with scenarios in wh=
ich a tunneled packet does not contain the entire IPv6 header chain, since =
not all "link layers" (as IPv4 when IPv6 is tuneled over IPv4) guarantee a =
minimum MTU of 1280 bytes.
Thanks,
Fernando




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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Fernando,<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Can you please re-send in=
 plaintext, as all of the other messages in this thread<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">have been? Richly formatt=
ed text makes annotation impossible.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks - Fred<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> fernando=
.gont.netbook@gmail.com [mailto:fernando.gont.netbook@gmail.com]
<b>On Behalf Of </b>Fernando Gont<br>
<b>Sent:</b> Wednesday, October 16, 2013 9:09 AM<br>
<b>To:</b> Templin, Fred L<br>
<b>Cc:</b> Ole Troan; 6man-chairs@tools.ietf.org; 6man Mailing List; ietf@i=
etf.org; Ray Hunter; Fernando Gont<br>
<b>Subject:</b> Re: Last Call: &lt;draft-ietf-6man-oversized-header-chain-0=
8.txt&gt; (Implications of Oversized IPv6 Header Chains) to Proposed Standa=
rd<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">Hi, Fred,<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Wed, Oct 16, 2013 at 12:45 PM, Templin, Fred L &l=
t;<a href=3D"mailto:Fred.L.Templin@boeing.com" target=3D"_blank">Fred.L.Tem=
plin@boeing.com</a>&gt; wrote:<o:p></o:p></p>
<p class=3D"MsoNormal">I disagree with the header chain terminating as soon=
 as another IPv6<br>
header is encounter. That defeats defense-in-depth, since outer<br>
perimeter middleboxes would be forced to admit packets with unexamined<br>
header chains inward to inner perimeter middleboxes. And, if the<br>
unexamined header chains contain bad stuff inserted by an attacker,<br>
the attack is successful.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">The same is true if t=
he underlying encapsulation layer is IPv4. Once you're encapsulating, all b=
ets are off in that respect. You should do defense-in-depth at the tunnel i=
ngress or egress points. Or, if you
 wish, a middle-box could reassemble-inspect/filter-re-fragment<o:p></o:p><=
/p>
</div>
<div>
<p class=3D"MsoNormal">Note that no matter what hardcoded limit you enforce=
, an attacker willing to evade you're security controls can always add an e=
xtra-layer of encapsulation (assuming he controls that). Also, common secur=
ity policy is &quot;default deny&quot; -- so
 if the attacker plays dirty, his packets will be dropped.<br>
<br>
&nbsp;<o:p></o:p></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class=3D"MsoNormal">That requirement is also not observed by common midd=
lebox systems<br>
such as Wireshark and tcpdump. Both will blast past encapsulating<br>
IPv6 headers through to the header chain inserted by the original<br>
host without stopping at the outermost IPv6 header.<o:p></o:p></p>
</blockquote>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">They do what a middle=
-box would do in this case: whatever part of the header chain is there, it'=
s up to you to inspect it. As noted by Ole, when you tunnel over IP, IP bec=
omes a link layer... so whatever &quot;defense
 in depth&quot; techniques you're using, they should be prepared to deal wi=
th scenarios in which a tunneled packet does not contain the entire IPv6 he=
ader chain, since not all &quot;link layers&quot; (as IPv4 when IPv6 is tun=
eled over IPv4) guarantee a minimum MTU of 1280
 bytes.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Thanks,<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Fernando<br>
<br>
<br>
<br>
<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_2134F8430051B64F815C691A62D9831812F7BDXCHBLV504nwnosboe_--


From fgont.si6networks@gmail.com  Wed Oct 16 09:34:50 2013
Return-Path: <fgont.si6networks@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F38EF11E8316; Wed, 16 Oct 2013 09:34:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.289
X-Spam-Level: 
X-Spam-Status: No, score=-2.289 tagged_above=-999 required=5 tests=[AWL=-0.311, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N83h5UGiYBi0; Wed, 16 Oct 2013 09:34:49 -0700 (PDT)
Received: from mail-wg0-x22c.google.com (mail-wg0-x22c.google.com [IPv6:2a00:1450:400c:c00::22c]) by ietfa.amsl.com (Postfix) with ESMTP id EB9F011E8329; Wed, 16 Oct 2013 09:34:48 -0700 (PDT)
Received: by mail-wg0-f44.google.com with SMTP id n12so984854wgh.23 for <multiple recipients>; Wed, 16 Oct 2013 09:34:47 -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=2A0KJ4SxFmBQUJSpwP7L2rz/0MP4NMuUqlY0CXkJ6x4=; b=Xga+QjvQUsb+nvK3YqYbT6KQ+wQNyWeS1A+IpUgVOzrBlOg2szRxVTr/SAfkWfyGk6 fjwJ4PpryuKH8zTfGT6UTel6mGcke5d/uSZzOjsifXoj1uG+hwuUxRwiSbywlaJYU3SB +SKSFCs/AI6Vl8BC8aYWvMfhouVBKpwIBweVrsxzsc01NxYsbHUjjLkPqr422sbAeAGB J4QHKG7S0dXGW+Dt2N+D796/bVnrcrgapgkHKiTDo/+EmmoE1BojQLZTd1JBN/JKQMah AnbNUZOwBV3NlLELwNokEPyyTbgwJowNi357b9FnMFRaPfa3vB7RtxZB+lTnUCUjm54f feeQ==
MIME-Version: 1.0
X-Received: by 10.194.89.233 with SMTP id br9mr3192125wjb.15.1381941287134; Wed, 16 Oct 2013 09:34:47 -0700 (PDT)
Sender: fgont.si6networks@gmail.com
Received: by 10.217.46.198 with HTTP; Wed, 16 Oct 2013 09:34:47 -0700 (PDT)
In-Reply-To: <2134F8430051B64F815C691A62D9831812F69E@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com> <525DD007.8030100@si6networks.com> <57E5A58E-0DAF-4545-8580-ACDB59475F46@employees.org> <2134F8430051B64F815C691A62D9831812F69E@XCH-BLV-504.nw.nos.boeing.com>
Date: Wed, 16 Oct 2013 13:34:47 -0300
X-Google-Sender-Auth: cWKPFPFDJm9DLHeoAQ4ENQ3a4wQ
Message-ID: <CAFQ9LJ+-4SdUdoku_on0YX9rTHMPBJQ-Yz7e+Rbb_PoFt1+TjA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
From: Fernando Gont <fgont@si6networks.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.net>, Fernando Gont <fgont@si6networks.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 16 Oct 2013 16:41:30 -0000

[Resending in plain-txt -- my apologies... I was using a web interface...]

Fred,

On Wed, Oct 16, 2013 at 12:45 PM, Templin, Fred L
<Fred.L.Templin@boeing.com> wrote:
> I disagree with the header chain terminating as soon as another IPv6
> header is encounter. That defeats defense-in-depth, since outer
> perimeter middleboxes would be forced to admit packets with unexamined
> header chains inward to inner perimeter middleboxes. And, if the
> unexamined header chains contain bad stuff inserted by an attacker,
> the attack is successful.

The same is true if the underlying encapsulation layer is IPv4. Once
you're encapsulating, all bets are off in that respect. You should do
defense-in-depth at the tunnel ingress or egress points. Or, if you
wish, a middle-box could reassemble-inspect/filter-re-fragment

Note that no matter what hardcoded limit you enforce, an attacker
willing to evade you're security controls can always add an
extra-layer of encapsulation (assuming he controls that). Also, common
security policy is "default deny" -- so if the attacker plays dirty,
his packets will be dropped.


> That requirement is also not observed by common middlebox systems
> such as Wireshark and tcpdump. Both will blast past encapsulating
> IPv6 headers through to the header chain inserted by the original
> host without stopping at the outermost IPv6 header.

They do what a middle-box would do in this case: whatever part of the
header chain is there, it's up to you to inspect it. As noted by Ole,
when you tunnel over IP, IP becomes a link layer... so whatever
"defense in depth" techniques you're using, they should be prepared to
deal with scenarios in which a tunneled packet does not contain the
entire IPv6 header chain, since not all "link layers" (as IPv4 when
IPv6 is tuneled over IPv4) guarantee a minimum MTU of 1280 bytes.

Thanks,
Fernando

From Fred.L.Templin@boeing.com  Wed Oct 16 09:54:29 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7836B11E8138; Wed, 16 Oct 2013 09:54:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.515
X-Spam-Level: 
X-Spam-Status: No, score=-6.515 tagged_above=-999 required=5 tests=[AWL=0.084,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iSYL2mZ96G9v; Wed, 16 Oct 2013 09:54:23 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) by ietfa.amsl.com (Postfix) with ESMTP id 4960511E82C3; Wed, 16 Oct 2013 09:54:21 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9GGsKmc007963; Wed, 16 Oct 2013 09:54:20 -0700
Received: from XCH-PHX-110.sw.nos.boeing.com (xch-phx-110.sw.nos.boeing.com [130.247.25.39]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9GGsJAv007928 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Wed, 16 Oct 2013 09:54:19 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-PHX-110.sw.nos.boeing.com ([169.254.10.89]) with mapi id 14.03.0158.001; Wed, 16 Oct 2013 09:54:18 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Fernando Gont <fgont@si6networks.com>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOyo2gebc9KTehbEGO6mhunuAlj5n3hyjw
Date: Wed, 16 Oct 2013 16:54:17 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812F8C5@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net>	<5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com>	<52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com> <525DD007.8030100@si6networks.com> <57E5A58E-0DAF-4545-8580-ACDB59475F46@employees.org> <2134F8430051B64F815C691A62D9831812F69E@XCH-BLV-504.nw.nos.boeing.com> <CAFQ9LJ+-4SdUdoku_on0YX9rTHMPBJQ-Yz7e+Rbb_PoFt1+TjA@mail.gmail.com>
In-Reply-To: <CAFQ9LJ+-4SdUdoku_on0YX9rTHMPBJQ-Yz7e+Rbb_PoFt1+TjA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 16 Oct 2013 16:54:29 -0000

Hi Fernando,

> -----Original Message-----
> From: fgont.si6networks@gmail.com [mailto:fgont.si6networks@gmail.com]
> On Behalf Of Fernando Gont
> Sent: Wednesday, October 16, 2013 9:35 AM
> To: Templin, Fred L
> Cc: Ole Troan; Ronald Bonica; Brian E Carpenter; 6man-
> chairs@tools.ietf.org; Ray Hunter; 6man Mailing List; ietf@ietf.org;
> Fernando Gont
> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> [Resending in plain-txt -- my apologies... I was using a web
> interface...]
>=20
> Fred,
>=20
> On Wed, Oct 16, 2013 at 12:45 PM, Templin, Fred L
> <Fred.L.Templin@boeing.com> wrote:
> > I disagree with the header chain terminating as soon as another IPv6
> > header is encounter. That defeats defense-in-depth, since outer
> > perimeter middleboxes would be forced to admit packets with
> unexamined
> > header chains inward to inner perimeter middleboxes. And, if the
> > unexamined header chains contain bad stuff inserted by an attacker,
> > the attack is successful.
>=20
> The same is true if the underlying encapsulation layer is IPv4.

We should not default to doing as badly as IPv4.

> Once
> you're encapsulating, all bets are off in that respect. You should do
> defense-in-depth at the tunnel ingress or egress points. Or, if you
> wish, a middle-box could reassemble-inspect/filter-re-fragment

If an outer perimeter middlebox connects to a 10Gbps link on its
outward facing interface and a 64Kbps link on its inward facing
interface, then the middlebox can allow a successful DOS attack
against its protected domain if it does not look at headers beyond
the outermost IPv6 header.

> Note that no matter what hardcoded limit you enforce, an attacker
> willing to evade you're security controls can always add an
> extra-layer of encapsulation (assuming he controls that).

Yes. With a 1024 limit on the amount of extension headers a
host can add, approximately 5-6 encapsulations can be added
before the tunnel headers cause the header chain to overflow
the IPv6 minMTU. But, that means that there would still be
5-6 protected perimeters to penetrate before an attack could
penetrate through to the innermost protected domain. This is
considerable defense-in-depth.

> Also, common
> security policy is "default deny" -- so if the attacker plays dirty,
> his packets will be dropped.

Without looking past the outermost IP header, there is no way
to discern the good stuff from the bad stuff. So, default
deny will potentially drop good stuff.

> > That requirement is also not observed by common middlebox systems
> > such as Wireshark and tcpdump. Both will blast past encapsulating
> > IPv6 headers through to the header chain inserted by the original
> > host without stopping at the outermost IPv6 header.
>=20
> They do what a middle-box would do in this case: whatever part of the
> header chain is there, it's up to you to inspect it. As noted by Ole,
> when you tunnel over IP, IP becomes a link layer... so whatever
> "defense in depth" techniques you're using, they should be prepared to
> deal with scenarios in which a tunneled packet does not contain the
> entire IPv6 header chain, since not all "link layers" (as IPv4 when
> IPv6 is tuneled over IPv4) guarantee a minimum MTU of 1280 bytes.

The 1024 proposal gives 256 bytes of room for encapsulation headers
and still fit within the IPv6 minMTU - enough for 5-6 layers of defense
in depth. This is part of the analysis I believe was missing when the
IPv6 minMTU of 1280 was established.

One clarification I would like to make is that I *like* the 1280
IPv6 minMTU and do not think it was a mistake. It was the missing
analysis of what it means for tunnels that I think we are only
now exploring.

Thanks - Fred
fred.l.templin@boeing.com

> Thanks,
> Fernando

From fgont.si6networks@gmail.com  Wed Oct 16 10:04:57 2013
Return-Path: <fgont.si6networks@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C52211E8109; Wed, 16 Oct 2013 10:04:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.834
X-Spam-Level: 
X-Spam-Status: No, score=-1.834 tagged_above=-999 required=5 tests=[AWL=-0.456, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_13=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zwc5hxEXBql1; Wed, 16 Oct 2013 10:04:56 -0700 (PDT)
Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 5292711E8191; Wed, 16 Oct 2013 10:04:51 -0700 (PDT)
Received: by mail-wg0-f45.google.com with SMTP id z12so1039591wgg.12 for <multiple recipients>; Wed, 16 Oct 2013 10:04:47 -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=M0nFWF45OUKsK1gdV7vlOUSaDrRrONlqohKpx5La+B4=; b=Bjd1QJ+sEJGSx7d/XxaZPlv6s7zBIHlozJ5P3QnYfS9dC4Rzzyr85Xf2c9aOUox6uG l/cm2ypTmqbZPH6I6YlVcHZpPv40C4ipGztgru4RvJ0LNkq1g5kHyffYyh3Im2dNwzIS yIKnhsa4mKRVp1qME1Y5UNPDzBVe/wfafwce9Q2k6IfXBxdnH/9Ii876I1HyL6KOl68f 7R4/Nn240l2En6i8t22mBLVW7/xHupT8e521o8KvTfTdQ0JnSrK5K5u1/ehT2umrGc8s SU1lZy+qCdxkh+NrwWjUGa/cPhCNTELVxEqn3Dn+dv0WrMMlRmm4YVXKgXjMv4fljE7w Lfyg==
MIME-Version: 1.0
X-Received: by 10.180.198.5 with SMTP id iy5mr15621028wic.45.1381943086490; Wed, 16 Oct 2013 10:04:46 -0700 (PDT)
Sender: fgont.si6networks@gmail.com
Received: by 10.217.46.198 with HTTP; Wed, 16 Oct 2013 10:04:46 -0700 (PDT)
In-Reply-To: <2134F8430051B64F815C691A62D9831812F8C5@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com> <525DD007.8030100@si6networks.com> <57E5A58E-0DAF-4545-8580-ACDB59475F46@employees.org> <2134F8430051B64F815C691A62D9831812F69E@XCH-BLV-504.nw.nos.boeing.com> <CAFQ9LJ+-4SdUdoku_on0YX9rTHMPBJQ-Yz7e+Rbb_PoFt1+TjA@mail.gmail.com> <2134F8430051B64F815C691A62D9831812F8C5@XCH-BLV-504.nw.nos.boeing.com>
Date: Wed, 16 Oct 2013 14:04:46 -0300
X-Google-Sender-Auth: OA63yt7cPR5bGiC6snn3uARP8HM
Message-ID: <CAFQ9LJJVqV0q-br5wsSCpUgH=M1BXMitohExh7-MQhsWjVABJA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
From: Fernando Gont <fgont@si6networks.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 16 Oct 2013 17:04:57 -0000

On Wed, Oct 16, 2013 at 1:54 PM, Templin, Fred L
<Fred.L.Templin@boeing.com> wrote:
>> On Wed, Oct 16, 2013 at 12:45 PM, Templin, Fred L
>> <Fred.L.Templin@boeing.com> wrote:
>> > I disagree with the header chain terminating as soon as another IPv6
>> > header is encounter. That defeats defense-in-depth, since outer
>> > perimeter middleboxes would be forced to admit packets with
>> unexamined
>> > header chains inward to inner perimeter middleboxes. And, if the
>> > unexamined header chains contain bad stuff inserted by an attacker,
>> > the attack is successful.
>>
>> The same is true if the underlying encapsulation layer is IPv4.
>
> We should not default to doing as badly as IPv4.

The point is that this is no worse than IPv4. And it is very likely
that one of underlying encapsulations will be IPv4.


>> Once
>> you're encapsulating, all bets are off in that respect. You should do
>> defense-in-depth at the tunnel ingress or egress points. Or, if you
>> wish, a middle-box could reassemble-inspect/filter-re-fragment
>
> If an outer perimeter middlebox connects to a 10Gbps link on its
> outward facing interface and a 64Kbps link on its inward facing
> interface, then the middlebox can allow a successful DOS attack
> against its protected domain if it does not look at headers beyond
> the outermost IPv6 header.

Is it me, or there are actually a plethora of attack vectors an
attacker would use (instead of this one) in such scenario?



>> Note that no matter what hardcoded limit you enforce, an attacker
>> willing to evade you're security controls can always add an
>> extra-layer of encapsulation (assuming he controls that).
>
> Yes. With a 1024 limit on the amount of extension headers a
> host can add, approximately 5-6 encapsulations can be added
> before the tunnel headers cause the header chain to overflow
> the IPv6 minMTU.

That depends on whether extension headers are employed in different
layer of encapsulation.

Besides, what's the different between an attacker exceeding your
hardcoded limit and traffic resulting in tunnling packets failing to
include the entire header chain?

As noted off-list, this hard limit becomes a BCP, rather than a std
update: the larger your extension header chain, the higher the chances
that your packets get dropped. For instance, your harcoded 1000 (or
whatever) value means that there are still *lots* of boxes that will
not be able to handle those packets properly, and hence will get
dropped (check the 6man and/or v6ops discussions).

Thanks,
Fernando

From Fred.L.Templin@boeing.com  Wed Oct 16 10:23:10 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B80421F8EC3; Wed, 16 Oct 2013 10:23:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.218
X-Spam-Level: 
X-Spam-Status: No, score=-6.218 tagged_above=-999 required=5 tests=[AWL=-0.219, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xBwNLNuzTfwl; Wed, 16 Oct 2013 10:23:01 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) by ietfa.amsl.com (Postfix) with ESMTP id 5E15A11E8191; Wed, 16 Oct 2013 10:23:01 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9GHN0QA016043; Wed, 16 Oct 2013 10:23:00 -0700
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9GHMxhQ016021 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Wed, 16 Oct 2013 10:22:59 -0700
Received: from XCH-BLV-405.nw.nos.boeing.com (130.247.25.158) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Wed, 16 Oct 2013 10:22:58 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-BLV-405.nw.nos.boeing.com ([169.254.5.227]) with mapi id 14.03.0158.001; Wed, 16 Oct 2013 10:22:58 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Fernando Gont <fgont@si6networks.com>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOypHQebc9KTehbEGO6mhunuAlj5n3j5QA
Date: Wed, 16 Oct 2013 17:22:57 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812F95C@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net>	<5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com>	<52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com> <525DD007.8030100@si6networks.com> <57E5A58E-0DAF-4545-8580-ACDB59475F46@employees.org> <2134F8430051B64F815C691A62D9831812F69E@XCH-BLV-504.nw.nos.boeing.com> <CAFQ9LJ+-4SdUdoku_on0YX9rTHMPBJQ-Yz7e+Rbb_PoFt1+TjA@mail.gmail.com> <2134F8430051B64F815C691A62D9831812F8C5@XCH-BLV-504.nw.nos.boeing.com> <CAFQ9LJJVqV0q-br5wsSCpUgH=M1BXMitohExh7-MQhsWjVABJA@mail.gmail.com>
In-Reply-To: <CAFQ9LJJVqV0q-br5wsSCpUgH=M1BXMitohExh7-MQhsWjVABJA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 16 Oct 2013 17:23:11 -0000

Hi Fernando,

> -----Original Message-----
> From: fgont.si6networks@gmail.com [mailto:fgont.si6networks@gmail.com]
> On Behalf Of Fernando Gont
> Sent: Wednesday, October 16, 2013 10:05 AM
> To: Templin, Fred L
> Cc: Ole Troan; Ronald Bonica; Brian E Carpenter; 6man-
> chairs@tools.ietf.org; Ray Hunter; 6man Mailing List; ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> On Wed, Oct 16, 2013 at 1:54 PM, Templin, Fred L
> <Fred.L.Templin@boeing.com> wrote:
> >> On Wed, Oct 16, 2013 at 12:45 PM, Templin, Fred L
> >> <Fred.L.Templin@boeing.com> wrote:
> >> > I disagree with the header chain terminating as soon as another
> IPv6
> >> > header is encounter. That defeats defense-in-depth, since outer
> >> > perimeter middleboxes would be forced to admit packets with
> >> unexamined
> >> > header chains inward to inner perimeter middleboxes. And, if the
> >> > unexamined header chains contain bad stuff inserted by an
> attacker,
> >> > the attack is successful.
> >>
> >> The same is true if the underlying encapsulation layer is IPv4.
> >
> > We should not default to doing as badly as IPv4.
>=20
> The point is that this is no worse than IPv4. And it is very likely
> that one of underlying encapsulations will be IPv4.

If an underlying encapsulation is IPv4, there is a very good
chance that the IPv4 path MTU is at least 1280. Else, the
underlying link with MTU smaller than 1280 is very likely to
be low speed. That being the case, the middlebox would have to
perform IPv4 reassembly, yes. But, that is truly a corner case,
and only when IPv4 is involved. Again, we should be striving
to do better than IPv4.

> >> Once
> >> you're encapsulating, all bets are off in that respect. You should
> do
> >> defense-in-depth at the tunnel ingress or egress points. Or, if you
> >> wish, a middle-box could reassemble-inspect/filter-re-fragment
> >
> > If an outer perimeter middlebox connects to a 10Gbps link on its
> > outward facing interface and a 64Kbps link on its inward facing
> > interface, then the middlebox can allow a successful DOS attack
> > against its protected domain if it does not look at headers beyond
> > the outermost IPv6 header.
>=20
> Is it me, or there are actually a plethora of attack vectors an
> attacker would use (instead of this one) in such scenario?

Please don't discount this scenario as contrived or unlikely; there
are certainly such low-end data links in real deployments (civil
aviation networks, DoD networks, etc.) that need DOS protection.

> >> Note that no matter what hardcoded limit you enforce, an attacker
> >> willing to evade you're security controls can always add an
> >> extra-layer of encapsulation (assuming he controls that).
> >
> > Yes. With a 1024 limit on the amount of extension headers a
> > host can add, approximately 5-6 encapsulations can be added
> > before the tunnel headers cause the header chain to overflow
> > the IPv6 minMTU.
>=20
> That depends on whether extension headers are employed in different
> layer of encapsulation.

Most tunneling protocols I am aware of do not specify that additional
extension headers can be added (one exception is the Encapsulation Limit
option specified by RFC2473). So, it should be reasonable for a middlebox=20
to drop an encapsulated packet with an unusually long encapsulation
extension header chain inserted by the purported tunnel ingress.=20
=20
> Besides, what's the different between an attacker exceeding your
> hardcoded limit and traffic resulting in tunnling packets failing to
> include the entire header chain?

The hard-coded limit is 5-6 layers of encapsulation headers fitting
within the IPv6 minMTU but that does not stop tunnels from recursing
indefinitely. What it does do is provide a healthy number of layers
of defense in depth.

> As noted off-list, this hard limit becomes a BCP, rather than a std
> update: the larger your extension header chain, the higher the chances
> that your packets get dropped. For instance, your harcoded 1000 (or
> whatever) value means that there are still *lots* of boxes that will
> not be able to handle those packets properly, and hence will get
> dropped (check the 6man and/or v6ops discussions).

That's OK. Let the BCP for hosts be 1024, and I am happy.

Thanks - Fred
fred.l.templin@boeing.com

> Thanks,
> Fernando

From ietf-secretariat-reply@ietf.org  Wed Oct 16 11:29:17 2013
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D935711E8141 for <ipv6@ietfa.amsl.com>; Wed, 16 Oct 2013 11:29:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.344
X-Spam-Level: 
X-Spam-Status: No, score=-101.344 tagged_above=-999 required=5 tests=[AWL=-0.963, BAYES_00=-2.599, NO_RELAYS=-0.001, TVD_SPACE_RATIO=2.219, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5HCtSuqZgdTI; Wed, 16 Oct 2013 11:29:17 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7818911E819D; Wed, 16 Oct 2013 11:29:17 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
To: 6man-chairs@tools.ietf.org, draft-ietf-6man-oversized-header-chain@tools.ietf.org, ipv6@ietf.org
Subject: ID Tracker State Update Notice: <draft-ietf-6man-oversized-header-chain-08.txt>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131016182917.16458.6608.idtracker@ietfa.amsl.com>
Date: Wed, 16 Oct 2013 11:29:17 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 16 Oct 2013 18:29:18 -0000

State changed to Waiting for Writeup::AD Followup from Waiting for Writeup
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-6man-oversized-h=
eader-chain/


From internet-drafts@ietf.org  Wed Oct 16 15:43:34 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7138011E812B; Wed, 16 Oct 2013 15:43:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SxDg0l1qY576; Wed, 16 Oct 2013 15:43:32 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F38621F9946; Wed, 16 Oct 2013 15:43:32 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-ext-transmit-05.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131016224332.4997.24148.idtracker@ietfa.amsl.com>
Date: Wed, 16 Oct 2013 15:43:32 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 16 Oct 2013 22:43:34 -0000

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           : Transmission and Processing of IPv6 Extension Headers
	Author(s)       : Brian Carpenter
                          Sheng Jiang
	Filename        : draft-ietf-6man-ext-transmit-05.txt
	Pages           : 10
	Date            : 2013-10-16

Abstract:
   Various IPv6 extension headers have been standardised since the IPv6
   standard was first published.  This document updates RFC 2460 to
   clarify how intermediate nodes should deal with such extension
   headers and with any that are defined in future.  It also specifies
   how extension headers should be registered by IANA, with a
   corresponding minor update to RFC 2780.


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

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

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


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 internet-drafts@ietf.org  Wed Oct 16 15:43:35 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B01C11E812B for <ipv6@ietfa.amsl.com>; Wed, 16 Oct 2013 15:43:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7mrx2AGkD6ZC; Wed, 16 Oct 2013 15:43:34 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 90A8821F9AE2; Wed, 16 Oct 2013 15:43:33 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: 6man-chairs@tools.ietf.org, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org, brian@innovationslab.net
Subject: New Version Notification - draft-ietf-6man-ext-transmit-05.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131016224333.4997.95040.idtracker@ietfa.amsl.com>
Date: Wed, 16 Oct 2013 15:43:33 -0700
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 16 Oct 2013 22:43:35 -0000

A new version (-05) has been submitted for draft-ietf-6man-ext-transmit:
http://www.ietf.org/internet-drafts/draft-ietf-6man-ext-transmit-05.txt

Sub state has been changed to AD Followup from Revised ID Needed


The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-ext-transmit/

Diff from previous version:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-ext-transmit-05

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.

IETF Secretariat.


From nalini.elkins@insidethestack.com  Wed Oct 16 20:25:20 2013
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7134B11E8159 for <ipv6@ietfa.amsl.com>; Wed, 16 Oct 2013 20:25:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.454
X-Spam-Level: 
X-Spam-Status: No, score=-2.454 tagged_above=-999 required=5 tests=[AWL=0.144,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1izvmvRoyEZO for <ipv6@ietfa.amsl.com>; Wed, 16 Oct 2013 20:25:15 -0700 (PDT)
Received: from nm14-vm2.access.bullet.mail.gq1.yahoo.com (nm14-vm2.access.bullet.mail.gq1.yahoo.com [216.39.63.42]) by ietfa.amsl.com (Postfix) with ESMTP id 26EA011E8220 for <ipv6@ietf.org>; Wed, 16 Oct 2013 20:25:10 -0700 (PDT)
Received: from [216.39.60.175] by nm14.access.bullet.mail.gq1.yahoo.com with NNFMP; 17 Oct 2013 03:25:07 -0000
Received: from [216.39.60.164] by tm11.access.bullet.mail.gq1.yahoo.com with NNFMP; 17 Oct 2013 03:25:07 -0000
Received: from [127.0.0.1] by omp1030.access.mail.gq1.yahoo.com with NNFMP; 17 Oct 2013 03:25:07 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 27982.15738.bm@omp1030.access.mail.gq1.yahoo.com
Received: (qmail 38103 invoked by uid 60001); 17 Oct 2013 03:25:06 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1381980306; bh=mh+oOdKCb2QvARY0zwoNtRPnZbCODjlb33S9+KrICg0=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=nzxBSXhwYbz0s/nMnFUB0m0I1TEgSHOT3gcRyf4zh7mjWp7KFo5TD8hS/vYdpVIVID5VqyyZnZdtnzY4aIKpy5s43NJi1dLFLKasCtm1fRKCtyew0k4uwgKtV0lBnhT9N0AmYwPt2qykrZ5/TBABR2T9KCBigL/7ttlHwaRI88k=
X-YMail-OSG: 1sz_vFYVM1ngcJrIW7V59MZW_xiOO6tZT.SNylU6w7CYKJz 9F7drv1c3ENvQxsGYwfBhqAxOkRKh_pqMBDSeRXrqUUPsw59enSew6ISqzor 5Ca_30y4RB0yw8MoH0LZE4BRESTUNcvIOK2rBEomPNi7ZparDoYpPATPuEci cHMM1tdhOR6Dy1EcLQk0RVTL3EkNk_FdHwUNoMfGb9wgkywvBqzSGezCODvU UMR.A9o8ewqAkbci.JJA_fze7O4JtdHat6wZdr9_EtKQ7OSD0SLxwb1gbOlk .kDW8qv5PTLh_zUKpHll.EJJABj_oXWnPNEvyZOv5AoQFZaUMXIE2jen4TwX ZuInf_NZsn6t2BdJaQ4w3GA3qbhY5wjavDoEu9DpuAdnGhILXJynNvHnjb4f p9TyRS1PY78Z9QiMGuu08dSNjJV00.x9WZ6rp2wLLlYdaftXzJqWz4YiDfRD tWeZoA16uK4kkiue.IYJnNk13htS9GFC0h._MT43w80pgxUG24LDK5Hc50wA uYEJih4PoJSwZ3ubuczlblctvdjcb13RzEmsdM2s8CufkzJ074BWqqAE45ND __iYU8pk86lSMRDKuOk2G40d8pBkecKufNHKnnA6_enl3k8JfNQpW3nMvhv2 SbXqTo4HE0s9_4KD7MdA6Q2xXxX6Df8jBNTqPAJM-
Received: from [24.130.37.147] by web2803.biz.mail.ne1.yahoo.com via HTTP; Wed, 16 Oct 2013 20:25:05 PDT
X-Rocket-MIMEInfo: 002.001, QWxsLAoKSSBoYXZlIHJldmlzZWQgdGhlIDZtYW4gc3VibWlzc2lvbiB0byB0YWtlIG91dCB0aGUgY2FsY3VsYXRpb25zIGFuZCBwYWNrZXQgZmxvd3MuIMKgQWxsIG9mIHRoZXNlIGFyZSBpbiB0aGUgSVBQTSBkb2N1bWVudC4gwqAgQSBub3RhdGlvbiBvZiBhbGwgdGhlIHVzYWdlIGNhc2VzIHRoYXQgdGhpcyBtZXRob2RvbG9neSBzaG91bGQgaGFuZGxlIGhhcyBhbHNvIGJlZW7CoGFkZGVkIHRvIHRoZSBJUFBNIGRyYWZ0LgoKVGhlIElQUE0gZHJhZnQgaXMgaGVyZTrCoGh0dHA6Ly9kYXRhdHJhY2tlci5pZXQBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.160.587
References: <20131017032024.5051.20799.idtracker@ietfa.amsl.com>
Message-ID: <1381980305.36254.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com>
Date: Wed, 16 Oct 2013 20:25:05 -0700 (PDT)
From: Nalini Elkins <nalini.elkins@insidethestack.com>
Subject: Fw: New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-04.txt
To: v6ops WG <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>
In-Reply-To: <20131017032024.5051.20799.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-1551098171-1958070460-1381980305=:36254"
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Nalini Elkins <nalini.elkins@insidethestack.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: Thu, 17 Oct 2013 03:25:20 -0000

---1551098171-1958070460-1381980305=:36254
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

All,=0A=0AI have revised the 6man submission to take out the calculations a=
nd packet flows. =A0All of these are in the IPPM document. =A0 A notation o=
f all the usage cases that this methodology should handle has also been=A0a=
dded to the IPPM draft.=0A=0AThe IPPM draft is here:=A0http://datatracker.i=
etf.org/doc/draft-elkins-ippm-pdm-metrics/=0A=0AThe 6man draft is below.=0A=
=0AI appreciate any thoughts and comments.=0A=0AA new version of I-D, draft=
-elkins-6man-ipv6-pdm-dest-option-04.txt=0Ahas been successfully submitted =
by Nalini Elkins and posted to the=0AIETF repository.=0A=0AFilename:=A0=A0=
=A0  draft-elkins-6man-ipv6-pdm-dest-option=0ARevision:=A0=A0=A0  04=0ATitl=
e:=A0=A0=A0 =A0=A0=A0  IPv6 Performance and Diagnostic Metrics Destination =
Option=0ACreation date:=A0=A0=A0  2013-10-16=0AGroup:=A0=A0=A0 =A0=A0=A0  I=
ndividual Submission=0ANumber of pages: 12=0AURL:=A0 =A0 =A0 =A0 =A0 =A0  h=
ttp://www.ietf.org/internet-drafts/draft-elkins-6man-ipv6-pdm-dest-option-0=
4.txt=0AStatus:=A0 =A0 =A0 =A0 =A0 http://datatracker.ietf.org/doc/draft-el=
kins-6man-ipv6-pdm-dest-option=0AHtmlized:=A0 =A0 =A0 =A0 http://tools.ietf=
.org/html/draft-elkins-6man-ipv6-pdm-dest-option-04=0ADiff:=A0 =A0 =A0 =A0 =
=A0 =A0 http://www.ietf.org/rfcdiff?url2=3Ddraft-elkins-6man-ipv6-pdm-dest-=
option-04=0A=0AAbstract:=0A=A0  To diagnose performance and connectivity pr=
oblems, metrics on real=0A=A0  (non-synthetic) transmission are critical fo=
r timely end-to-end=0A=A0  problem resolution. Such diagnostics may be real=
-time or after the=0A=A0  fact, but must not impact an operational producti=
on network. The base=0A=A0  metrics are: packet sequence number and packet =
timestamp.=A0 Metrics=0A=A0  derived from these will be described separatel=
y. This document solves=0A=A0  these problems with a new destination option=
, the Performance and=0A=A0  Diagnostic Metrics destination option (PDM).=
=0A=0A=0A=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =0A=0A=0APlease note that it may take a couple of =
minutes from the time of submission=0Auntil the htmlized version and diff a=
re available at tools.ietf.org.=0A=0AThe IETF Secretariat
---1551098171-1958070460-1381980305=:36254
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:ar=
ial, helvetica, sans-serif;font-size:12pt"><div><span>All,</span></div><div=
 style=3D"color: rgb(0, 0, 0); font-size: 16px; font-family: arial, helveti=
ca, sans-serif; background-color: transparent; font-style: normal;"><span><=
br></span></div><div style=3D"color: rgb(0, 0, 0); font-size: 16px; font-fa=
mily: arial, helvetica, sans-serif; background-color: transparent; font-sty=
le: normal;"><span>I have revised the 6man submission to take out the calcu=
lations and packet flows. &nbsp;All of these are in the IPPM document. &nbs=
p; A notation of all the usage cases that this methodology should handle ha=
s also been&nbsp;</span><span style=3D"background-color: transparent;">adde=
d to the IPPM draft.</span></div><div></div><div><br></div><div>The IPPM dr=
aft is here:&nbsp;<a href=3D"http://datatracker.ietf.org/doc/draft-elkins-i=
ppm-pdm-metrics/" style=3D"font-family: 'times new roman', 'new york', time=
s,
 serif; font-size: 12pt;">http://datatracker.ietf.org/doc/draft-elkins-ippm=
-pdm-metrics/</a></div><div><br></div><div>The 6man draft is below.</div><d=
iv><br></div><div>I appreciate any thoughts and comments.</div><div style=
=3D"font-family: arial, helvetica, sans-serif; font-size: 12pt;"><div style=
=3D"font-family: 'times new roman', 'new york', times, serif; font-size: 12=
pt;"><div class=3D"y_msg_container">=0A<br>A new version of I-D, draft-elki=
ns-6man-ipv6-pdm-dest-option-04.txt<br>has been successfully submitted by N=
alini Elkins and posted to the<br>IETF repository.<br><br>Filename:&nbsp;&n=
bsp;&nbsp;  draft-elkins-6man-ipv6-pdm-dest-option<br>Revision:&nbsp;&nbsp;=
&nbsp;  04<br>Title:&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;  IPv6 Performance=
 and Diagnostic Metrics Destination Option<br>Creation date:&nbsp;&nbsp;&nb=
sp;  2013-10-16<br>Group:&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;  Individual =
Submission<br>Number of pages: 12<br>URL:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 &nbsp;  http://www.ietf.org/internet-drafts/draft-elkins-6man-ipv6-pdm-des=
t-option-04.txt<br>Status:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; http://datatra=
cker.ietf.org/doc/draft-elkins-6man-ipv6-pdm-dest-option<br>Htmlized:&nbsp;=
 &nbsp; &nbsp; &nbsp; http://tools.ietf.org/html/draft-elkins-6man-ipv6-pdm=
-dest-option-04<br>Diff:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
 http://www.ietf.org/rfcdiff?url2=3Ddraft-elkins-6man-ipv6-pdm-dest-option-=
04<br><br>Abstract:<br>&nbsp;  To diagnose performance and connectivity pro=
blems, metrics on real<br>&nbsp;  (non-synthetic) transmission are critical=
 for timely end-to-end<br>&nbsp;  problem resolution. Such diagnostics may =
be real-time or after the<br>&nbsp;  fact, but must not impact an operation=
al production network. The base<br>&nbsp;  metrics are: packet sequence num=
ber and packet timestamp.&nbsp; Metrics<br>&nbsp;  derived from these will =
be described separately. This document solves<br>&nbsp;  these problems wit=
h a new destination option, the Performance and<br>&nbsp;  Diagnostic Metri=
cs destination option (PDM).<br><br><br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br><br><br>Please note that it may tak=
e a couple of minutes from the time of submission<br>until the htmlized ver=
sion and diff are available at <a target=3D"_blank" href=3D"http://tools.ie=
tf.org/">tools.ietf.org</a>.<br><br>The IETF Secretariat<br><br><br><br></d=
iv> </div> </div>  </div></body></html>
---1551098171-1958070460-1381980305=:36254--

From internet-drafts@ietf.org  Wed Oct 16 23:10:56 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1D1711E80FE; Wed, 16 Oct 2013 23:10:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4qNK8USfrKDz; Wed, 16 Oct 2013 23:10:56 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0014711E81A1; Wed, 16 Oct 2013 23:10:55 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-ipv6-address-generation-privacy-00.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131017061055.4875.17634.idtracker@ietfa.amsl.com>
Date: Wed, 16 Oct 2013 23:10:55 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Oct 2013 06:10:57 -0000

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           : Privacy Considerations for IPv6 Address Generation Mecha=
nisms
	Author(s)       : Alissa Cooper
                          Fernando Gont
                          Dave Thaler
	Filename        : draft-ietf-6man-ipv6-address-generation-privacy-00.txt
	Pages           : 15
	Date            : 2013-10-16

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-pr=
ivacy

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


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 bob.hinden@gmail.com  Thu Oct 17 05:41:21 2013
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F23D121F994A for <ipv6@ietfa.amsl.com>; Thu, 17 Oct 2013 05:41:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lhsdebwkWJ4p for <ipv6@ietfa.amsl.com>; Thu, 17 Oct 2013 05:41:18 -0700 (PDT)
Received: from mail-ye0-x235.google.com (mail-ye0-x235.google.com [IPv6:2607:f8b0:4002:c04::235]) by ietfa.amsl.com (Postfix) with ESMTP id 6E42A11E81B1 for <ipv6@ietf.org>; Thu, 17 Oct 2013 05:41:18 -0700 (PDT)
Received: by mail-ye0-f181.google.com with SMTP id q4so480511yen.26 for <ipv6@ietf.org>; Thu, 17 Oct 2013 05:41:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:date:cc :content-transfer-encoding:message-id:references:to; bh=wKgZar+DaPUw1krzhrhXMGJcp4Pq2CnJl5aQJrMPPXg=; b=ojNm8CMSnJ5VQ+FoJ7ElzeCTArJeUNeSHe+rYq9dWI3DZK/aq560ysGoadxZ68FklG y+VhtQb0zOJonzonwvJJYhfi4aLCjnc2WWWBVwuv2FRQpjweJF0ypQujj5G9GGlcIyac aOUqMRpn5qOfu5py4Mld5G+QC0MGq2qk/TLju4hybXgtvFzXNVRBmvMi6Qv44Y3cBbiA yEC0ByT/g9a8x56zZAZ9WU029uAJBVuLktLqNn2XB4CtonAzql2hHkg9iN09hKYl1Q0W 0H8/2VF2Y8G3eDLHek1GKp1hL/+RGy4DldeHKFrHRimLdFA4gMOnuqTyh+7wRFkKo7+o f+kg==
X-Received: by 10.236.63.225 with SMTP id a61mr6635048yhd.52.1382013677945; Thu, 17 Oct 2013 05:41:17 -0700 (PDT)
Received: from [172.24.250.135] (dyn32-131.checkpoint.com. [194.29.32.131]) by mx.google.com with ESMTPSA id t31sm128321383yhp.13.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Oct 2013 05:41:15 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Fwd: Publication has been requested for draft draft-ietf-6man-stable-privacy-addresses
From: Bob Hinden <bob.hinden@gmail.com>
Date: Thu, 17 Oct 2013 15:41:11 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <455406D7-8EB5-4E53-96E1-754D2485A1EC@gmail.com>
References: <20131017124007.21859.69876.idtracker@ietfa.amsl.com>
To: IPv6 List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.1510)
Cc: Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Oct 2013 12:41:21 -0000

FYI

Begin forwarded message:

> From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
> Subject: Publication has been requested for draft =
draft-ietf-6man-stable-privacy-addresses
> Date: October 17, 2013 3:40:07 PM GMT+03:00
> To: "IESG Secretary" <iesg-secretary@ietf.org>, "Brian Haberman" =
<brian@innovationslab.net>
> Cc: "Robert Hinden" <bob.hinden@gmail.com>, "Ole Troan" =
<otroan@employees.org>
>=20
>=20
> The state of document draft-ietf-6man-stable-privacy-addresses has =
been updated. See more information below.
>=20
> Previous state: WG Consensus: Waiting for Write-Up
> Current state: Submitted to IESG for Publication
> Transition date: 2013-10-17 05:40
> Author of the change: Robert Hinden
>=20
> Comment:
>=20
>=20


From pthubert@cisco.com  Thu Oct 17 05:58:31 2013
Return-Path: <pthubert@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70FD311E8242 for <ipv6@ietfa.amsl.com>; Thu, 17 Oct 2013 05:58:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.495
X-Spam-Level: 
X-Spam-Status: No, score=-10.495 tagged_above=-999 required=5 tests=[AWL=0.104, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hhkGLi42nh6r for <ipv6@ietfa.amsl.com>; Thu, 17 Oct 2013 05:58:24 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 83BF111E81BC for <6man@ietf.org>; Thu, 17 Oct 2013 05:57:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3516; q=dns/txt; s=iport; t=1382014652; x=1383224252; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=mOJ1x87SmPAGppZO/EMGddxFq5nW3Ec5Nq5sG2tzE2o=; b=bhMt/rtgo6Ru1XvxRrO5lh//vyadxdM7zgWFbSJFT0uiuLBQcuxBtmkE h9WGUshqsUgVQfbPrPxHsANl4Y8/NRalThyRPf/PCN7nPskXiT+605ham eU1KUPntvuv0s/bkyFqpotYSk4FqmFDqHHbWUDFshiOvBSnvJAdPupEuf Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiIGAHHdX1KtJV2b/2dsb2JhbABagwc4UoMpulkYgQoWbQeCJQEBAQQjEUMCDAQCAQgRBAEBAwIGHQMCAgIwFAEGAQEFAwIEDgUIAYd9DK1Xkk6BKY13MQcGgmQ1gQcDlCeFDpBVgySCKQ
X-IronPort-AV: E=Sophos;i="4.93,514,1378857600"; d="scan'208";a="273257798"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-8.cisco.com with ESMTP; 17 Oct 2013 12:57:21 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r9HCvLXF019385 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 17 Oct 2013 12:57:21 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.2]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.02.0318.004; Thu, 17 Oct 2013 07:57:20 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "6man@ietf.org" <6man@ietf.org>
Subject: FW: New Version Notification for draft-thubert-6man-wind-sail-00.txt
Thread-Topic: New Version Notification for draft-thubert-6man-wind-sail-00.txt
Thread-Index: AQHOyzb/tYKXAYgTyk+bHF6rAp3Bmpn415/A
Date: Thu, 17 Oct 2013 12:57:19 +0000
Deferred-Delivery: Thu, 17 Oct 2013 12:57:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD84151959E@xmb-rcd-x01.cisco.com>
References: <20131017124659.21823.57455.idtracker@ietfa.amsl.com>
In-Reply-To: <20131017124659.21823.57455.idtracker@ietfa.amsl.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.25]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, "Eric Levy- Abegnoli \(elevyabe\)" <elevyabe@cisco.com>, "Erik Nordmark \(nordmark@sonic.net\)" <nordmark@sonic.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Oct 2013 12:58:31 -0000

RGVhciA2TUFOZXJzOg0KDQpTQUlMIGlzIGEgY29tcGxlbWVudCB0byB0aGUgU0FWSSBhbmQgV2lO
RCB3b3JrLiBTQUlMIGV4dGVuZHMgdGhlIERBUi9EQUMgYmFzZWQgREFEIHByb2Nlc3MgaW4gUkZD
IDY3NzUgYW5kIGRpc3RyaWJ1dGVzIE5EIHJlbGF0ZWQgc3RhdGUgaW4gYSBtYXBwaW5nIHN5c3Rl
bSBpbnNpZGUgdGhlIChtdWx0aWxpbmspIHN1Ym5ldC4gVGhlIG1hcHBpbmcgc3lzdGVtIGVuYWJs
ZXMgdG8gcXVlcnkgd2hlcmUgYSBnaXZlbiBJUHY2IGlzIGxvY2F0ZWQgaW4gdGhlIHN1Ym5ldCwg
YXMgd2VsbCBhcyByZXNvbHZlIE1BQyBsYXllciBhZGRyZXNzIGFuZCBvdGhlciBpbmZvcm1hdGlv
biwgd2l0aG91dCB0aGUgbmVlZCBvZiBhIG11bHRpY2FzdCBvcGVyYXRpb24uIFRoZSBzeXN0ZW0g
Y2FuIGJlIGZlZCBieSBjbGFzc2ljYWwgU0FWSSBzdHlsZSBzbm9vcGluZy4gQnV0IHByZWZlcmFi
bHkgaXQgaXMgZmVkIGJ5IGEgcmVnaXN0cmF0aW9uIG1lY2hhbmlzbSBzdWNoIGFzIFJGQyA2Nzc1
LCBXaU5ELCBvciByZWRpc3RyaWJ1dGVkIFJQTCBmcm9tIHRoZSBlZGdlIG9mIHRoZSBtdWx0aWxp
bmsgc3VibmV0Lg0KDQpUaGUgZHJhZnQgaW4gaXRzIGVhcmx5IHZlcnNpb24gaXMgbW9zdGx5IGFi
b3V0IHBvc2l0aW9uaW5nIHZzLiBleGlzdGluZyB3b3JrIGFuZCB0cnlpbmcgdG8gZGVyaXZlIGEg
Y29tbW9uIGFic3RyYWN0aW9uLiBUaGVuIHdlIHByb3Bvc2UgZXh0ZW5zaW9ucyBiYXNlZCBvbiBS
RkMgNjc3NSBEQVIvREFDIHRoYXQgZmVlZHMgdGhlIG1hcHBpbmcgc3lzdGVtLiBUaGUgb3ZlcmFs
bCBpZGVhIGlzIHRvIHJlbGlldmUgdGhlIGJhY2tib25lIGZyb20gYXMgbXVjaCBsaW5rIGxheWVy
IG11bHRpY2FzdCBhcyB3ZSBjYW4gYW5kIHlldCBtYWludGFpbiBhIGtub3dsZWRnZSBvZiB0aGUg
bG9jYXRpb24gb2YgbW9iaWxlIGRldmljZXMgaW4gYW4gZXh0cmVtZWx5IHNjYWxhYmxlIGZhc2hp
b24uDQoNCk1vcmUgaW4gdGhlIGRyYWZ0Li4uDQoNClBhc2NhbA0KDQoNCi0tLS0tT3JpZ2luYWwg
TWVzc2FnZS0tLS0tDQpGcm9tOiBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcgW21haWx0bzppbnRl
cm5ldC1kcmFmdHNAaWV0Zi5vcmddIA0KU2VudDogamV1ZGkgMTcgb2N0b2JyZSAyMDEzIDE0OjQ3
DQpUbzogUGFzY2FsIFRodWJlcnQgKHB0aHViZXJ0KTsgRXJpYyBMZXZ5LSBBYmVnbm9saSAoZWxl
dnlhYmUpDQpTdWJqZWN0OiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIGRyYWZ0LXRodWJl
cnQtNm1hbi13aW5kLXNhaWwtMDAudHh0DQoNCg0KQSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0
LXRodWJlcnQtNm1hbi13aW5kLXNhaWwtMDAudHh0DQpoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3Vi
bWl0dGVkIGJ5IFBhc2NhbCBUaHViZXJ0IGFuZCBwb3N0ZWQgdG8gdGhlIElFVEYgcmVwb3NpdG9y
eS4NCg0KRmlsZW5hbWU6CSBkcmFmdC10aHViZXJ0LTZtYW4td2luZC1zYWlsDQpSZXZpc2lvbjoJ
IDAwDQpUaXRsZToJCSBXaXJlbGVzcyBOZWlnaGJvciBEaXNjb3ZlcnkgU3RhdGVmdWwgQWRkcmVz
cyBJZGVudGlmaWNhdGlvbiBhbmQgTG9jYXRpb24gZXhjaGFuZ2UNCkNyZWF0aW9uIGRhdGU6CSAy
MDEzLTEwLTE3DQpHcm91cDoJCSBJbmRpdmlkdWFsIFN1Ym1pc3Npb24NCk51bWJlciBvZiBwYWdl
czogMjENClVSTDogICAgICAgICAgICAgaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFm
dHMvZHJhZnQtdGh1YmVydC02bWFuLXdpbmQtc2FpbC0wMC50eHQNClN0YXR1czogICAgICAgICAg
aHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC10aHViZXJ0LTZtYW4td2luZC1z
YWlsDQpIdG1saXplZDogICAgICAgIGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LXRo
dWJlcnQtNm1hbi13aW5kLXNhaWwtMDANCg0KDQpBYnN0cmFjdDoNCiAgIFRoaXMgZHJhZnQgcHJv
cG9zZXMgYW4gZXh0ZW5zaW9uIHRvIElQdjYgTmVpZ2hib3IgRGlzY292ZXJ5IHRvDQogICBleGNo
YW5nZSBTdGF0ZWZ1bCBBZGRyZXNzIElkZW50aWZpY2F0aW9uIGFuZCBMb2NhdGlvbiBiZXR3ZWVu
IFN0YXRlDQogICBNYWludGFpbmluZyBFbnRpdGllcyBsb2NhdGVkIG92ZXIgYSBiYWNrYm9uZSBs
aW5rIGFib3V0IGF0dGFjaGVkDQogICBub2RlcyB0aGF0IGFyZSBhdHRhY2hlZCB0byB0aGUgYmFj
a2JvbmUgdmlhIGEgV2lyZWxlc3MgTGluaywgaW4gb3JkZXINCiAgIHRvIG1haW50YWluIGFsbCB0
aGUgZW50aXRpZXMgdXAtdG8tZGF0ZSBhbmQgbWFpbnRhaW4gcmVhY2hhYmlsaXR5IGFzDQogICB0
aGUgYXR0YWNoZWQgbm9kZXMgbW92ZS4NCg0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KDQoN
ClBsZWFzZSBub3RlIHRoYXQgaXQgbWF5IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRo
ZSB0aW1lIG9mIHN1Ym1pc3Npb24gdW50aWwgdGhlIGh0bWxpemVkIHZlcnNpb24gYW5kIGRpZmYg
YXJlIGF2YWlsYWJsZSBhdCB0b29scy5pZXRmLm9yZy4NCg0KVGhlIElFVEYgU2VjcmV0YXJpYXQN
Cg0K

From ietf-secretariat-reply@ietf.org  Thu Oct 17 06:00:54 2013
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 525A721F9B0D for <ipv6@ietfa.amsl.com>; Thu, 17 Oct 2013 06:00:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.35
X-Spam-Level: 
X-Spam-Status: No, score=-101.35 tagged_above=-999 required=5 tests=[AWL=-0.969, BAYES_00=-2.599, NO_RELAYS=-0.001, TVD_SPACE_RATIO=2.219, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6TKGV9pcDe9B; Thu, 17 Oct 2013 06:00:53 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DCA3011E81C0; Thu, 17 Oct 2013 06:00:43 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
To: 6man-chairs@tools.ietf.org, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org
Subject: ID Tracker State Update Notice: <draft-ietf-6man-ext-transmit-05.txt>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131017130043.21877.24463.idtracker@ietfa.amsl.com>
Date: Thu, 17 Oct 2013 06:00:43 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Oct 2013 13:00:54 -0000

State changed to Approved-announcement to be sent from IESG Evaluation::AD =
Followup
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-6man-ext-transmi=
t/


From ietf-secretariat-reply@ietf.org  Thu Oct 17 06:01:59 2013
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09CA711E8249 for <ipv6@ietfa.amsl.com>; Thu, 17 Oct 2013 06:01:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.46
X-Spam-Level: 
X-Spam-Status: No, score=-102.46 tagged_above=-999 required=5 tests=[AWL=0.140, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8FU6wDHZV8ON; Thu, 17 Oct 2013 06:01:58 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E0F3021F9B0D; Thu, 17 Oct 2013 06:01:44 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
To: 6man-chairs@tools.ietf.org, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org
Subject: ID Tracker State Update Notice: <draft-ietf-6man-ext-transmit-05.txt>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131017130144.21841.36886.idtracker@ietfa.amsl.com>
Date: Thu, 17 Oct 2013 06:01:44 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Oct 2013 13:01:59 -0000

IESG has approved the document and state has been changed to Approved-annou=
ncement sent
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-6man-ext-transmi=
t/


From iesg-secretary@ietf.org  Thu Oct 17 06:02:23 2013
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7108411E81BC; Thu, 17 Oct 2013 06:02:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.446
X-Spam-Level: 
X-Spam-Status: No, score=-102.446 tagged_above=-999 required=5 tests=[AWL=0.154, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iDzXIHDxjcZN; Thu, 17 Oct 2013 06:02:14 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DA7111E81CD; Thu, 17 Oct 2013 06:01:45 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'Transmission and Processing of IPv6 Extension Headers' to Proposed Standard (draft-ietf-6man-ext-transmit-05.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131017130145.21841.55303.idtracker@ietfa.amsl.com>
Date: Thu, 17 Oct 2013 06:01:45 -0700
Cc: 6man chair <6man-chairs@tools.ietf.org>, 6man mailing list <ipv6@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Oct 2013 13:02:23 -0000

The IESG has approved the following document:
- 'Transmission and Processing of IPv6 Extension Headers'
  (draft-ietf-6man-ext-transmit-05.txt) as Proposed Standard

This document is the product of the IPv6 Maintenance Working Group.

The IESG contact persons are Brian Haberman and Ted Lemon.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-6man-ext-transmit/




Technical Summary:

  This document updates RFC 2460 to clarify how intermediate nodes should
  deal with such extension headers and with any that are defined in
  future.  It also specifies how extension headers should be registered
  by IANA, with a corresponding minor update to RFC 2780.

Working Group Summary:

Was there anything in WG process that is worth noting? For example,
was there controversy about particular points or were there decisions
where the consensus was particularly rough?

  No.

Document Quality:

  There was a good discussion in the working group and well as a detailed
  review by Fernando Gont.  The current draft resolves issues raised in
  the w.g. last call and detailed review.  

Personnel:

  Bob Hinden is the Document Shepherd. 
  Brian Haberman is the Responsible Area Director.

From Fred.L.Templin@boeing.com  Thu Oct 17 06:44:20 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2190621F93E4; Thu, 17 Oct 2013 06:44:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.51
X-Spam-Level: 
X-Spam-Status: No, score=-6.51 tagged_above=-999 required=5 tests=[AWL=0.089,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6nOgeNDZUx4x; Thu, 17 Oct 2013 06:44:13 -0700 (PDT)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) by ietfa.amsl.com (Postfix) with ESMTP id 9B96921F88BA; Thu, 17 Oct 2013 06:44:13 -0700 (PDT)
Received: from blv-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9HDiCj9022493; Thu, 17 Oct 2013 06:44:13 -0700
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9HDiB5o022485 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Thu, 17 Oct 2013 06:44:11 -0700
Received: from XCH-EXCO-102.nw.nos.boeing.com (130.247.25.34) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Thu, 17 Oct 2013 06:44:11 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-EXCO-102.nw.nos.boeing.com ([fe80::452:98ce:3aa6:3fe9%15]) with mapi id 14.03.0158.001; Thu, 17 Oct 2013 06:44:10 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Fernando Gont <fgont@si6networks.com>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOypHQJAvRrWBwLEyOc1cqWuOOX5n3j5QAgAFTCZA=
Date: Thu, 17 Oct 2013 13:44:09 +0000
Message-ID: <2134F8430051B64F815C691A62D98318131522@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net>	<5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com>	<52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com> <525DD007.8030100@si6networks.com> <57E5A58E-0DAF-4545-8580-ACDB59475F46@employees.org> <2134F8430051B64F815C691A62D9831812F69E@XCH-BLV-504.nw.nos.boeing.com> <CAFQ9LJ+-4SdUdoku_on0YX9rTHMPBJQ-Yz7e+Rbb_PoFt1+TjA@mail.gmail.com> <2134F8430051B64F815C691A62D9831812F8C5@XCH-BLV-504.nw.nos.boeing.com> <CAFQ9LJJVqV0q-br5wsSCpUgH=M1BXMitohExh7-MQhsWjVABJA@mail.gmail.com> <2134F8430051B64F815C691A62D9831812F95C@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831812F95C@XCH-BLV-504.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Ray Hunter <v6ops@globis.net>, 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Oct 2013 13:44:20 -0000

Hi Fernando,

I want to revisit a point that needs to be corrected:

> The point is that this is no worse than IPv4.

Why should it be as bad as IPv4 when it can be better? IPv4
middleboxes that wish to do deep packet inspection may need to
gather the fragments of a fragmented datagram before deciding
whether to let them pass through. IPv6 middleboxes shouldn't
have to do that, but they will if the host is permitted to
include MTU-sized header chains and there is a tunnel on the
path that has to fragment for whatever reason.

> And it is very likely
> that one of underlying encapsulations will be IPv4.

That is not necessarily true. Tunnels are used for many reasons
other than IPv6/IPv4 transition, including routing control,
mobility, traffic engineering, multihoming, security etc.
Tunnels will be part of the IPv6 architecture long after IPv4
has faded into the sunset, so let's get this right now so we
don't have to live with legacy behavior.

Thanks - Fred
fred.l.templin@boeing.com



From rdroms.ietf@gmail.com  Thu Oct 17 09:11:01 2013
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0723521F9C4A; Thu, 17 Oct 2013 09:11:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FsKPznzRxXMw; Thu, 17 Oct 2013 09:11:00 -0700 (PDT)
Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 8478321F9A61; Thu, 17 Oct 2013 09:10:55 -0700 (PDT)
Received: by mail-pa0-f44.google.com with SMTP id fb1so1019392pad.31 for <multiple recipients>; Thu, 17 Oct 2013 09:10:55 -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 :content-transfer-encoding:message-id:references:to; bh=QycdZMbsWrKXKVMc2LTsHhAMtORtYHVk5lpladNznsI=; b=bB+Wkk1wr+gyhB98ADdO14CZNDD0F1m7IwjPv3P8v2Brr6hT3SxxlH3VfWqvpjqZKK R0yI4sTMUXjcdjeQPgKNwOPJlERPD+Kr2nFR6KrguFntcoSQIxzxeTkByqGhoYwWI2vb Rbrzigs5XWuu6r4AZLebn3gfryPyGrBDcLnvbXhGAECLpFSP82Lqj5LjTCgvGQeOQN6Q a1L/n4jA8lvIEj/Wra4JMscs8e+LKdR6nvq3fyGhuJBa1vQw5wS9xlWSL4P5E2KPj3yP YwT71MwzCPvPryLwxz+BmGpDDCx6DZiI19xX/MvejaaG1cfwpRQNrgV//04LQAal02Jn RAMA==
X-Received: by 10.68.172.36 with SMTP id az4mr9449936pbc.48.1382026254983; Thu, 17 Oct 2013 09:10:54 -0700 (PDT)
Received: from [10.154.37.65] (128-107-239-234.cisco.com. [128.107.239.234]) by mx.google.com with ESMTPSA id qw8sm98747783pbb.27.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Oct 2013 09:10:51 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re: [Roll] [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope value of 3 - subnet-local)
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <CABOxzu0L-EY0iDGpAJ+ER15CPL-3v8F77ewn-G=gZYODixevZg@mail.gmail.com>
Date: Thu, 17 Oct 2013 09:10:50 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <3CC8783F-F4DA-47B9-A051-DBBA6EF00C19@gmail.com>
References: <3599.1381852752@sandelman.ca> <CE82BA46.24343%d.sturek@att.net> <CABOxzu2nLuny5uySEEdb6ji9ucE6xqGZ6DLe-mc6KUqVszNfFg@mail.gmail.com> <525DC6C9.2010808@gridmerge.com> <CABOxzu2apwBRpU1h4mKJwpO+U+Y9Q_q-h5AhZ+hGzAdjdPdmUQ@mail.gmail.com> <525E5064.4050109@gridmerge.com> <CABOxzu0L-EY0iDGpAJ+ER15CPL-3v8F77ewn-G=gZYODixevZg@mail.gmail.com>
To: "6man@ietf.org" <6man@ietf.org>
X-Mailer: Apple Mail (2.1510)
Cc: Routing Over Low power and Lossy networks <roll@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Oct 2013 16:11:01 -0000

Kerry correctly points out that RFC 4007 and RFC 4291 are in conflict =
regarding the way in which multicast scope 3 is defined:

RFC 4007, section 5:

   o  The boundaries of zones of a scope other than interface-local,
      link-local, and global must be defined and configured by network
      administrators.

RFC 4291, section 2.7:

         Admin-Local scope is the smallest scope that must be
         administratively configured, i.e., not automatically derived
         from physical connectivity or other, non-multicast-related
         configuration.

Noting this conflict, I propose adding a bit of text to =
draft-ietf-6man-multicast-scopes to update RFC 4007 for consistency with =
RFC 4291:

Add section 3 (and renumber current section 3-5):

3.  Updates to RFC 4007, section 5

   Section 5 of RFC 4007 and section 2.7 of RFC 4291 disagree about the
   way in which multicast scope 3 is configured.  To resolve that =
disagreement,
   change the last bullet in the list in section 5 of RFC 4007 as =
follows:

OLD:

   o  The boundaries of zones of a scope other than interface-local,
      link-local, and global must be defined and configured by network
      administrators.

NEW:

   o  Admin-Local scope is the smallest scope that must be
      administratively configured, i.e., not automatically derived
      from physical connectivity or other, non-multicast-related
      configuration.

Looking for consensus in the 6man WG before I make this change...

- Ralph

On Oct 16, 2013, at 10:04 AM 10/16/13, Kerry Lynn <kerlyn@ieee.org> =
wrote:

> [...]

> I think Ralph's approach is the correct one.  His =
draft-droms-6man-multicast-scopes belongs in
> 6man as it re-defines a reserved code point in the IPv6 addressing =
architecture.  It nominally
> updates RFC 4291 but should probably also update RFC 4007 as these =
RFCs are in conflict
> regarding the automatic definition of scope 0x03.
[...]


From kerlyn2001@gmail.com  Thu Oct 17 09:16:44 2013
Return-Path: <kerlyn2001@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0817711E825D; Thu, 17 Oct 2013 09:16:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UnBzs2Kz6Bcu; Thu, 17 Oct 2013 09:16:43 -0700 (PDT)
Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com [IPv6:2a00:1450:400c:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id 489ED11E8271; Thu, 17 Oct 2013 09:16:39 -0700 (PDT)
Received: by mail-wg0-f54.google.com with SMTP id c11so2594439wgh.9 for <multiple recipients>; Thu, 17 Oct 2013 09:16:37 -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=3m6QM95Y58yuqeOqhvhP2HX72L7Ku2fd+vuM74irvOg=; b=NOsj4d0ELoDKRGIuUSYQ7lmuy9uWf61D+kX//zUmIdRX2llO0jnI/5mXaHiR3K7jMI qlqkRA1B+pZq1mGx5UUfvKCjwJhV8gkq5oHporzBvLMKc98NNOIA8s9GA1vMYwPSP/06 JkD7+yVmrJsK0t8+Cmrm+fg4XquyjVZiHOZvUvn9JxqYpGU+dJXMvuMKmzwcmhTO2XZT lbQaFavIZKKgipXT4juwKVKFJptkJPO1pIhz5UOJfrGjbGhl55uRobzhqoWqppjXXI/E JF3xTWuJurE8CndCCEq1UDi5508G85Zst16lkGyERDIDSsiOTixTgENidljhyZsylVno l/sw==
MIME-Version: 1.0
X-Received: by 10.180.182.15 with SMTP id ea15mr29921654wic.16.1382026597536;  Thu, 17 Oct 2013 09:16:37 -0700 (PDT)
Sender: kerlyn2001@gmail.com
Received: by 10.216.227.132 with HTTP; Thu, 17 Oct 2013 09:16:37 -0700 (PDT)
In-Reply-To: <3CC8783F-F4DA-47B9-A051-DBBA6EF00C19@gmail.com>
References: <3599.1381852752@sandelman.ca> <CE82BA46.24343%d.sturek@att.net> <CABOxzu2nLuny5uySEEdb6ji9ucE6xqGZ6DLe-mc6KUqVszNfFg@mail.gmail.com> <525DC6C9.2010808@gridmerge.com> <CABOxzu2apwBRpU1h4mKJwpO+U+Y9Q_q-h5AhZ+hGzAdjdPdmUQ@mail.gmail.com> <525E5064.4050109@gridmerge.com> <CABOxzu0L-EY0iDGpAJ+ER15CPL-3v8F77ewn-G=gZYODixevZg@mail.gmail.com> <3CC8783F-F4DA-47B9-A051-DBBA6EF00C19@gmail.com>
Date: Thu, 17 Oct 2013 12:16:37 -0400
X-Google-Sender-Auth: _d8c8iiXon2bZ9RiaS8uIK7F4Xw
Message-ID: <CABOxzu1VMw3EkCCkXRU4h=obSKbO8JSXfS+_NJ-S-vV3bkuP+g@mail.gmail.com>
Subject: Re: [Roll] draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re: [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope value of 3 - subnet-local)
From: Kerry Lynn <kerlyn@ieee.org>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b62535a6a98d504e8f2243a
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Oct 2013 16:16:44 -0000

--047d7b62535a6a98d504e8f2243a
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Oct 17, 2013 at 12:10 PM, Ralph Droms <rdroms.ietf@gmail.com> wrote:

> Kerry correctly points out that RFC 4007 and RFC 4291 are in conflict
> regarding the way in which multicast scope 3 is defined:
>
> RFC 4007, section 5:
>
>    o  The boundaries of zones of a scope other than interface-local,
>       link-local, and global must be defined and configured by network
>       administrators.
>
> RFC 4291, section 2.7:
>
>          Admin-Local scope is the smallest scope that must be
>          administratively configured, i.e., not automatically derived
>          from physical connectivity or other, non-multicast-related
>          configuration.
>
> Noting this conflict, I propose adding a bit of text to
> draft-ietf-6man-multicast-scopes to update RFC 4007 for consistency with
> RFC 4291:
>
> Add section 3 (and renumber current section 3-5):
>
> 3.  Updates to RFC 4007, section 5
>
>    Section 5 of RFC 4007 and section 2.7 of RFC 4291 disagree about the
>    way in which multicast scope 3 is configured.  To resolve that
> disagreement,
>    change the last bullet in the list in section 5 of RFC 4007 as follows:
>
> OLD:
>
>    o  The boundaries of zones of a scope other than interface-local,
>       link-local, and global must be defined and configured by network
>       administrators.
>
> NEW:
>
>    o  Admin-Local scope is the smallest scope that must be
>       administratively configured, i.e., not automatically derived
>       from physical connectivity or other, non-multicast-related
>       configuration.
>
> Looking for consensus in the 6man WG before I make this change...
>
> +1

-K-


> - Ralph
>
> On Oct 16, 2013, at 10:04 AM 10/16/13, Kerry Lynn <kerlyn@ieee.org> wrote:
>
> > [...]
>
> > I think Ralph's approach is the correct one.  His
> draft-droms-6man-multicast-scopes belongs in
> > 6man as it re-defines a reserved code point in the IPv6 addressing
> architecture.  It nominally
> > updates RFC 4291 but should probably also update RFC 4007 as these RFCs
> are in conflict
> > regarding the automatic definition of scope 0x03.
> [...]
>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>

--047d7b62535a6a98d504e8f2243a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Thu, Oct 17, 2013 at 12:10 PM, Ralph Droms <span dir=3D=
"ltr">&lt;<a href=3D"mailto:rdroms.ietf@gmail.com" target=3D"_blank">rdroms=
.ietf@gmail.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div cl=
ass=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Kerry correctly points out that RFC 4007 and=
 RFC 4291 are in conflict regarding the way in which multicast scope 3 is d=
efined:<br>

<br>
RFC 4007, section 5:<br>
<br>
=A0 =A0o =A0The boundaries of zones of a scope other than interface-local,<=
br>
=A0 =A0 =A0 link-local, and global must be defined and configured by networ=
k<br>
=A0 =A0 =A0 administrators.<br>
<br>
RFC 4291, section 2.7:<br>
<br>
=A0 =A0 =A0 =A0 =A0Admin-Local scope is the smallest scope that must be<br>
=A0 =A0 =A0 =A0 =A0administratively configured, i.e., not automatically der=
ived<br>
=A0 =A0 =A0 =A0 =A0from physical connectivity or other, non-multicast-relat=
ed<br>
=A0 =A0 =A0 =A0 =A0configuration.<br>
<br>
Noting this conflict, I propose adding a bit of text to draft-ietf-6man-mul=
ticast-scopes to update RFC 4007 for consistency with RFC 4291:<br>
<br>
Add section 3 (and renumber current section 3-5):<br>
<br>
3. =A0Updates to RFC 4007, section 5<br>
<br>
=A0 =A0Section 5 of RFC 4007 and section 2.7 of RFC 4291 disagree about the=
<br>
=A0 =A0way in which multicast scope 3 is configured. =A0To resolve that dis=
agreement,<br>
=A0 =A0change the last bullet in the list in section 5 of RFC 4007 as follo=
ws:<br>
<br>
OLD:<br>
<br>
=A0 =A0o =A0The boundaries of zones of a scope other than interface-local,<=
br>
=A0 =A0 =A0 link-local, and global must be defined and configured by networ=
k<br>
=A0 =A0 =A0 administrators.<br>
<br>
NEW:<br>
<br>
=A0 =A0o =A0Admin-Local scope is the smallest scope that must be<br>
=A0 =A0 =A0 administratively configured, i.e., not automatically derived<br=
>
=A0 =A0 =A0 from physical connectivity or other, non-multicast-related<br>
=A0 =A0 =A0 configuration.<br>
<br>
Looking for consensus in the 6man WG before I make this change...<br>
<br></blockquote><div>+1<br><br></div><div>-K-<br>=A0<br></div><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex">
- Ralph<br>
<br>
On Oct 16, 2013, at 10:04 AM 10/16/13, Kerry Lynn &lt;<a href=3D"mailto:ker=
lyn@ieee.org">kerlyn@ieee.org</a>&gt; wrote:<br>
<br>
&gt; [...]<br>
<br>
&gt; I think Ralph&#39;s approach is the correct one. =A0His draft-droms-6m=
an-multicast-scopes belongs in<br>
&gt; 6man as it re-defines a reserved code point in the IPv6 addressing arc=
hitecture. =A0It nominally<br>
&gt; updates RFC 4291 but should probably also update RFC 4007 as these RFC=
s are in conflict<br>
&gt; regarding the automatic definition of scope 0x03.<br>
[...]<br>
<br>
_______________________________________________<br>
Roll mailing list<br>
<a href=3D"mailto:Roll@ietf.org">Roll@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/roll" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/roll</a><br>
</blockquote></div><br></div></div>

--047d7b62535a6a98d504e8f2243a--

From Fred.L.Templin@boeing.com  Thu Oct 17 14:30:41 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FC8911E8192 for <ipv6@ietfa.amsl.com>; Thu, 17 Oct 2013 14:30:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.513
X-Spam-Level: 
X-Spam-Status: No, score=-6.513 tagged_above=-999 required=5 tests=[AWL=0.086,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f-yp2FDE26PR for <ipv6@ietfa.amsl.com>; Thu, 17 Oct 2013 14:30:32 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) by ietfa.amsl.com (Postfix) with ESMTP id B8ACF21F99F8 for <ipv6@ietf.org>; Thu, 17 Oct 2013 14:30:32 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9HLUWkj027115 for <ipv6@ietf.org>; Thu, 17 Oct 2013 14:30:32 -0700
Received: from XCH-PHX-211.sw.nos.boeing.com (xch-phx-211.sw.nos.boeing.com [130.247.25.140]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9HLUVxD027112 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK) for <ipv6@ietf.org>; Thu, 17 Oct 2013 14:30:32 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-PHX-211.sw.nos.boeing.com ([169.254.11.248]) with mapi id 14.03.0158.001; Thu, 17 Oct 2013 14:30:30 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: IPv6 <ipv6@ietf.org>
Subject: RE: RFC4821 for tunnels using SEAL
Thread-Topic: RFC4821 for tunnels using SEAL
Thread-Index: AQHOuXZekaTnL3mBHkmiKZRKieAct5n5i8ag
Date: Thu, 17 Oct 2013 21:30:30 +0000
Message-ID: <2134F8430051B64F815C691A62D98318131E90@XCH-BLV-504.nw.nos.boeing.com>
References: <782A011A-B28F-4BD9-B3F1-C194D6244DFA@gmail.com> <Pine.LNX.4.64.1308010951100.15607@shell4.bayarea.net> <Pine.LNX.4.64.1308052027420.28100@shell4.bayarea.net> <f4cb5436e86b4ec88d34f2d21e2bbb24@BL2PR05MB243.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983180E0A69@XCH-BLV-504.nw.nos.boeing.com> <fee4460daf2748e0bc5efda62c00b7df@BL2PR05MB243.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983180E0D96@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983180E0E0D@XCH-BLV-504.nw.nos.boeing.com> <ce9ac441c5c949d184997bcce7d154f5@BL2PR05MB243.namprd05.prod.outlook.com> <Pine.LNX.4.64.1308191017070.7703@shell4.bayarea.net> <58A2CCE5-4EAB-4D80-8A97-88885F0E268C@kumari.net> <Pine.LNX.4.64.1308271421490.16620@shell4.bayarea.net> <Pine.LNX.4.64.1309221049010.11395@shell4.bayarea.net> <5240A149.4090600@si6networks.com> <2134F8430051B64F815C691A62D9831811195A@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983181119E1@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D983181119E1@XCH-BLV-504.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Oct 2013 21:30:41 -0000

Hi,

A new version of the SEAL code is available here:

http://linkupnetworks.com/seal/sealv2-0.1.tgz

This version picks up changes introduced by the recently
released -63 SEAL draft version:

http://www.ietf.org/id/draft-templin-intarea-seal-63.txt

It also adds support for IPv6-in-IPv4 tunnels, and ensures
that the first fragment of a fragmented tunneled packet will
include as close as possible to the IPv6 minMTU of 1280 bytes.

Thanks - Fred
fred.l.templin@boeing.com



> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> Templin, Fred L
> Sent: Tuesday, September 24, 2013 3:35 PM
> To: IPv6
> Subject: RFC4821 for tunnels using SEAL
>=20
> Hi,
>=20
> I have prepared an alpha implementation of SEAL that focuses
> on RFC4821 for tunnels:
>=20
>     http://linkupnetworks.com/seal/sealv2-0.0.tgz
>=20
> The code has been tested on Ubuntu 12.04 linux with the 3.10.12
> linux kernel. The release contains a README with instructions
> on how to reproduce the experiments.
>=20
> The implementation has been tested with both IP/IPv6 and GRE/IPv6
> tunnels, and includes test scripts that can show the functionality
> using the Common Open Research Emulator (CORE):
>=20
>     http://cs.itd.nrl.navy.mil/work/core/
>=20
> The implementation inserts a SEAL shim header between the outer
> IPv6 header and the inner packet, and uses SEAL fragmentation
> and reassembly as follows:
>=20
>   1) If the inner packet is no larger than 1280 bytes minus the
>      length of the encapsulation headers, encapsulate and send
>      without fragmentation.
>=20
>   2) If the inner packet is larger than 1500 bytes but no larger
>      than the path MTU, encapsulate and send without fragmentation.
>=20
>   3) For all other packets, encapsulate and use SEAL fragmentation
>      to break the packets into a size that should be small enough
>      to traverse the path without further fragmentation even if
>      there are other tunnels in the path. At the same time, probe
>      the path to see if packets of this size can be delivered without
>      fragmentation and, if so, discontinue the fragmentation process
>      and send future packets in this size range as whole packets.
>=20
> The procedures are specified in 'draft-templin-intarea-seal', which
> can be found here:
>=20
>     http://tools.ietf.org/html/draft-templin-intarea-seal
>=20
> Any comments or observations would be welcome.
>=20
> Thanks - Fred
> fred.l.templin@boeing.com
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

From ietf-secretariat-reply@ietf.org  Fri Oct 18 11:31:56 2013
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1556411E82B9 for <ipv6@ietfa.amsl.com>; Fri, 18 Oct 2013 11:31:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.355
X-Spam-Level: 
X-Spam-Status: No, score=-101.355 tagged_above=-999 required=5 tests=[AWL=-0.974, BAYES_00=-2.599, NO_RELAYS=-0.001, TVD_SPACE_RATIO=2.219, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YOjpxXdyjZ36; Fri, 18 Oct 2013 11:31:55 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DDF111E82C9; Fri, 18 Oct 2013 11:31:53 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
To: 6man-chairs@tools.ietf.org, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org
Subject: ID Tracker State Update Notice: <draft-ietf-6man-ext-transmit-05.txt>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131018183153.20826.68539.idtracker@ietfa.amsl.com>
Date: Fri, 18 Oct 2013 11:31:53 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 18 Oct 2013 18:31:56 -0000

IANA action state changed to In Progress
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-6man-ext-transmi=
t/


From ietf-secretariat-reply@ietf.org  Fri Oct 18 14:18:55 2013
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7980111E8332 for <ipv6@ietfa.amsl.com>; Fri, 18 Oct 2013 14:18:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.356
X-Spam-Level: 
X-Spam-Status: No, score=-101.356 tagged_above=-999 required=5 tests=[AWL=-0.975, BAYES_00=-2.599, NO_RELAYS=-0.001, TVD_SPACE_RATIO=2.219, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ynevzcn7jRK2; Fri, 18 Oct 2013 14:18:55 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 39D5811E81F2; Fri, 18 Oct 2013 14:18:55 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
To: 6man-chairs@tools.ietf.org, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org
Subject: ID Tracker State Update Notice: <draft-ietf-6man-ext-transmit-05.txt>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131018211855.4069.92320.idtracker@ietfa.amsl.com>
Date: Fri, 18 Oct 2013 14:18:55 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 18 Oct 2013 21:18:55 -0000

State changed to RFC Ed Queue from Approved-announcement sent
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-6man-ext-transmi=
t/


From internet-drafts@ietf.org  Fri Oct 18 14:32:35 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A693C11E8358; Fri, 18 Oct 2013 14:32:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Level: 
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N29DnBalc3T8; Fri, 18 Oct 2013 14:32:35 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1289B11E8353; Fri, 18 Oct 2013 14:32:31 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-multicast-addr-arch-update-02.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131018213230.21929.15660.idtracker@ietfa.amsl.com>
Date: Fri, 18 Oct 2013 14:32:30 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 18 Oct 2013 21:32:35 -0000

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           : Updates to the IPv6 Multicast Addressing Architecture
	Author(s)       : Mohamed Boucadair
                          Stig Venaas
	Filename        : draft-ietf-6man-multicast-addr-arch-update-02.txt
	Pages           : 8
	Date            : 2013-10-18

Abstract:
   This document updates the IPv6 multicast addressing architecture by
   defining the 17-20 reserved bits as generic flag bits.  The document
   provides also some clarifications related to the use of these flag
   bits.

   This document updates RFC 3956, RFC 3306 and RFC 4291.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-multicast-addr-arch-update

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-multicast-addr-arch-update-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-multicast-addr-arch-upda=
te-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 Fred.L.Templin@boeing.com  Fri Oct 18 15:17:15 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E9BD21F9A71 for <ipv6@ietfa.amsl.com>; Fri, 18 Oct 2013 15:17:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.516
X-Spam-Level: 
X-Spam-Status: No, score=-6.516 tagged_above=-999 required=5 tests=[AWL=0.083,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NNpF4bYEpygJ for <ipv6@ietfa.amsl.com>; Fri, 18 Oct 2013 15:17:10 -0700 (PDT)
Received: from blv-mbsout-01.boeing.com (blv-mbsout-01.boeing.com [130.76.32.231]) by ietfa.amsl.com (Postfix) with ESMTP id A26021F0D13 for <ipv6@ietf.org>; Fri, 18 Oct 2013 15:17:07 -0700 (PDT)
Received: from blv-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9IMH6AJ024785 for <ipv6@ietf.org>; Fri, 18 Oct 2013 15:17:07 -0700
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9IMH6WL024781 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK) for <ipv6@ietf.org>; Fri, 18 Oct 2013 15:17:06 -0700
Received: from XCH-EXCO-103.nw.nos.boeing.com (130.247.25.37) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Fri, 18 Oct 2013 15:17:07 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-EXCO-103.nw.nos.boeing.com ([fe80::7434:66d:a0ba:2234%15]) with mapi id 14.03.0158.001; Fri, 18 Oct 2013 15:17:05 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: IPv6 <ipv6@ietf.org>
Subject: RE: RFC4821 for tunnels using SEAL
Thread-Topic: RFC4821 for tunnels using SEAL
Thread-Index: AQHOuXZekaTnL3mBHkmiKZRKieAct5n5i8aggAGevVA=
Date: Fri, 18 Oct 2013 22:17:04 +0000
Message-ID: <2134F8430051B64F815C691A62D983181333AC@XCH-BLV-504.nw.nos.boeing.com>
References: <782A011A-B28F-4BD9-B3F1-C194D6244DFA@gmail.com> <Pine.LNX.4.64.1308010951100.15607@shell4.bayarea.net> <Pine.LNX.4.64.1308052027420.28100@shell4.bayarea.net> <f4cb5436e86b4ec88d34f2d21e2bbb24@BL2PR05MB243.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983180E0A69@XCH-BLV-504.nw.nos.boeing.com> <fee4460daf2748e0bc5efda62c00b7df@BL2PR05MB243.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983180E0D96@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983180E0E0D@XCH-BLV-504.nw.nos.boeing.com> <ce9ac441c5c949d184997bcce7d154f5@BL2PR05MB243.namprd05.prod.outlook.com> <Pine.LNX.4.64.1308191017070.7703@shell4.bayarea.net> <58A2CCE5-4EAB-4D80-8A97-88885F0E268C@kumari.net> <Pine.LNX.4.64.1308271421490.16620@shell4.bayarea.net> <Pine.LNX.4.64.1309221049010.11395@shell4.bayarea.net> <5240A149.4090600@si6networks.com> <2134F8430051B64F815C691A62D9831811195A@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983181119E1@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D98318131E90@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D98318131E90@XCH-BLV-504.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 18 Oct 2013 22:17:15 -0000

Hi, I had to make another change before putting this to rest. A new
version of the SEAL code is here:

http://linkupnetworks.com/seal/sealv2-0.2.tgz

and picks up the changes introduced in the -64 version of the spec:

http://www.ietf.org/id/draft-templin-intarea-seal-64.txt

The substantive change is that SEAL is now using the IP protocol
number for the IPv6 Fragment Header, and codes the Reserved field
of the Fragment Header to indicate that SEAL is being used. On
Wireshark, it looks just like an ordinary IPv6 Fragment Header,
but if you look closely the Reserved field has the value
"SEAL_VER1" encoded instead of set to 0.

Everything else works just as in the previous release. Only now,
there is no need for an experimental IP version number and no need
to bother IANA about assigning an official IP version number. This
is in fact simply a new version of the IPv6 fragment header. (That
it also gets used in IPv4 is somewhat interesting...)

Thanks - Fred
fred.l.templin@boeing.com



> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> Templin, Fred L
> Sent: Thursday, October 17, 2013 2:31 PM
> To: IPv6
> Subject: RE: RFC4821 for tunnels using SEAL
>=20
> Hi,
>=20
> A new version of the SEAL code is available here:
>=20
> http://linkupnetworks.com/seal/sealv2-0.1.tgz
>=20
> This version picks up changes introduced by the recently
> released -63 SEAL draft version:
>=20
> http://www.ietf.org/id/draft-templin-intarea-seal-63.txt
>=20
> It also adds support for IPv6-in-IPv4 tunnels, and ensures
> that the first fragment of a fragmented tunneled packet will
> include as close as possible to the IPv6 minMTU of 1280 bytes.
>=20
> Thanks - Fred
> fred.l.templin@boeing.com
>=20
>=20
>=20
> > -----Original Message-----
> > From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf
> Of
> > Templin, Fred L
> > Sent: Tuesday, September 24, 2013 3:35 PM
> > To: IPv6
> > Subject: RFC4821 for tunnels using SEAL
> >
> > Hi,
> >
> > I have prepared an alpha implementation of SEAL that focuses
> > on RFC4821 for tunnels:
> >
> >     http://linkupnetworks.com/seal/sealv2-0.0.tgz
> >
> > The code has been tested on Ubuntu 12.04 linux with the 3.10.12
> > linux kernel. The release contains a README with instructions
> > on how to reproduce the experiments.
> >
> > The implementation has been tested with both IP/IPv6 and GRE/IPv6
> > tunnels, and includes test scripts that can show the functionality
> > using the Common Open Research Emulator (CORE):
> >
> >     http://cs.itd.nrl.navy.mil/work/core/
> >
> > The implementation inserts a SEAL shim header between the outer
> > IPv6 header and the inner packet, and uses SEAL fragmentation
> > and reassembly as follows:
> >
> >   1) If the inner packet is no larger than 1280 bytes minus the
> >      length of the encapsulation headers, encapsulate and send
> >      without fragmentation.
> >
> >   2) If the inner packet is larger than 1500 bytes but no larger
> >      than the path MTU, encapsulate and send without fragmentation.
> >
> >   3) For all other packets, encapsulate and use SEAL fragmentation
> >      to break the packets into a size that should be small enough
> >      to traverse the path without further fragmentation even if
> >      there are other tunnels in the path. At the same time, probe
> >      the path to see if packets of this size can be delivered without
> >      fragmentation and, if so, discontinue the fragmentation process
> >      and send future packets in this size range as whole packets.
> >
> > The procedures are specified in 'draft-templin-intarea-seal', which
> > can be found here:
> >
> >     http://tools.ietf.org/html/draft-templin-intarea-seal
> >
> > Any comments or observations would be welcome.
> >
> > Thanks - Fred
> > fred.l.templin@boeing.com
> > --------------------------------------------------------------------
> > 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 brian@innovationslab.net  Sat Oct 19 07:27:21 2013
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93A6911E81C7 for <ipv6@ietfa.amsl.com>; Sat, 19 Oct 2013 07:27:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.574
X-Spam-Level: 
X-Spam-Status: No, score=-102.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r2MM-hIjkwfB for <ipv6@ietfa.amsl.com>; Sat, 19 Oct 2013 07:27:14 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 64D2F11E81A9 for <ipv6@ietf.org>; Sat, 19 Oct 2013 07:27:14 -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 E99228807C; Sat, 19 Oct 2013 07:27:13 -0700 (PDT)
Received: from Littlejohn.local (c-69-140-213-249.hsd1.md.comcast.net [69.140.213.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 86A1313680E2; Sat, 19 Oct 2013 07:27:13 -0700 (PDT)
Message-ID: <526296B8.5080108@innovationslab.net>
Date: Sat, 19 Oct 2013 10:27:04 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Subject: Re-use of fragment header in SEAL
X-Enigmail-Version: 1.5.2
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="TjL1sTEHLtUiSL6495ivnBRI3Nc4jCjbQ"
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 19 Oct 2013 14:27:21 -0000

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

Fred,
     The way you have re-used the Next Header value of the Fragment
Header may be troublesome.  If someone updates 2460 to change the
Fragment Header (i.e., add additional info in the current Reserved
field), they will step on your use of the header and make them
indistinguishable.

Regards,
Brian


--TjL1sTEHLtUiSL6495ivnBRI3Nc4jCjbQ
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

iQEcBAEBCgAGBQJSYpa+AAoJEBOZRqCi7goqACwIALiXBHc3SdjZQMnrOD46FyIS
Qcuf1XuqvI3JEdXpoK2G4B++hdZRFgH8qoLw59WCewvvZJ8rDEhDt86YobbjnUHp
CDQgqzBlC/b3sXo40Il8uY7hS7AhcZ04T3xYAf/mRKJEhsaltZJGMNzjNYXSBE69
UyVu+MCFJDQz/l0Z9mGFFe0Ed+bb+CwZ1qiS/vAQs17C+PQVPxbfnP+11sO5mcpA
ooA6VwHtzE5PQ7bDM+t5cAO51Ng5H9QCNbOSRFuHeCox47/BdP2/dXMW6JKIc9LL
ro+ygqa0bGJRIP8XworSu1myIqKgs8hghAj5vqkbBbjTBMYN1Zcv5AHd60rthxU=
=d9rg
-----END PGP SIGNATURE-----

--TjL1sTEHLtUiSL6495ivnBRI3Nc4jCjbQ--

From v6ops@globis.net  Sun Oct 20 05:07:43 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25B9E11E83B7; Sun, 20 Oct 2013 05:07:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D86ek-V6F8fQ; Sun, 20 Oct 2013 05:07:42 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id DD26611E81B0; Sun, 20 Oct 2013 05:07:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 05DC1870076; Sun, 20 Oct 2013 14:07:33 +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 2FVtSBQZRb1a; Sun, 20 Oct 2013 14:07:32 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id C7D7987003F; Sun, 20 Oct 2013 14:07:32 +0200 (CEST)
Message-ID: <5263C783.1080001@globis.net>
Date: Sun, 20 Oct 2013 14:07:31 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Nalini Elkins <nalini.elkins@insidethestack.com>
Subject: Re: [v6ops] Fw: New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-04.txt
References: <20131017032024.5051.20799.idtracker@ietfa.amsl.com> <1381980305.36254.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com>
In-Reply-To: <1381980305.36254.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: v6ops WG <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 20 Oct 2013 12:07:43 -0000

Nalini Elkins wrote:
> All,
>
> I have revised the 6man submission to take out the calculations and packet flows.  All of these are in the IPPM document.   A notation of all the usage cases that this methodology should handle has also been added to the IPPM draft.
>
> The IPPM draft is here: http://datatracker.ietf.org/doc/draft-elkins-ippm-pdm-metrics/
>
> The 6man draft is below.
>
> I appreciate any thoughts and comments.
>
> A new version of I-D, draft-elkins-6man-ipv6-pdm-dest-option-04.txt
> has been successfully submitted by Nalini Elkins and posted to the
> IETF repository.
>
> Filename:     draft-elkins-6man-ipv6-pdm-dest-option
> Revision:     04
> Title:         IPv6 Performance and Diagnostic Metrics Destination Option
> Creation date:     2013-10-16
> Group:         Individual Submission
> Number of pages: 12
> URL:             http://www.ietf.org/internet-drafts/draft-elkins-6man-ipv6-pdm-dest-option-04.txt
> Status:          http://datatracker.ietf.org/doc/draft-elkins-6man-ipv6-pdm-dest-option
> Htmlized:        http://tools.ietf.org/html/draft-elkins-6man-ipv6-pdm-dest-option-04
> Diff:            http://www.ietf.org/rfcdiff?url2=draft-elkins-6man-ipv6-pdm-dest-option-04
>
> Abstract:
>    To diagnose performance and connectivity problems, metrics on real
>    (non-synthetic) transmission are critical for timely end-to-end
>    problem resolution. Such diagnostics may be real-time or after the
>    fact, but must not impact an operational production network. The base
>    metrics are: packet sequence number and packet timestamp.  Metrics
>    derived from these will be described separately. This document solves
>    these problems with a new destination option, the Performance and
>    Diagnostic Metrics destination option (PDM).
>
>
>                                                                                   
>
>
> 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

Given that it seems to me that:

1) encoding has to be fast, but decoding does not
2) a node's clock could be either in our out of synch with some notional
master clock (e.g. via NTP)
3) two clocks could be in synch to a master source, but the master
sources may themselves not share a common source (one sourced from GPS,
one from DCF77)
4) the key to being able to perform the end to end calculations is
whether two communicating nodes are synchronised to the same master
clock (within some level of error/jitter)
5) the absolute time is not particularly important

Q1. Why do you want to encode differences as deltas in the case of an
unsynchronised/ free running clock?

Isn't that slow, and difficult for hardware implementations to achieve
(e.g. TCP offload)?
Doesn't it also require maintaining large amounts of state in the
sending node.
 
Why not just encode the timestamp as-is and perform the appropriate
difference calculation during decoding?

Q2. Why do you need two separate packet formats at all?

Why not have a common format for all cases, containing a timestamp based
on the local clock, plus an optional field containing a flag that states
if the local timestamp is coordinated to some master clock, plus an
identifier for the master clock.

You could then encode whether a node had a free-running clock (case 2),
a synchronised clock (case 1), and whether it was synched via NTP to
some stratum 0 source e.g. GPS, and also some identification of the
stratum 1 source (IPv6 address).

Two communicating nodes could then use e.g. NTP trace to see if they
shared a common clock source or not, before performing their calculations.

IMHO that would then allow you to place some error bounds on your time
calculations, whilst also simplifying the implementation for the sender.

-- 
Regards,
RayH


From Fred.L.Templin@boeing.com  Mon Oct 21 08:08:26 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 323DF11E85ED for <ipv6@ietfa.amsl.com>; Mon, 21 Oct 2013 08:08:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.519
X-Spam-Level: 
X-Spam-Status: No, score=-6.519 tagged_above=-999 required=5 tests=[AWL=0.080,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sgz21uBifeJk for <ipv6@ietfa.amsl.com>; Mon, 21 Oct 2013 08:08:19 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) by ietfa.amsl.com (Postfix) with ESMTP id 5817A11E85FF for <ipv6@ietf.org>; Mon, 21 Oct 2013 08:07:43 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9LF7gsu008120 for <ipv6@ietf.org>; Mon, 21 Oct 2013 10:07:42 -0500
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9LF7L3L007212 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 21 Oct 2013 10:07:42 -0500
Received: from XCH-BLV-402.nw.nos.boeing.com (130.247.25.31) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Mon, 21 Oct 2013 08:07:37 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-BLV-402.nw.nos.boeing.com ([169.254.2.160]) with mapi id 14.03.0158.001; Mon, 21 Oct 2013 08:07:37 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Brian Haberman <brian@innovationslab.net>
Subject: RE: Re-use of fragment header in SEAL
Thread-Topic: Re-use of fragment header in SEAL
Thread-Index: AQHOzNdeHEb9dzMx1kyeywzrFKUFx5n/Q/3A
Date: Mon, 21 Oct 2013 15:07:36 +0000
Message-ID: <2134F8430051B64F815C691A62D9831813500F@XCH-BLV-504.nw.nos.boeing.com>
References: <526296B8.5080108@innovationslab.net>
In-Reply-To: <526296B8.5080108@innovationslab.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Oct 2013 15:08:26 -0000

Hi Brian,

> Fred,
>      The way you have re-used the Next Header value of the Fragment
> Header may be troublesome.  If someone updates 2460 to change the
> Fragment Header (i.e., add additional info in the current Reserved
> field), they will step on your use of the header and make them
> indistinguishable.

That is true, but if the SEAL document were the one to update RFC2460
then there would be no concerns for future collisions. So, in the next
document version I will add "Updates RFC2460". Thanks for the comment.

Fred
fred.l.templin@boeing.com

> Regards,
> Brian


From bob.hinden@gmail.com  Mon Oct 21 09:22:04 2013
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE15811E81F3 for <ipv6@ietfa.amsl.com>; Mon, 21 Oct 2013 09:22:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TPzYvVUQg4UM for <ipv6@ietfa.amsl.com>; Mon, 21 Oct 2013 09:22:04 -0700 (PDT)
Received: from mail-wg0-x232.google.com (mail-wg0-x232.google.com [IPv6:2a00:1450:400c:c00::232]) by ietfa.amsl.com (Postfix) with ESMTP id EC86511E81DA for <ipv6@ietf.org>; Mon, 21 Oct 2013 09:22:03 -0700 (PDT)
Received: by mail-wg0-f50.google.com with SMTP id n12so6840964wgh.29 for <ipv6@ietf.org>; Mon, 21 Oct 2013 09:22:03 -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 :content-transfer-encoding:message-id:references:to; bh=eZY6npG8CYSPebOxgFzbfQA6rRSC/pXHHS5n1PkrKXE=; b=Gd4GtrFaBBMtO32znNNUv1KGDIxR8eE4cHBNRTZcUNakKkcg/8qNjWiS/F3MmBvcbI erDH4Hh198t54HQekvFBHc22vhSaEjOpMoSCb4SdS6p7vUnJCPGLpk/SRqsguBC/4Zdj +hT6oRxcOWXT+Uf28dzKUEq2XV+7TJUXjZHIEtZQC9oa1zWpoP/9G0m3GaYQUUjyMeZ5 eQzS7fkFWSRThTuUZyzmmeoMVdgFzzBEDlmH/Uvz+6oAyO0y+oxtpmkVQlQumTyolVs1 VNhTN2iTo9jBiLxtF/H6Qc8bfCCJf8aHSjiwXWI0zoHHPnNiGuJ8n2G37RjojObYMTMS Njxg==
X-Received: by 10.180.89.42 with SMTP id bl10mr10291792wib.47.1382372522996; Mon, 21 Oct 2013 09:22:02 -0700 (PDT)
Received: from [10.0.0.24] (c-24-130-151-138.hsd1.ca.comcast.net. [24.130.151.138]) by mx.google.com with ESMTPSA id eq12sm33794429wic.7.2013.10.21.09.21.57 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Oct 2013 09:21:59 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Re-use of fragment header in SEAL
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831813500F@XCH-BLV-504.nw.nos.boeing.com>
Date: Mon, 21 Oct 2013 09:21:53 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <2D191A96-1EF1-4792-8C26-6C7B5D835C72@gmail.com>
References: <526296B8.5080108@innovationslab.net> <2134F8430051B64F815C691A62D9831813500F@XCH-BLV-504.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.1510)
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, Brian Haberman <brian@innovationslab.net>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Oct 2013 16:22:05 -0000

Fred,

> Fred,
>>     The way you have re-used the Next Header value of the Fragment
>> Header may be troublesome.  If someone updates 2460 to change the
>> Fragment Header (i.e., add additional info in the current Reserved
>> field), they will step on your use of the header and make them
>> indistinguishable.
>=20
> That is true, but if the SEAL document were the one to update RFC2460
> then there would be no concerns for future collisions. So, in the next
> document version I will add "Updates RFC2460". Thanks for the comment.

I don't think it is appropriate for a draft that is updating an =
experimental RFC to update a standards track RFC.  It will cause a lot =
of confusion in the community.

Bob




From Fred.L.Templin@boeing.com  Mon Oct 21 09:39:01 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B3C611E8411 for <ipv6@ietfa.amsl.com>; Mon, 21 Oct 2013 09:39:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.521
X-Spam-Level: 
X-Spam-Status: No, score=-6.521 tagged_above=-999 required=5 tests=[AWL=0.078,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id huKkUHBBRtq0 for <ipv6@ietfa.amsl.com>; Mon, 21 Oct 2013 09:38:54 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) by ietfa.amsl.com (Postfix) with ESMTP id CA84D11E8666 for <ipv6@ietf.org>; Mon, 21 Oct 2013 09:36:46 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9LGafwc008212 for <ipv6@ietf.org>; Mon, 21 Oct 2013 11:36:41 -0500
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9LGadq1008152 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 21 Oct 2013 11:36:41 -0500
Received: from XCH-EXCO-105.nw.nos.boeing.com (130.247.204.69) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Mon, 21 Oct 2013 09:36:34 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-EXCO-105.nw.nos.boeing.com ([fe80::f17a:6d23:e244:5ed2%14]) with mapi id 14.03.0158.001; Mon, 21 Oct 2013 11:36:32 -0500
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Bob Hinden <bob.hinden@gmail.com>
Subject: RE: Re-use of fragment header in SEAL
Thread-Topic: Re-use of fragment header in SEAL
Thread-Index: AQHOznmnHEb9dzMx1kyeywzrFKUFx5n/WXHQ
Date: Mon, 21 Oct 2013 16:36:30 +0000
Message-ID: <2134F8430051B64F815C691A62D983181353A9@XCH-BLV-504.nw.nos.boeing.com>
References: <526296B8.5080108@innovationslab.net> <2134F8430051B64F815C691A62D9831813500F@XCH-BLV-504.nw.nos.boeing.com> <2D191A96-1EF1-4792-8C26-6C7B5D835C72@gmail.com>
In-Reply-To: <2D191A96-1EF1-4792-8C26-6C7B5D835C72@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: Brian Haberman <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Oct 2013 16:39:01 -0000

Hi Bob,

> -----Original Message-----
> From: Bob Hinden [mailto:bob.hinden@gmail.com]
> Sent: Monday, October 21, 2013 9:22 AM
> To: Templin, Fred L
> Cc: Bob Hinden; Brian Haberman; ipv6@ietf.org
> Subject: Re: Re-use of fragment header in SEAL
>=20
> Fred,
>=20
> > Fred,
> >>     The way you have re-used the Next Header value of the Fragment
> >> Header may be troublesome.  If someone updates 2460 to change the
> >> Fragment Header (i.e., add additional info in the current Reserved
> >> field), they will step on your use of the header and make them
> >> indistinguishable.
> >
> > That is true, but if the SEAL document were the one to update RFC2460
> > then there would be no concerns for future collisions. So, in the
> next
> > document version I will add "Updates RFC2460". Thanks for the
> comment.
>=20
> I don't think it is appropriate for a draft that is updating an
> experimental RFC to update a standards track RFC.  It will cause a lot
> of confusion in the community.

I think then that we would need to re-target SEAL as standards-track,
and as obsoleting the previous experimental RFC. I can make that
change in the next draft version so that it is clear that we are
not trying to make an experimental update a standards track.

Then, I guess the next question is whether we want to continue with
SEAL as an individual sub or bring it in as a 6man wg item? I am
open to either approach.

Thanks - Fred
fred.l.templin@boeing.com
=20
> Bob
=20


From bob.hinden@gmail.com  Mon Oct 21 10:01:26 2013
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21BF711E86A2 for <ipv6@ietfa.amsl.com>; Mon, 21 Oct 2013 10:01:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9rsL13S6KcIg for <ipv6@ietfa.amsl.com>; Mon, 21 Oct 2013 10:01:25 -0700 (PDT)
Received: from mail-we0-x230.google.com (mail-we0-x230.google.com [IPv6:2a00:1450:400c:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id AABE211E8604 for <ipv6@ietf.org>; Mon, 21 Oct 2013 10:01:23 -0700 (PDT)
Received: by mail-we0-f176.google.com with SMTP id w62so6724423wes.7 for <ipv6@ietf.org>; Mon, 21 Oct 2013 10:01:14 -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 :content-transfer-encoding:message-id:references:to; bh=jevm8ISU3OENU+Oc//g6XaF5Q148YutseF51nKInrtY=; b=CBM8zKTOfH6eO412Plbio/0nwScu0RLCFSB+3VLPSHSd56vRBAXyqlmPdHOM2IDIJ+ liCwogYzIVRLMxbAUjJErHSMnAJ5BjCeH/NFqcJrcukA/jYKsgHsY7Wcf0zEySnVCelU MvBbiyOFl/DRqdfd8vAhBkSLpZQy+qfVh3YV8dyFEgwN6Ytg7HHdsjp1+iJ/q9LNk0Nd RdZ8x0MmYPJxekyyj/gjVx3aSD7EQ9O5x6XSxVzTt6Jx8Aeu6iHtekfEQmIEZI3393OK cIgpsAsYDOVD6EaCHFKChD2fJwI16PbdQEzJFMwnvRaHlKONg1uVHXKFWwMon7PK2Goj b5Sg==
X-Received: by 10.194.240.129 with SMTP id wa1mr14519553wjc.31.1382374874800;  Mon, 21 Oct 2013 10:01:14 -0700 (PDT)
Received: from [10.0.0.24] (c-24-130-151-138.hsd1.ca.comcast.net. [24.130.151.138]) by mx.google.com with ESMTPSA id gg20sm56481539wic.1.2013.10.21.10.01.12 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Oct 2013 10:01:13 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Re-use of fragment header in SEAL
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <2134F8430051B64F815C691A62D983181353A9@XCH-BLV-504.nw.nos.boeing.com>
Date: Mon, 21 Oct 2013 10:01:09 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <99FA6EFF-E860-4DC1-8BB3-1759F135483A@gmail.com>
References: <526296B8.5080108@innovationslab.net> <2134F8430051B64F815C691A62D9831813500F@XCH-BLV-504.nw.nos.boeing.com> <2D191A96-1EF1-4792-8C26-6C7B5D835C72@gmail.com> <2134F8430051B64F815C691A62D983181353A9@XCH-BLV-504.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.1510)
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, Brian Haberman <brian@innovationslab.net>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Oct 2013 17:01:26 -0000

Fred,

>> I don't think it is appropriate for a draft that is updating an
>> experimental RFC to update a standards track RFC.  It will cause a =
lot
>> of confusion in the community.
>=20
> I think then that we would need to re-target SEAL as standards-track,
> and as obsoleting the previous experimental RFC. I can make that
> change in the next draft version so that it is clear that we are
> not trying to make an experimental update a standards track.
>=20
> Then, I guess the next question is whether we want to continue with
> SEAL as an individual sub or bring it in as a 6man wg item? I am
> open to either approach.

I don't know what is appropriate, but there would have to be enough =
interest in taking on this work.  I have only seen one person talking =
about it.

But as I said, in it's current state it is not appropriate to update a =
standards track RFC.

Bob




From Fred.L.Templin@boeing.com  Mon Oct 21 10:17:29 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B42911E83B4 for <ipv6@ietfa.amsl.com>; Mon, 21 Oct 2013 10:17:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Level: 
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XwyqzLmR4awC for <ipv6@ietfa.amsl.com>; Mon, 21 Oct 2013 10:17:22 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) by ietfa.amsl.com (Postfix) with ESMTP id 00B6511E869F for <ipv6@ietf.org>; Mon, 21 Oct 2013 10:17:15 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9LHHFeN013928 for <ipv6@ietf.org>; Mon, 21 Oct 2013 10:17:15 -0700
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9LHH1UQ013784 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 21 Oct 2013 10:17:15 -0700
Received: from XCH-BLV-403.nw.nos.boeing.com (130.247.25.62) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Mon, 21 Oct 2013 10:17:13 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-BLV-403.nw.nos.boeing.com ([169.254.3.243]) with mapi id 14.03.0158.001; Mon, 21 Oct 2013 10:17:13 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Bob Hinden <bob.hinden@gmail.com>
Subject: RE: Re-use of fragment header in SEAL
Thread-Topic: Re-use of fragment header in SEAL
Thread-Index: AQHOzn8jHEb9dzMx1kyeywzrFKUFx5n/ZMZQ
Date: Mon, 21 Oct 2013 17:17:12 +0000
Message-ID: <2134F8430051B64F815C691A62D9831813550A@XCH-BLV-504.nw.nos.boeing.com>
References: <526296B8.5080108@innovationslab.net> <2134F8430051B64F815C691A62D9831813500F@XCH-BLV-504.nw.nos.boeing.com> <2D191A96-1EF1-4792-8C26-6C7B5D835C72@gmail.com> <2134F8430051B64F815C691A62D983181353A9@XCH-BLV-504.nw.nos.boeing.com> <99FA6EFF-E860-4DC1-8BB3-1759F135483A@gmail.com>
In-Reply-To: <99FA6EFF-E860-4DC1-8BB3-1759F135483A@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: Brian Haberman <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Oct 2013 17:17:29 -0000

Hi Bob,

> -----Original Message-----
> From: Bob Hinden [mailto:bob.hinden@gmail.com]
> Sent: Monday, October 21, 2013 10:01 AM
> To: Templin, Fred L
> Cc: Bob Hinden; Brian Haberman; ipv6@ietf.org
> Subject: Re: Re-use of fragment header in SEAL
>=20
> Fred,
>=20
> >> I don't think it is appropriate for a draft that is updating an
> >> experimental RFC to update a standards track RFC.  It will cause a
> lot
> >> of confusion in the community.
> >
> > I think then that we would need to re-target SEAL as standards-track,
> > and as obsoleting the previous experimental RFC. I can make that
> > change in the next draft version so that it is clear that we are
> > not trying to make an experimental update a standards track.
> >
> > Then, I guess the next question is whether we want to continue with
> > SEAL as an individual sub or bring it in as a 6man wg item? I am
> > open to either approach.
>=20
> I don't know what is appropriate, but there would have to be enough
> interest in taking on this work.  I have only seen one person talking
> about it.

Can I get an agenda slot to talk about it in Vancouver?
=20
> But as I said, in it's current state it is not appropriate to update a
> standards track RFC.

OK - I will fix it.

Thanks - Fred
fred.l.templin@boeing.com


From ietf@rozanak.com  Mon Oct 21 11:20:14 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33C9411E839D for <ipv6@ietfa.amsl.com>; Mon, 21 Oct 2013 11:20:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.184
X-Spam-Level: 
X-Spam-Status: No, score=-0.184 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VFZgbXSS3phy for <ipv6@ietfa.amsl.com>; Mon, 21 Oct 2013 11:20:09 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id A848021F9FA2 for <ipv6@ietf.org>; Mon, 21 Oct 2013 11:20:09 -0700 (PDT)
Received: from kopoli (g231251108.adsl.alicedsl.de [92.231.251.108]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0M7XuJ-1VtYWY0esZ-00wXGH; Mon, 21 Oct 2013 14:20:08 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: "Andrew Yourtchenko" <ayourtch@gmail.com>, <ipv6@ietf.org>
Subject: ra privacy: an improvement to privacy extension plus source code
Date: Mon, 21 Oct 2013 20:20:02 +0200
Message-ID: <014301cece8a$2b780e20$82682a60$@rozanak.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0144_01CECE9A.EF030100"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac7N9zv8jFkYd89tRhe5F6vfxErc0Q==
Content-Language: en-us
X-Provags-ID: V02:K0:K4M1TeAdnt2yApS/EAC600ELtfs5n6LiNl88osv1oPt ft+aFXK4MVNK0njr44jxFr0aZ51PPcGVxz11YlTROrVvsnwbRw JoDKM++ek+MpauTpLm4NN4skSVOei23M0PGNKHyijjjJE4edfP x9DRHu3js3mKMksI7TH3z2HgUqE0e9VYc/9ab21mNvHuZpVjX0 QcyGzPsSsPAUjb04rOymmZx8qIICAq6g3kW7aUJl3EBX+0Ocx9 hqQnW8MIddxq1GJhxtlDkTF7RxcWvVUngPMjrhuO23vhaTsTiB f+OCf+rcNi5coCI9Njo2EZgycXxIyiqYa2HpNom+468Gy4HLGR NJhUN7vI3fZk5gQG3uMk=
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Oct 2013 18:20:14 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0144_01CECE9A.EF030100
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

First I would like to thank Andrew for his constructive comments off list. I
tried to address his concerns.

 

I wrote a small c++ program that compares ra-privacy with privacy extension.
Before, I submitted a version that only ran on windows OS
(www.hpi.uni-potsdam.de/fileadmin/hpi/FG_ITS/research/Ipv6/md5_Test.zip ).
This version works on Linux. I haven't tried it on another OS (FreeBSD ,
etc). I guess you should try to compile it for other OSs.

You only need to run compare.cpp. It will call the other functions.

http://sourceforge.net/u/hrafiee/raprivacy/ci/master/tree/

 

Finally I had a chance to update ra-privacy draft as well. The purpose of
this draft, if you can still remember :-), is to improve privacy
deficiencies that exist in Privacy Extension RFC  (RFC 4941) and update it.
Please share your comments and support the document. I would like to ask the
chair of 6man to assign a timeslot at the upcoming IETF meeting  to discuss
it further.

http://tools.ietf.org/html/draft-rafiee-6man-ra-privacy 

 

Thank you,

 

 

-----------smile----------

Hosnieh

. success is a journey, not a destination..

 


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>First I =
would like to thank Andrew for his constructive comments off list. I =
tried to address his concerns.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I wrote a =
small c++ program that compares ra-privacy with privacy extension. =
Before, I submitted a version that only ran on windows OS (<a =
href=3D"http://www.hpi.uni-potsdam.de/fileadmin/hpi/FG_ITS/research/Ipv6/=
md5_Test.zip">www.hpi.uni-potsdam.de/fileadmin/hpi/FG_ITS/research/Ipv6/m=
d5_Test.zip</a> ). This version works on Linux. I haven&#8217;t tried it =
on another OS (FreeBSD , etc). I guess you should try to compile it for =
other OSs.<o:p></o:p></p><p class=3DMsoNormal>You only need to run =
compare.cpp. It will call the other functions.<o:p></o:p></p><p =
class=3DMsoNormal><a =
href=3D"http://sourceforge.net/u/hrafiee/raprivacy/ci/master/tree/">http:=
//sourceforge.net/u/hrafiee/raprivacy/ci/master/tree/</a><o:p></o:p></p><=
p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Finally I =
had a chance to update ra-privacy draft as well. The purpose of this =
draft, if you can still remember :-), is to improve privacy deficiencies =
that exist in Privacy Extension RFC&nbsp; (RFC 4941) and update it. =
Please share your comments and support the document. I would like to ask =
the chair of 6man to assign a timeslot at the upcoming IETF =
meeting&nbsp; to discuss it further.<o:p></o:p></p><p =
class=3DMsoNormal><a =
href=3D"http://tools.ietf.org/html/draft-rafiee-6man-ra-privacy">http://t=
ools.ietf.org/html/draft-rafiee-6man-ra-privacy</a> <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Thank =
you,<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p =
class=3DMsoNormal><i>-----------smile</i>----------<o:p></o:p></p><p =
class=3DMsoNormal>Hosnieh<o:p></o:p></p><p class=3DMsoNormal><i><span =
style=3D'font-size:12.0pt'>&#8230; success is a journey, not a =
destination&#8230;.<o:p></o:p></span></i></p></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0144_01CECE9A.EF030100--


From jinmei.tatuya@gmail.com  Mon Oct 21 12:03:00 2013
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C09211E86C2; Mon, 21 Oct 2013 12:02:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.222
X-Spam-Level: *
X-Spam-Status: No, score=1.222 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3SNh1Aemf9WA; Mon, 21 Oct 2013 12:02:58 -0700 (PDT)
Received: from mail-wg0-x235.google.com (mail-wg0-x235.google.com [IPv6:2a00:1450:400c:c00::235]) by ietfa.amsl.com (Postfix) with ESMTP id 12B7011E865C; Mon, 21 Oct 2013 12:00:10 -0700 (PDT)
Received: by mail-wg0-f53.google.com with SMTP id y10so7184706wgg.32 for <multiple recipients>; Mon, 21 Oct 2013 12:00:08 -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=rS4fzCbJ4FWr9XlBmJlk+cjXUNHZnVlmo58XAAHEy2U=; b=ug4Agz6M12eN2WCB+DaUlCLqmoofQyGsH9lAhv5n/YGefak81q1YaSOX80EdMNUvaG FTWh4ZRmaqZFfMH9tm4vpyfJgnIjaToowGFR5v9mMWZob7MeQe6b3AW4Tr3UmZnKlIi0 mDjvZjMdsRSlfRLD2+6GND68blUuSMej7A5UQBCYSeMY/sxJ96rLdOnOhKc+9WPDUVq3 fcBEAJrXuSmaHf5XwwTRVQC2/0VAXXq6rzaRtHRDi2T8FWDbecO0LYXIRFJx/njs98Qz q52Q8u78PsixQXBz8RFdaDCbhHDY6oxlBnvOca7AZS0dbiVjMi+80iJMHUzEDlT7LN2l b7kg==
MIME-Version: 1.0
X-Received: by 10.180.86.230 with SMTP id s6mr11149204wiz.64.1382382008857; Mon, 21 Oct 2013 12:00:08 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.120.167 with HTTP; Mon, 21 Oct 2013 12:00:08 -0700 (PDT)
In-Reply-To: <3CC8783F-F4DA-47B9-A051-DBBA6EF00C19@gmail.com>
References: <3599.1381852752@sandelman.ca> <CE82BA46.24343%d.sturek@att.net> <CABOxzu2nLuny5uySEEdb6ji9ucE6xqGZ6DLe-mc6KUqVszNfFg@mail.gmail.com> <525DC6C9.2010808@gridmerge.com> <CABOxzu2apwBRpU1h4mKJwpO+U+Y9Q_q-h5AhZ+hGzAdjdPdmUQ@mail.gmail.com> <525E5064.4050109@gridmerge.com> <CABOxzu0L-EY0iDGpAJ+ER15CPL-3v8F77ewn-G=gZYODixevZg@mail.gmail.com> <3CC8783F-F4DA-47B9-A051-DBBA6EF00C19@gmail.com>
Date: Mon, 21 Oct 2013 12:00:08 -0700
X-Google-Sender-Auth: 6BZ1xqZg8blT5QbcDoVKDbjh0QU
Message-ID: <CAJE_bqdL3v4XK+dJPx1ZVFoRS+yjFDZEwVZ64fhYW6QUWVS6JA@mail.gmail.com>
Subject: Re: draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re: [Roll] [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope value of 3 - subnet-local)
From: =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>
To: Ralph Droms <rdroms.ietf@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Routing Over Low power and Lossy networks <roll@ietf.org>, "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Oct 2013 19:03:00 -0000

At Thu, 17 Oct 2013 09:10:50 -0700,
Ralph Droms <rdroms.ietf@gmail.com> wrote:

> Noting this conflict, I propose adding a bit of text to
> draft-ietf-6man-multicast-scopes to update RFC 4007 for consistency
> with RFC 4291:

I think making these consistent is a good idea.

> OLD:
>
>    o  The boundaries of zones of a scope other than interface-local,
>       link-local, and global must be defined and configured by network
>       administrators.
>
> NEW:
>
>    o  Admin-Local scope is the smallest scope that must be
>       administratively configured, i.e., not automatically derived
>       from physical connectivity or other, non-multicast-related
>       configuration.

I'm okay with the proposed text, but on a closer look I've noticed
a couple of subtle points you may want to consider:

- I see a slight difference between the OLD (RFC 4007) and NEW (RFC
  4291) even after fixing the obvious inconsistency, in that the NEW
  version does not necessarily say how the scopes larger than
  admin-local scope is configured; technically it only states
  interface-local and link-local (and "Realm-Local" if assigned)
  would not be automatically configured.  In fact, the global scope
  shouldn't be "administratively" configured, which is crystal clear
  from the OLD version, but not necessarily in the NEW version.

- should we worry about possible future updates to the addressing
  architecture and scope architecture documents?  If we keep these
  documents separately and have a copy of the text in both, we may need
  to update both copies when we need to make a change on this point as
  more "currently reserved" scopes are assigned.

These are probably too minor and maybe we can simply ignore the
subtlety.  If that's our consensus I'm okay with that.  But if we want
to address these points, maybe:

OLD:

   o  The boundaries of zones of a scope other than interface-local,
      link-local, and global must be defined and configured by network
      administrators.

NEW:

   o  The boundaries of zones of an interface-local, link-local, or
      global scope automatically derived from physical connectivity.
      For zones of other types of scopes, the IPv6 addressing
      architecture specification defines how their boundaries must be
      determined, whether automatically derived or administratively
      configured.

--
JINMEI, Tatuya

From gnocuil@gmail.com  Mon Oct 21 14:19:42 2013
Return-Path: <gnocuil@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66A5E11E827B for <ipv6@ietfa.amsl.com>; Mon, 21 Oct 2013 14:19:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SQMXnwdRr07X for <ipv6@ietfa.amsl.com>; Mon, 21 Oct 2013 14:19:41 -0700 (PDT)
Received: from mail-qe0-x22c.google.com (mail-qe0-x22c.google.com [IPv6:2607:f8b0:400d:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 945E611E8269 for <ipv6@ietf.org>; Mon, 21 Oct 2013 14:19:41 -0700 (PDT)
Received: by mail-qe0-f44.google.com with SMTP id 6so4234126qeb.31 for <ipv6@ietf.org>; Mon, 21 Oct 2013 14:19:40 -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 :content-type; bh=Gui2k4T+zjvWfhMaMCLZJEtoju7bKWIw7+e5yh8kIpk=; b=LFM2KzV2/z2WZMatKFf4sHFm5VQXqxnH/LmHBSR3qnFpfODdx6DSpRlL3vldeKrIZT kqNdJdjITUdo+UKBWoPsZrWDBeReasFTD03qY0sgm3E23Ggn2vnm4Qtp5nOK7X7xmct9 XBM8w9PeNPatUqFGKbRRbLCQyNPxGbycsBpmdNJDcUCKZzb0WDM4JfbbggV9rh+Wpj9G AeuE+IxCk8CaFssr3nN14wivxZllX4ImFS3HQ+MN822snL0xprPaN1S5hiRK1e8qoB9K djAXlBVBgFWA1xEKIKdvA8niuZOgvLihrvwxY5zF5QN5hs5cx+g8UCTJYwIcUnbXb+UV khgQ==
X-Received: by 10.49.131.200 with SMTP id oo8mr25788385qeb.0.1382390380889; Mon, 21 Oct 2013 14:19:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.96.185.33 with HTTP; Mon, 21 Oct 2013 14:19:20 -0700 (PDT)
In-Reply-To: <20131021182214.32521.22673.idtracker@ietfa.amsl.com>
References: <20131021182214.32521.22673.idtracker@ietfa.amsl.com>
From: Cong Liu <gnocuil@gmail.com>
Date: Tue, 22 Oct 2013 05:19:20 +0800
Message-ID: <CAF+sHxFeVnvQM-JC+gt=7MDtP5Hxwzp+i5UhMwF8g-+6oMW2tw@mail.gmail.com>
Subject: Fwd: New Version Notification for draft-liu-6man-ident-tunnel-packet-addr-00.txt
To: ipv6@ietf.org
Content-Type: multipart/alternative; boundary=047d7bdc8afe980cf404e946d7c7
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Oct 2013 21:19:42 -0000

--047d7bdc8afe980cf404e946d7c7
Content-Type: text/plain; charset=ISO-8859-1

Dear all,

We have submitted a new draft proposes how a IPv6 tunnel node identifies
inbound tunnel packets.

We appreciate any comments and questions.

Cong Liu

---------- Forwarded message ----------
From: <internet-drafts@ietf.org>
Date: 2013/10/22
Subject: New Version Notification for
draft-liu-6man-ident-tunnel-packet-addr-00.txt
To: Jianping Wu <jianping@cernet.edu.cn>, Cong Liu <gnocuil@gmail.com>,
Yong Cui <yong@csnet1.cs.tsinghua.edu.cn>



A new version of I-D, draft-liu-6man-ident-tunnel-packet-addr-00.txt
has been successfully submitted by Jianping Wu and posted to the
IETF repository.

Filename:        draft-liu-6man-ident-tunnel-packet-addr
Revision:        00
Title:           Identifying Addresses of IPv6 Tunnel Packets at Tunnel
Exit-point
Creation date:   2013-10-21
Group:           Individual Submission
Number of pages: 6
URL:
http://www.ietf.org/internet-drafts/draft-liu-6man-ident-tunnel-packet-addr-00.txt
Status:
http://datatracker.ietf.org/doc/draft-liu-6man-ident-tunnel-packet-addr
Htmlized:
http://tools.ietf.org/html/draft-liu-6man-ident-tunnel-packet-addr-00


Abstract:
   In the networks where IPv6 tunneling is used, it is not specific
   about how a tunnel end-node identifies the received tunnel packets by
   checking the destination and source addresses.  when the tunnel end-
   node is configured with multiple IPv6 addresses or multiple IPv6
   tunnel instances, such identification is necessary.  This document
   describes the problem and defines the behavior of IPv6 tunnel end-
   nodes about identifying tunnel packets.




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

--047d7bdc8afe980cf404e946d7c7
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Dear all,</div><div><br></div><div>We have submitted =
a new draft proposes how a IPv6 tunnel node identifies inbound tunnel packe=
ts.</div><div><br></div><div>We appreciate any comments and questions.</div=
>

<div><br></div><div>Cong Liu</div><br><div class=3D"gmail_quote">----------=
 Forwarded message ----------<br>From: <b class=3D"gmail_sendername"></b> <=
span dir=3D"ltr">&lt;<a href=3D"mailto:internet-drafts@ietf.org">internet-d=
rafts@ietf.org</a>&gt;</span><br>

Date: 2013/10/22<br>Subject: New Version Notification for draft-liu-6man-id=
ent-tunnel-packet-addr-00.txt<br>To: Jianping Wu &lt;<a href=3D"mailto:jian=
ping@cernet.edu.cn">jianping@cernet.edu.cn</a>&gt;, Cong Liu &lt;<a href=3D=
"mailto:gnocuil@gmail.com">gnocuil@gmail.com</a>&gt;, Yong Cui &lt;<a href=
=3D"mailto:yong@csnet1.cs.tsinghua.edu.cn">yong@csnet1.cs.tsinghua.edu.cn</=
a>&gt;<br>

<br><br><br>
A new version of I-D, draft-liu-6man-ident-tunnel-packet-addr-00.txt<br>
has been successfully submitted by Jianping Wu and posted to the<br>
IETF repository.<br>
<br>
Filename: =A0 =A0 =A0 =A0draft-liu-6man-ident-tunnel-packet-addr<br>
Revision: =A0 =A0 =A0 =A000<br>
Title: =A0 =A0 =A0 =A0 =A0 Identifying Addresses of IPv6 Tunnel Packets at =
Tunnel Exit-point<br>
Creation date: =A0 2013-10-21<br>
Group: =A0 =A0 =A0 =A0 =A0 Individual Submission<br>
Number of pages: 6<br>
URL: =A0 =A0 =A0 =A0 =A0 =A0 <a href=3D"http://www.ietf.org/internet-drafts=
/draft-liu-6man-ident-tunnel-packet-addr-00.txt" target=3D"_blank">http://w=
ww.ietf.org/internet-drafts/draft-liu-6man-ident-tunnel-packet-addr-00.txt<=
/a><br>
Status: =A0 =A0 =A0 =A0 =A0<a href=3D"http://datatracker.ietf.org/doc/draft=
-liu-6man-ident-tunnel-packet-addr" target=3D"_blank">http://datatracker.ie=
tf.org/doc/draft-liu-6man-ident-tunnel-packet-addr</a><br>
Htmlized: =A0 =A0 =A0 =A0<a href=3D"http://tools.ietf.org/html/draft-liu-6m=
an-ident-tunnel-packet-addr-00" target=3D"_blank">http://tools.ietf.org/htm=
l/draft-liu-6man-ident-tunnel-packet-addr-00</a><br>
<br>
<br>
Abstract:<br>
=A0 =A0In the networks where IPv6 tunneling is used, it is not specific<br>
=A0 =A0about how a tunnel end-node identifies the received tunnel packets b=
y<br>
=A0 =A0checking the destination and source addresses. =A0when the tunnel en=
d-<br>
=A0 =A0node is configured with multiple IPv6 addresses or multiple IPv6<br>
=A0 =A0tunnel instances, such identification is necessary. =A0This document=
<br>
=A0 =A0describes the problem and defines the behavior of IPv6 tunnel end-<b=
r>
=A0 =A0nodes about identifying tunnel packets.<br>
<br>
<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
The IETF Secretariat<br>
<br>
</div><br></div>

--047d7bdc8afe980cf404e946d7c7--

From gnocuil@gmail.com  Mon Oct 21 14:22:56 2013
Return-Path: <gnocuil@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEFEA11E8416 for <ipv6@ietfa.amsl.com>; Mon, 21 Oct 2013 14:22:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rZt5JuvXb1Wv for <ipv6@ietfa.amsl.com>; Mon, 21 Oct 2013 14:22:56 -0700 (PDT)
Received: from mail-qe0-x233.google.com (mail-qe0-x233.google.com [IPv6:2607:f8b0:400d:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 94ACE11E8453 for <ipv6@ietf.org>; Mon, 21 Oct 2013 14:22:51 -0700 (PDT)
Received: by mail-qe0-f51.google.com with SMTP id q19so4231610qeb.10 for <ipv6@ietf.org>; Mon, 21 Oct 2013 14:22:50 -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 :content-type; bh=JPPBfNsOl0WkcockYlSzgSUJK64eXm2SSg/xHbu8Nig=; b=fEgtNlfUzqIEDYqJn7Nra1DxF1Ej59Gj/EQPWxpn6n0Qh6N8j8k/e4p5almuRFM6gg c9FAtnq31kGbT4Q1JUGWuPBV2ytrpdNf6Atn9TK2lR736bbJbKOOLgd+KCPYRrNllT8N wvBeBpFjPns/o7dFCdT323C+uNPvquc5QO92jz/15R6r0zdedD9kclXABApSVu72KBls 3FeREDinB42IIG5ML3TxEz44WWH9S+F/Qh2v+d49x6hkPSJIjt0++OYTm0blrr85WMUY emieof7uz8kmWwjwg81GLl3e0jI2M8a2W+j0RL73XrfAi48Dya1wS0X1LjSr6cUOd/nv /bUw==
X-Received: by 10.49.12.14 with SMTP id u14mr25526506qeb.74.1382390570888; Mon, 21 Oct 2013 14:22:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.96.185.33 with HTTP; Mon, 21 Oct 2013 14:22:30 -0700 (PDT)
In-Reply-To: <20131021173916.32521.19650.idtracker@ietfa.amsl.com>
References: <20131021173916.32521.19650.idtracker@ietfa.amsl.com>
From: Cong Liu <gnocuil@gmail.com>
Date: Tue, 22 Oct 2013 05:22:30 +0800
Message-ID: <CAF+sHxE=H+7CJi7mL8rcamSeCUZqtm6rht4JwUdS2YYkVyyxQw@mail.gmail.com>
Subject: Fwd: New Version Notification for draft-liu-6man-tunnel-mtu-config-00.txt
To: ipv6 <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b6daa48eb348c04e946e225
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Oct 2013 21:22:57 -0000

--047d7b6daa48eb348c04e946e225
Content-Type: text/plain; charset=ISO-8859-1

Dear all,

We have submitted a new draft about IPv6 tunnel MTU issues.

We appreciate any comments and questions.

Cong Liu


---------- Forwarded message ----------
From: <internet-drafts@ietf.org>
Date: 2013/10/22
Subject: New Version Notification for
draft-liu-6man-tunnel-mtu-config-00.txt
To: Cong Liu <gnocuil@gmail.com>, Yong Cui <yong@csnet1.cs.tsinghua.edu.cn>



A new version of I-D, draft-liu-6man-tunnel-mtu-config-00.txt
has been successfully submitted by Yong Cui and posted to the
IETF repository.

Filename:        draft-liu-6man-tunnel-mtu-config
Revision:        00
Title:           IPv6 Tunnel MTU Configuration
Creation date:   2013-10-21
Group:           Individual Submission
Number of pages: 5
URL:
http://www.ietf.org/internet-drafts/draft-liu-6man-tunnel-mtu-config-00.txt
Status:
http://datatracker.ietf.org/doc/draft-liu-6man-tunnel-mtu-config
Htmlized:
http://tools.ietf.org/html/draft-liu-6man-tunnel-mtu-config-00


Abstract:
   It is not specific about how to decide IPv6 tunnel MTU in IPv6
   tunneling mechanisms in some situations.  This document describes the
   problem and provides a general solution to decide tunnel MTU value.




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

--047d7b6daa48eb348c04e946e225
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Dear all,<br><br>We have submitted a new draft about IPv6 =
tunnel MTU issues.<br><br>We appreciate any comments and questions.<br><br>=
Cong Liu<br><br><br>---------- Forwarded message ----------<br>From: &lt;<a=
 href=3D"mailto:internet-drafts@ietf.org" target=3D"_blank">internet-drafts=
@ietf.org</a>&gt;<br>


Date: 2013/10/22<br>Subject: New Version Notification for draft-liu-6man-tu=
nnel-mtu-config-00.txt<br>To: Cong Liu &lt;<a href=3D"mailto:gnocuil@gmail.=
com" target=3D"_blank">gnocuil@gmail.com</a>&gt;, Yong Cui &lt;<a href=3D"m=
ailto:yong@csnet1.cs.tsinghua.edu.cn" target=3D"_blank">yong@csnet1.cs.tsin=
ghua.edu.cn</a>&gt;<br>


<br><br><br>A new version of I-D, draft-liu-6man-tunnel-mtu-config-00.txt<b=
r>has been successfully submitted by Yong Cui and posted to the<br>IETF rep=
ository.<br><br>Filename: =A0 =A0 =A0 =A0draft-liu-6man-tunnel-mtu-config<b=
r>Revision: =A0 =A0 =A0 =A000<br>


Title: =A0 =A0 =A0 =A0 =A0 IPv6 Tunnel MTU Configuration<br>Creation date: =
=A0 2013-10-21<br>Group: =A0 =A0 =A0 =A0 =A0 Individual Submission<br>Numbe=
r of pages: 5<br>URL: =A0 =A0 =A0 =A0 =A0 =A0 <a href=3D"http://www.ietf.or=
g/internet-drafts/draft-liu-6man-tunnel-mtu-config-00.txt" target=3D"_blank=
">http://www.ietf.org/internet-drafts/draft-liu-6man-tunnel-mtu-config-00.t=
xt</a><br>


Status: =A0 =A0 =A0 =A0 =A0<a href=3D"http://datatracker.ietf.org/doc/draft=
-liu-6man-tunnel-mtu-config" target=3D"_blank">http://datatracker.ietf.org/=
doc/draft-liu-6man-tunnel-mtu-config</a><br>Htmlized: =A0 =A0 =A0 =A0<a hre=
f=3D"http://tools.ietf.org/html/draft-liu-6man-tunnel-mtu-config-00" target=
=3D"_blank">http://tools.ietf.org/html/draft-liu-6man-tunnel-mtu-config-00<=
/a><br>


<br><br>Abstract:<br>=A0 =A0It is not specific about how to decide IPv6 tun=
nel MTU in IPv6<br>=A0 =A0tunneling mechanisms in some situations. =A0This =
document describes the<br>=A0 =A0problem and provides a general solution to=
 decide tunnel MTU value.<br>


<br><br><br><br>Please note that it may take a couple of minutes from the t=
ime of submission<br>until the htmlized version and diff are available at <=
a href=3D"http://tools.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br>

<br>The IETF Secretariat<br>
<br></div>

--047d7b6daa48eb348c04e946e225--

From internet-drafts@ietf.org  Mon Oct 21 15:42:31 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78ADA11E87AA; Mon, 21 Oct 2013 15:42:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.571
X-Spam-Level: 
X-Spam-Status: No, score=-102.571 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FRhVmNPc-QJG; Mon, 21 Oct 2013 15:42:31 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AD36E11E87AC; Mon, 21 Oct 2013 15:42:15 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-impatient-nud-07.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131021224215.32495.73073.idtracker@ietfa.amsl.com>
Date: Mon, 21 Oct 2013 15:42:15 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Oct 2013 22:42:31 -0000

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           : Neighbor Unreachability Detection is too impatient
	Author(s)       : Erik Nordmark
                          Igor Gashinsky
	Filename        : draft-ietf-6man-impatient-nud-07.txt
	Pages           : 9
	Date            : 2013-10-21

Abstract:
   IPv6 Neighbor Discovery includes Neighbor Unreachability Detection.
   That function is very useful when a host has an alternative neighbor,
   for instance when there are multiple default routers, since it allows
   the host to switch to the alternative neighbor in short time.  This
   time is 3 seconds after the node starts probing by default.  However,
   if there are no alternative neighbors, this is far too impatient.
   This document specifies relaxed rules for Neighbor Discovery
   retransmissions that allow an implementation to choose different
   timeout behavior based on whether or not there are alternative
   neighbors.  This document updates RFC 4861.


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

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

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-impatient-nud-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 nalini.elkins@insidethestack.com  Mon Oct 21 15:58:39 2013
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38F2311E87BB for <ipv6@ietfa.amsl.com>; Mon, 21 Oct 2013 15:58:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.181
X-Spam-Level: 
X-Spam-Status: No, score=-1.181 tagged_above=-999 required=5 tests=[AWL=-1.181, BAYES_50=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c0X8AseoTXFB for <ipv6@ietfa.amsl.com>; Mon, 21 Oct 2013 15:58:39 -0700 (PDT)
Received: from nm4-vm1.access.bullet.mail.bf1.yahoo.com (nm4-vm1.access.bullet.mail.bf1.yahoo.com [216.109.114.112]) by ietfa.amsl.com (Postfix) with ESMTP id E4F8D11E8299 for <ipv6@ietf.org>; Mon, 21 Oct 2013 15:58:22 -0700 (PDT)
Received: from [66.196.81.163] by nm4.access.bullet.mail.bf1.yahoo.com with NNFMP; 21 Oct 2013 22:58:22 -0000
Received: from [66.196.81.128] by tm9.access.bullet.mail.bf1.yahoo.com with NNFMP; 21 Oct 2013 22:58:22 -0000
Received: from [127.0.0.1] by omp1004.access.mail.bf1.yahoo.com with NNFMP; 21 Oct 2013 22:58:22 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 16764.92499.bm@omp1004.access.mail.bf1.yahoo.com
Received: (qmail 23180 invoked by uid 60001); 21 Oct 2013 22:58:21 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1382396301; bh=gz7bsWA3BKYe3p8KchJBGACAUiJhFU+zTjXy2NOwom0=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=qdS7Q3Cy6lMzupXUJmmljNB/YrBNx/+yUBc9iKsGxxBNs+QEs/TRb6JXap2xfY/PkeeysCwQHmkjaMwChshIp6i3ToV3ebMokr17E2MESN6uvj8MCPhtQfUaNmCMWSfJQ6rK6WeNIstMipirz3dNoU36Sp54UDZtl8xIFXOlPhM=
X-YMail-OSG: 3qSutDkVM1m_rKOwD95QcNtpkvhcHeb9fl8kjbNU_zTepCz HpYBLoU8elofJ3oS18.BqVNg3h0TwGU5CANcnT30cosgpoOj1TSWC2l6vJX9 QFFrri7PMeDKffpZuH7mWWphetrFM6HF_vtVjXdEoRTmgmsGsnf00eGO2FAN l_a3a5fvrZZhH2b3DQPd06lhJIHNz.YKEjgpzggYc6jP7eJrxGnsJONWudMI tcqOh4R0NbruuSL9Q77wuqbxplQBmXM2dVQvLeKAhpGEPbkX16cR70wEf3aD WeoDj_HhOyKW.JLB6lKl4vY8vWYjE01qKOTYTbebOFmeM3RA.7gGGNsIaadq WPbIiC9BI8yLhGpaqXmVwgegUX84grXgjG1jpeYaguRYMfohIwQeWE_Xm0Vx SJvQE4RQCF4u2wFTfwVcpCduWql6lWyhAOmgBJXEZEWlt0HivW7Y3R6UJEGE EiNcNcAskPO9ZAoR7PdyPPTT.62TL5QJ3yzspqcO0sEJTkGVlSCRejis3XT. jGnv6I6YKq3lRqgv4Fs8JcEc_nc6HGHXwevqBtG2UF5ky5khqh3MaEHDspoc oSWu003NfORL2l8w-
Received: from [24.130.37.147] by web2801.biz.mail.ne1.yahoo.com via HTTP; Mon, 21 Oct 2013 15:58:20 PDT
X-Rocket-MIMEInfo: 002.001, Cj7CoDEpIGVuY29kaW5nIGhhcyB0byBiZSBmYXN0LCBidXQgZGVjb2RpbmcgZG9lcyBub3QKClRydWUKCj7CoDIpIGEgbm9kZSdzIGNsb2NrIGNvdWxkIGJlIGVpdGhlciBpbiBvdXIgb3V0IG9mIHN5bmNoIHdpdGggc29tZSBub3Rpb25hbAo.wqBtYXN0ZXIgY2xvY2sgKGUuZy4gdmlhIE5UUCkKPsKgMykgdHdvIGNsb2NrcyBjb3VsZCBiZSBpbiBzeW5jaCB0byBhIG1hc3RlciBzb3VyY2UsIGJ1dCB0aGUgbWFzdGVyCj7CoHNvdXJjZXMgbWF5IHRoZW1zZWx2ZXMgbm90IHNoYXJlIGEgY29tbW9uIHNvdXJjZSABMAEBAQE-
X-Mailer: YahooMailWebService/0.8.160.587
References: <20131017032024.5051.20799.idtracker@ietfa.amsl.com> <1381980305.36254.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com> <5263C783.1080001@globis.net> 
Message-ID: <1382396300.22968.YahooMailNeo@web2801.biz.mail.ne1.yahoo.com>
Date: Mon, 21 Oct 2013 15:58:20 -0700 (PDT)
From: Nalini Elkins <nalini.elkins@insidethestack.com>
Subject: Re: [v6ops] Fw: New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-04.txt
To: Ray Hunter <v6ops@globis.net>
In-Reply-To: <5263C783.1080001@globis.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: v6ops WG <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Nalini Elkins <nalini.elkins@insidethestack.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: Mon, 21 Oct 2013 22:58:39 -0000

=0A>=A01) encoding has to be fast, but decoding does not=0A=0ATrue=0A=0A>=
=A02) a node's clock could be either in our out of synch with some notional=
=0A>=A0master clock (e.g. via NTP)=0A>=A03) two clocks could be in synch to=
 a master source, but the master=0A>=A0sources may themselves not share a c=
ommon source (one sourced from GPS,=0A>one from DCF77)=0A>4) the key to bei=
ng able to perform the end to end calculations is=0A>whether two communicat=
ing nodes are synchronised to the same master=0A>clock (within some level o=
f error/jitter)=0A>5) the absolute time is not particularly important=0A=0A=
=0AThis is true for PDM 1 only. =A0PDM 2 does not require time synchronizat=
ion.=0A=0A>=A0Q1. Why do you want to encode differences as deltas in the ca=
se of an=A0unsynchronised/ free running clock?=0A>=A0Isn't that slow, and d=
ifficult for hardware implementations to achieve=A0(e.g. TCP offload)?=A0Do=
esn't it also require maintaining large amounts of state in the=A0sending n=
ode.=0A>=0A=0A1.=A0I think that it is going to be interesting to see how ha=
rdware is going to handle TCP offload with IPv6 extension headers. =A0 I do=
 not see why PDM 2 would be so much harder than PDM 1 for an OS.=0ACan you =
tell me which end host operating systems are doing TCP offload in hardware?=
 =A0=A0=0A=0AI know some OS's which process TCP segmentation in hardware. =
=A0 =A0But at this point, the packet is already crafted. =A0Also some do IP=
 checksum offload in hardware but that does not apply to IPv6 as there is n=
o IP header checksum.=0A=0A=0A2. =A0End hosts already maintain quite a bit =
of state. =A0Every OS has control blocks to handle events such as TCP dupli=
cate packets, round trip time, congestion window, etc. =A0 We are NOT sugge=
sting=0Athat the PDM headers be used in middle boxes. =A0That is, we are NO=
T asking routers to maintain state.=0A=0A=0A>=A0Why not just encode the tim=
estamp as-is and perform the appropriate=A0difference calculation during de=
coding?=0A=0AIf clocks are out of synch, you could end up having it look li=
ke you received the packet before you sent it.=0A=0A>=A0Q2. Why do you need=
 two separate packet formats at all?=0A=0A>=A0Why not have a common format =
for all cases, containing a timestamp based=0A>on the local clock, plus an =
optional field containing a flag that states=0A>if the local timestamp is c=
oordinated to some master clock, plus an=0A>identifier for the master clock=
.=0A=0A>You could then encode whether a node had a free-running clock (case=
 2),=0A>a synchronised clock (case 1), and whether it was synched via NTP t=
o=0A>some stratum 0 source e.g. GPS, and also some identification of the=0A=
>stratum 1 source (IPv6 address).=0A=0A>Two communicating nodes could then =
use e.g. NTP trace to see if they=0A>shared a common clock source or not, b=
efore performing their calculations.=0A=0AWe are trying to craft a solution=
 with PDM 2 for those situations where time synchronization is not practica=
l, possible or desired.=0A

From internet-drafts@ietf.org  Mon Oct 21 16:38:44 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8294511E881B; Mon, 21 Oct 2013 16:38:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.572
X-Spam-Level: 
X-Spam-Status: No, score=-102.572 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cxx8NvfS6Fe5; Mon, 21 Oct 2013 16:38:43 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6108411E8814; Mon, 21 Oct 2013 16:38:28 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-resilient-rs-02.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131021233827.32495.34424.idtracker@ietfa.amsl.com>
Date: Mon, 21 Oct 2013 16:38:27 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Oct 2013 23:38:45 -0000

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           : Packet loss resiliency for Router Solicitations
	Author(s)       : Suresh Krishnan
                          Dmitry Anipko
                          Dave Thaler
	Filename        : draft-ietf-6man-resilient-rs-02.txt
	Pages           : 7
	Date            : 2013-10-21

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-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-resilient-rs-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 samita.chakrabarti@ericsson.com  Mon Oct 21 16:44:42 2013
Return-Path: <samita.chakrabarti@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC27411E82C9 for <ipv6@ietfa.amsl.com>; Mon, 21 Oct 2013 16:44:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.572
X-Spam-Level: 
X-Spam-Status: No, score=-2.572 tagged_above=-999 required=5 tests=[AWL=0.027,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sJvdsC6TOgEX for <ipv6@ietfa.amsl.com>; Mon, 21 Oct 2013 16:44:35 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 46BA511E862B for <6man@ietf.org>; Mon, 21 Oct 2013 16:44:30 -0700 (PDT)
X-AuditID: c618062d-b7fda8e0000024c6-31-5265bc5c86a7
Received: from EUSAAHC002.ericsson.se (Unknown_Domain [147.117.188.78]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id FB.18.09414.D5CB5625; Tue, 22 Oct 2013 01:44:29 +0200 (CEST)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC002.ericsson.se ([147.117.188.78]) with mapi id 14.02.0328.009; Mon, 21 Oct 2013 19:44:28 -0400
From: Samita Chakrabarti <samita.chakrabarti@ericsson.com>
To: "6man@ietf.org" <6man@ietf.org>
Subject: Submitted draft-chakrabarti-nordmark-6man-efficient-nd-04.txt
Thread-Topic: Submitted draft-chakrabarti-nordmark-6man-efficient-nd-04.txt
Thread-Index: Ac7OtuxagWIUeP5ERjqo332IjGUxzQ==
Date: Mon, 21 Oct 2013 23:44:28 +0000
Message-ID: <ECA43DA70480A3498E43C3471FB2E1F01C0EEA05@eusaamb103.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.135]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrOLMWRmVeSWpSXmKPExsUyuXSPn27sntQgg427xC1WrrjLZLFg+VIW i5edG9gsZkx5x+jA4jHl90ZWjyVLfjJ5bNy+jsXjaXczSwBLFJdNSmpOZllqkb5dAldG1/w5 jAWzBCtmv8loYHwg0MXIySEhYCJx8sosVghbTOLCvfVsXYxcHEICRxklfs6+xwzhLGeUuLPr KhNIFZuAlURH7x52EFtEQFmi7egRJpAiZoHpjBItJ+YzgiSEBdwkvt39wQJR5C0xY9pDoDgH kK0nsfJJIEiYRUBV4l37B7ASXgFfiWMtk5hBbEagK76fWgO2i1lAXOLWk/lMENcJSCzZc54Z whaVePn4H9TVyhLf5zxiARnPLKApsX6XPkSrosSU7ofsEOMFJU7OfMIygVFkFpKpsxA6ZiHp mIWkYwEjyypGjtLi1LLcdCODTYzAyDgmwaa7g3HPS8tDjNIcLErivF/eOgcJCaQnlqRmp6YW pBbFF5XmpBYfYmTi4JRqYFzesyvrl6vTrw6u6qQTIWkfOmQyhbzTthjuKm9yMndQc/vnnuT7 f+aH1ZsEL8rePRT3tftz5seZvk8DeGd/Ejt3IjaXVeSNz/w61RWRgReSxXp5nLYpLX4rGZ14 5K6ve3OoeUF6z9pb9Zq+l857i7H/8bJ3F1fu53v++OWv311FZ+Y4JjLuVmIpzkg01GIuKk4E AIG5u8JaAgAA
Cc: "pthubert@cisco.com" <pthubert@cisco.com>, "Erik Nordmark \(nordmark@sonic.net\)" <nordmark@sonic.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Oct 2013 23:44:43 -0000

U3VibWl0dGVkIGEgIHNsaWdodGx5IG1vZGlmaWVkIHZlcnNpb24gKDA0KSBvZiBFZmZpY2llbnQt
bmQgYmFzZWQgb24gZnVydGhlciBpbnB1dCBvbiB2ZXJzaW9uIDAzIDoNCg0KLS0gIEFkZGVkIGEg
cGxhY2UgaG9sZGVyIHNlY3Rpb24gb24gVlJSUCBpbnRlcmFjdGlvbiBbIENvLWF1dGhvcnMgdG8g
ZGlzY3VzcyBmdXJ0aGVyIG9uIHRoaXMgdG9waWMgcHJvcG9zZWQgYnkgTWFyayBaWlogU21pdGhd
DQotLSAgQ2xhcmlmaWVkIHRoYXQgdGhlIE5FQVIgcm91dGVyIGNhbiBkZW55IHJlZ2lzdHJhdGlv
biBpZiB0aGUgbmVpZ2hib3IgY2FjaGUgaXMgZnVsbA0KLS0gIENsYXJpZmllZCAgRUFIIChob3N0
KSBiZWhhdmlvciBvbiByZWdpc3RyYXRpb24gZGVuaWFsLg0KDQoNClRoYW5rcywNCi1TYW1pdGEN
Cg0KDQoNClVSTDogICAgICAgICAgICAgaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFm
dHMvZHJhZnQtY2hha3JhYmFydGktbm9yZG1hcmstNm1hbi1lZmZpY2llbnQtbmQtMDQudHh0DQoN
Cg0KQWJzdHJhY3Q6DQogICBJUHY2IE5laWdoYm9yIERpc2NvdmVyeSAoUkZDIDQ4NjEpIHByb3Rv
Y29sIGhhcyBiZWVuIGRlc2lnbmVkIGZvcg0KICAgbmVpZ2hib3IncyBhZGRyZXNzIHJlc29sdXRp
b24sIHVucmVhY2hhYmlsaXR5IGRldGVjdGlvbiwgYWRkcmVzcw0KICAgYXV0b2NvbmZpZ3VyYXRp
b24sIHJvdXRlciBhZHZlcnRpc2VtZW50IGFuZCBzb2xpY2l0YXRpb24uICBXaXRoIHRoZQ0KICAg
cHJvZ3Jlc3Mgb2YgSW50ZXJuZXQgYWRvcHRpb24gb24gdmFyaW91cyBpbmR1c3RyaWVzIGluY2x1
ZGluZyBob21lLA0KICAgd2lyZWxlc3MsIE0yTSBhbmQgY2VsbHVsYXIgbmV0d29ya3MgdGhlcmUg
aXMgYSBkZXNpcmUgZm9yIG9wdGltaXppbmcNCiAgIHRoZSBsZWdhY3kgSVB2NiBOZWlnaGJvciBE
aXNjb3ZlcnkgcHJvdG9jb2wuICBUaGlzIGRvY3VtZW50IGRlc2NyaWJlcw0KICAgYSBtZXRob2Qg
b2Ygb3B0aW1pemF0aW9uIGJ5IHJlZHVjaW5nIG11bHRpY2FzdCBtZXNzYWdlcyBhbmQNCiAgIGlu
dHJvZHVjaW5nIGFuIElQdjYgYWRkcmVzcyBSZWdpc3RyYXRpb24gbWVjaGFuaXNtLiAgVGhlIG9w
dGltaXphdGlvbg0KICAgb2YgSVB2NiBOZWlnaGJvciBEaXNjb3ZlcnkgcHJvdG9jb2wgaXMgdXNl
ZnVsIGZvciBXaXJsZXNzIGFuZCBsb3ctDQogICBwb3dlciBJUHY2IG5ldHdvcmtzIGFuZCBhcyB3
ZWxsIGFzIERhdGEgQ2VudGVycyBhbmQgSG9tZSBOZXR3b3Jrcy4NCiAgIFRoZSBzb2x1dGlvbiBp
cyBjYXBhYmxlIG9mIGhhbmRsaW5nIGV4aXN0aW5nIGxlZ2FjeSBJUHY2IG5vZGVzIGluIHRoZQ0K
ICAgbmV0d29yayB3aXRoIGxvY2FsIG1vYmlsaXR5Lg0KDQogICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgDQoNCg0KUGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBhIGNvdXBsZSBvZiBtaW51dGVz
IGZyb20gdGhlIHRpbWUgb2Ygc3VibWlzc2lvbiB1bnRpbCB0aGUgaHRtbGl6ZWQgdmVyc2lvbiBh
bmQgZGlmZiBhcmUgYXZhaWxhYmxlIGF0IHRvb2xzLmlldGYub3JnLg0KDQpUaGUgSUVURiBTZWNy
ZXRhcmlhdA0KDQo=

From ietf@rozanak.com  Mon Oct 21 16:47:14 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E474B11E8837 for <ipv6@ietfa.amsl.com>; Mon, 21 Oct 2013 16:47:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.995
X-Spam-Level: 
X-Spam-Status: No, score=-1.995 tagged_above=-999 required=5 tests=[AWL=0.604,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5xiTXByYBRTw for <ipv6@ietfa.amsl.com>; Mon, 21 Oct 2013 16:46:42 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id DDF8911E82C9 for <ipv6@ietf.org>; Mon, 21 Oct 2013 16:45:41 -0700 (PDT)
Received: from kopoli (g231251108.adsl.alicedsl.de [92.231.251.108]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0LyEBR-1Vk6at4AnF-015vP7; Mon, 21 Oct 2013 19:45:28 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: <ipv6@ietf.org>, <mcr@sandelman.ca>, "'Derek Atkins'" <derek@ihtfp.com>
Subject: I-D: draft-rafiee-6man-ssas  
Date: Tue, 22 Oct 2013 01:45:19 +0200
Message-ID: <023901ceceb7$9e750810$db5f1830$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac7Ot0IQfEkOMFEjSoOwvfwz7V+++A==
Content-Language: en-us
X-Provags-ID: V02:K0:vFT4+A0TejPJPICmaQ9HrxFxSdS39RzLPv8v0w5PW6D r0bevavCCD7NnrpdC+BLIQ8/ci4xIcS+kYaXwCWzVkTXg8ZSpc I/+PG2/06oU1Dp3mMev8pqtazciTL9EdjMLGBzkXY/WD3fAP43 YZ/L1PkdEn8WfPQApRq+AojkuUOjrIqn56FKRqgJ/T555WZDVL v3+JFpm7AzLzvJ/hmg1yD09fWHhPAgxE+7tpb2VEgTyq4gzh2x ZF5vOPfWe8cr8Eif6Ylc83rDuCEasxOd2GuKcex6bXyrgy2I8e jakG/XbK8U1DOoDnX5DsFTy9Ny1tBitl+ZTC2vH7bQeQ2MM82u foSWIuQw+lyySQgD/pBs=
Cc: Erik Nordmark <nordmark@sonic.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Oct 2013 23:47:15 -0000

I submitted new version of SSAS draft. I applied the comments received =
during last IETF meeting and off list comments. I also separated the =
rpki from this draft. I will submit the rpki as a new document.

Please share your comments :-)
Thanks,

-----------smile----------
Hosnieh
=E2=80=A6 success is a journey, not a destination=E2=80=A6.
You cannot change your destination overnight, but you can change your =
direction ... Focus on the journey



A new version of I-D, draft-rafiee-6man-ssas-06.txt has been =
successfully submitted by Hosnieh Rafiee and posted to the IETF =
repository.

Filename:	 draft-rafiee-6man-ssas
Revision:	 06
Title:		 A Simple Secure Address Generation Scheme for IPv6 =
AutoConfiguration (SSAS)
Creation date:	 2013-10-21
Group:		 Individual Submission
Number of pages: 15
URL:             =
http://www.ietf.org/internet-drafts/draft-rafiee-6man-ssas-06.txt
Status:          http://datatracker.ietf.org/doc/draft-rafiee-6man-ssas
Htmlized:        http://tools.ietf.org/html/draft-rafiee-6man-ssas-06
Diff:            =
http://www.ietf.org/rfcdiff?url2=3Ddraft-rafiee-6man-ssas-06

Abstract:
   The purpose of this document is to address the current problem
   inherent with using of Cryptographically Generated Addresses (CGA)
   [RFC3972] and introduces a new algorithm that can eliminate the cost
   of CGA algorithm. This algorithm also responds to the security issues
   (IP spoofing) exists in Privacy Extension [RFC4941] document by
   integrating privacy with the security.



                                                                         =
        =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.

The IETF Secretariat


From v6ops@globis.net  Mon Oct 21 23:10:16 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7868011E815B; Mon, 21 Oct 2013 23:10:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SJFbTpG883gE; Mon, 21 Oct 2013 23:10:15 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 6ED2511E8160; Mon, 21 Oct 2013 23:10:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 823348700BD; Tue, 22 Oct 2013 08:10:14 +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 Rc69tpUhZj34; Tue, 22 Oct 2013 08:10:14 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 0222387005F; Tue, 22 Oct 2013 08:10:13 +0200 (CEST)
Message-ID: <526616C4.40304@globis.net>
Date: Tue, 22 Oct 2013 08:10:12 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Nalini Elkins <nalini.elkins@insidethestack.com>
Subject: Re: [v6ops] Fw: New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-04.txt
References: <20131017032024.5051.20799.idtracker@ietfa.amsl.com> <1381980305.36254.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com> <5263C783.1080001@globis.net> <1382396300.22968.YahooMailNeo@web2801.biz.mail.ne1.yahoo.com>
In-Reply-To: <1382396300.22968.YahooMailNeo@web2801.biz.mail.ne1.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: v6ops WG <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 22 Oct 2013 06:10:16 -0000

> Nalini Elkins <mailto:nalini.elkins@insidethestack.com>
> 22 October 2013 00:58
>>  1) encoding has to be fast, but decoding does not
>
> True
>
>>  2) a node's clock could be either in our out of synch with some notional
>>  master clock (e.g. via NTP)
>>  3) two clocks could be in synch to a master source, but the master
>>  sources may themselves not share a common source (one sourced from GPS,
>> one from DCF77)
>> 4) the key to being able to perform the end to end calculations is
>> whether two communicating nodes are synchronised to the same master
>> clock (within some level of error/jitter)
>> 5) the absolute time is not particularly important
>
>
> This is true for PDM 1 only.  PDM 2 does not require time synchronization.
>
>>  Q1. Why do you want to encode differences as deltas in the case of an unsynchronised/ free running clock?
>>  Isn't that slow, and difficult for hardware implementations to achieve (e.g. TCP offload)? Doesn't it also require maintaining large amounts of state in the sending node.
>>
>
> 1. I think that it is going to be interesting to see how hardware is going to handle TCP offload with IPv6 extension headers.   I do not see why PDM 2 would be so much harder than PDM 1 for an OS.
> Can you tell me which end host operating systems are doing TCP offload in hardware?   
IMHO Not a relevant question. As a standards body we should be looking
to the future. There are many operations that are delegated to microcode.

If you specified the packet with one single way of encapsulating
timestamps, then hardware or interface microcode could add the timestamp
at the last possible moment before the packet reached the wire, without
having to examine the original packet contents, or knowing the context
of the communicating nodes. I think that's very desirable.
> I know some OS's which process TCP segmentation in hardware.    But at this point, the packet is already crafted.  Also some do IP checksum offload in hardware but that does not apply to IPv6 as there is no IP header checksum.
>
>
> 2.  End hosts already maintain quite a bit of state.  Every OS has control blocks to handle events such as TCP duplicate packets, round trip time, congestion window, etc.   We are NOT suggesting
> that the PDM headers be used in middle boxes.  That is, we are NOT asking routers to maintain state.
So what? Why add to the problem?

Why does the timestamp require synchronisation with that other TCP state?

Isn't it better to define a solution that is independent of the upper
layer header transport protocol?

<heresy>  Why not allow middleboxes (or node hardware) to insert the
timestamp header on the fly?</heresy>
>
>>  Why not just encode the timestamp as-is and perform the appropriate difference calculation during decoding?
>
> If clocks are out of synch, you could end up having it look like you received the packet before you sent it.

No. I'm not suggesting you use the same decoding algorithm: only that
you define a single common encoding algorithm that combines all the
information required for PDM 1 and PDM 2 calculations. Having to chose
which packet encoding to use in advance is problematic IMHO.



>>  Q2. Why do you need two separate packet formats at all?
>
>>  Why not have a common format for all cases, containing a timestamp based
>> on the local clock, plus an optional field containing a flag that states
>> if the local timestamp is coordinated to some master clock, plus an
>> identifier for the master clock.
>
>> You could then encode whether a node had a free-running clock (case 2),
>> a synchronised clock (case 1), and whether it was synched via NTP to
>> some stratum 0 source e.g. GPS, and also some identification of the
>> stratum 1 source (IPv6 address).
>
>> Two communicating nodes could then use e.g. NTP trace to see if they
>> shared a common clock source or not, before performing their calculations.
>
> We are trying to craft a solution with PDM 2 for those situations where time synchronization is not practical, possible or desired.

I understand the aim, but let me ask my question a different way.

Imagine there are nodes A&B that with clocks synched to DCF77.
Imagine there are nodes C&D that with clocks  synched to GPS.
Node E has free running clock (possibly because the GPS receiver is down).

Which packet format PDM type 1 or PDM type 2 do you use between each
pair of nodes, and how does the sending node know that?

Scale this solution to 100K hosts.
>
> ------------------------------------------------------------------------


-- 
Regards,
RayH


From leo.liubing@huawei.com  Tue Oct 22 00:46:55 2013
Return-Path: <leo.liubing@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9220411E8487 for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 00:46:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.47
X-Spam-Level: 
X-Spam-Status: No, score=-6.47 tagged_above=-999 required=5 tests=[AWL=0.129,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id POelKTI9I6VX for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 00:46:51 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id DBE2811E8349 for <ipv6@ietf.org>; Tue, 22 Oct 2013 00:46:47 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AXB02330; Tue, 22 Oct 2013 07:46:42 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.146.0; Tue, 22 Oct 2013 08:46:25 +0100
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.146.0; Tue, 22 Oct 2013 08:46:34 +0100
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.141]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0146.000; Tue, 22 Oct 2013 15:46:27 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: 6man WG <ipv6@ietf.org>
Subject: ND Option for NMS Discovery-//FW: New Version Notification for draft-liu-6man-nd-nms-discovery-00.txt
Thread-Topic: ND Option for NMS Discovery-//FW: New Version Notification for draft-liu-6man-nd-nms-discovery-00.txt
Thread-Index: AQHOzvrQkYnZSQrQ8EG70riP25iHvQ==
Date: Tue, 22 Oct 2013 07:46:27 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC189@nkgeml506-mbx.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.132]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 22 Oct 2013 07:46:55 -0000

SGksIERlYXIgQWxsDQoNCkkgc3VibWl0dGVkIGEgbmV3IGRyYWZ0LCB3aGljaCBpcyByZWdhcmRp
bmcgdXNpbmcgTkQgb3B0aW9uIHRvIGxldCB0aGUgZGV2aWNlcyBsZWFybiBOTVMgKE5ldHdvcmsg
TWFuYWdlbWVudCBTeXN0ZW0pIHNlcnZlcidzIGFkZHJlc3Mgd2hlbiB0aGV5IGdldCBvbmxpbmUu
DQoNCkFzIHdlIGtub3csIGl0IGlzIG5lY2Vzc2FyeSBmb3IgdGhlIGRldmljZXMgaW4gSVNQIG5l
dHdvcmtzIHRvIGJlIG1hbmFnZWQgYnkgTk1TIChpdCBtaWdodCBhbHNvIG5lY2Vzc2FyeSBmb3Ig
c29tZSBlbnRlcnByaXNlIG5ldHdvcmtzKS4NClNvIHRoZXJlIGlzIGEgcHJvYmxlbSBvZiBob3cg
dG8gZGlzY292ZXIgdGhlIE5NUyBzZXJ2ZXIgZm9yIHRoZSBkZXZpY2VzLiBUaGUgdHJhZGl0aW9u
YWwgbWV0aG9kcyBhcmUgdGhyb3VnaCBwcmUvbWFudWFsIGNvbmZpZyBvciBhIGRlZGljYXRlZCBs
b2dpY2FsIG1hbmFnZW1lbnQgbmV0d29yayB0aHJvdWdoIHdoaWNoIHRoZSBOTVMgY291bGQgZGlz
Y292ZXIgdGhlIG5ldyBkZXZpY2VzIHBlcmlvZGljYWxseS4gDQoNClRoaXMgZHJhZnQgcHJvcG9z
ZXMgYSBuZXcgbWV0aG9kIGZvciB0aGUgZGV2aWNlcyB0byBhY3RpdmVseSBkaXNjb3ZlciB0aGUg
Tk1TIHNlcnZlci4gV2hlbiBhIGRldmljZXMgZ2V0cyBvbmxpbmUsIGl0IGNvdWxkIGxlYXJuIHRo
ZSBOTVMgc2VydmVyJ3MgYWRkcmVzcyBmcm9tIGl0cyBuZWlnaGJvciB0aHJvdWdoIHRoZSBORCBv
cHRpb24gZGVmaW5lZCBpbiB0aGlzIGRvY3VtZW50LiBUaGUgaWRlYSBpcyBzaW1wbGUgYW5kIGVh
c3kgdG8gYmUgaW1wbGVtZW50ZWQsIGl0IGlzIGEgZ29vZCBsZXZlcmFnZSBvZiBJUHY2IGF1dG9t
YXRpYyBmZWF0dXJlcy4gQW5kIHRoZSBhdXRob3IgYmVsaWV2ZXMgaXQgaXMgdXNlZnVsIGluIHNv
bWUgc2NlbmFyaW9zLCBlc3BlY2lhbGx5IGZvciBzb21lIHplcm8tY29uZmlnIHRlY2hub2xvZ2ll
cy4NCg0KWW91ciBjb21tZW50cyB3b3VsZCBiZSBhcHByZWNpYXRlZCBtdWNoLg0KDQpCZXN0IHJl
Z2FyZHMsDQpCaW5nDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBpbnRlcm5l
dC1kcmFmdHNAaWV0Zi5vcmcgW21haWx0bzppbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmddIA0KU2Vu
dDogTW9uZGF5LCBPY3RvYmVyIDIxLCAyMDEzIDc6MDIgUE0NClRvOiBMaXViaW5nIChMZW8pDQpT
dWJqZWN0OiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIGRyYWZ0LWxpdS02bWFuLW5kLW5t
cy1kaXNjb3ZlcnktMDAudHh0DQoNCg0KQSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LWxpdS02
bWFuLW5kLW5tcy1kaXNjb3ZlcnktMDAudHh0DQpoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0
dGVkIGJ5IEJpbmcgTGl1IGFuZCBwb3N0ZWQgdG8gdGhlDQpJRVRGIHJlcG9zaXRvcnkuDQoNCkZp
bGVuYW1lOgkgZHJhZnQtbGl1LTZtYW4tbmQtbm1zLWRpc2NvdmVyeQ0KUmV2aXNpb246CSAwMA0K
VGl0bGU6CQkgSVB2NiBORCBPcHRpb24gZm9yIE5ldHdvcmsgTWFuYWdlbWVudCBTZXJ2ZXIgRGlz
Y292ZXJ5DQpDcmVhdGlvbiBkYXRlOgkgMjAxMy0xMC0yMQ0KR3JvdXA6CQkgSW5kaXZpZHVhbCBT
dWJtaXNzaW9uDQpOdW1iZXIgb2YgcGFnZXM6IDcNClVSTDogICAgICAgICAgICAgaHR0cDovL3d3
dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtbGl1LTZtYW4tbmQtbm1zLWRpc2NvdmVy
eS0wMC50eHQNClN0YXR1czogICAgICAgICAgaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2Rv
Yy9kcmFmdC1saXUtNm1hbi1uZC1ubXMtZGlzY292ZXJ5DQpIdG1saXplZDogICAgICAgIGh0dHA6
Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWxpdS02bWFuLW5kLW5tcy1kaXNjb3ZlcnktMDAN
Cg0KDQpBYnN0cmFjdDoNCiAgIFRoaXMgZG9jdW1lbnQgaW50cm9kdWNlcyBhIG1lY2hhbmlzbSBm
b3IgZGV2aWNlcyB0byBhY3RpdmVseSBsZWFybg0KICAgdGhlIE5NUyBzZXJ2ZXIgYWRkcmVzcyBm
cm9tIHRoZSBuZWlnaGJvcnMgdGhyb3VnaCBJUHY2IE5EIHByb3RvY29sDQogICBleHRlbnNpb24u
IEl0IGlzIGEgZ29vZCBsZXZlcmFnZSBvZiBJUHY2IGF1dG9tYXRpYyBmZWF0dXJlcy4NCg0KICAg
VGhpcyBkb2N1bWVudCBvbmx5IGRpc2N1c3NlcyBwcm9ibGVtL3NvbHV0aW9uIHdpdGhpbiB0aGUg
SVB2Ni1vbmx5DQogICBuZXR3b3Jrcy9wbGFuZS4NCg0KICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
IA0KDQoNClBsZWFzZSBub3RlIHRoYXQgaXQgbWF5IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBm
cm9tIHRoZSB0aW1lIG9mIHN1Ym1pc3Npb24NCnVudGlsIHRoZSBodG1saXplZCB2ZXJzaW9uIGFu
ZCBkaWZmIGFyZSBhdmFpbGFibGUgYXQgdG9vbHMuaWV0Zi5vcmcuDQoNClRoZSBJRVRGIFNlY3Jl
dGFyaWF0DQoNCg==

From swmike@swm.pp.se  Tue Oct 22 01:16:00 2013
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02CC611E8303 for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 01:16:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.558
X-Spam-Level: 
X-Spam-Status: No, score=-5.558 tagged_above=-999 required=5 tests=[AWL=0.691,  BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 67fbYi+5mP6S for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 01:15:55 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) by ietfa.amsl.com (Postfix) with ESMTP id A34D911E8180 for <ipv6@ietf.org>; Tue, 22 Oct 2013 01:15:55 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 9BB699C; Tue, 22 Oct 2013 10:15:54 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 984139A; Tue, 22 Oct 2013 10:15:54 +0200 (CEST)
Date: Tue, 22 Oct 2013 10:15:54 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "Liubing (Leo)" <leo.liubing@huawei.com>
Subject: Re: ND Option for NMS Discovery-//FW: New Version Notification for draft-liu-6man-nd-nms-discovery-00.txt
In-Reply-To: <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC189@nkgeml506-mbx.china.huawei.com>
Message-ID: <alpine.DEB.2.02.1310221010170.8663@uplift.swm.pp.se>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC189@nkgeml506-mbx.china.huawei.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; format=flowed; charset=US-ASCII
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 22 Oct 2013 08:16:00 -0000

On Tue, 22 Oct 2013, Liubing (Leo) wrote:

> Your comments would be appreciated much.

We have posted a similar kind of draft in Netconf-WG:

http://datatracker.ietf.org/doc/draft-fa-netconf-dhcpv6-option

I think your suggestion lacks for instance what kind of transport should 
be used to connect to the NMS, what port, and what kind of services the 
NMS offers. I guess could be expressed in the URL field, so you expect 
this option to be broadcasted in multiples in case the network supports 
multiple different types of NMS and different transport methods?

My opinion that this information is better carried in DHCPv6 as opposed to 
in ND.

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

From leo.liubing@huawei.com  Tue Oct 22 01:44:09 2013
Return-Path: <leo.liubing@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5203A11E8182 for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 01:44:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.486
X-Spam-Level: 
X-Spam-Status: No, score=-6.486 tagged_above=-999 required=5 tests=[AWL=0.113,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S+YASMVNfS2K for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 01:44:05 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8D8C711E833B for <ipv6@ietf.org>; Tue, 22 Oct 2013 01:44:02 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AXB09106; Tue, 22 Oct 2013 08:44:01 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.146.0; Tue, 22 Oct 2013 09:42:48 +0100
Received: from NKGEML410-HUB.china.huawei.com (10.98.56.41) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.146.0; Tue, 22 Oct 2013 09:43:46 +0100
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.141]) by nkgeml410-hub.china.huawei.com ([10.98.56.41]) with mapi id 14.03.0146.000; Tue, 22 Oct 2013 16:43:39 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Subject: RE: ND Option for NMS Discovery-//FW: New Version Notification for draft-liu-6man-nd-nms-discovery-00.txt
Thread-Topic: ND Option for NMS Discovery-//FW: New Version Notification for draft-liu-6man-nd-nms-discovery-00.txt
Thread-Index: AQHOzvrQkYnZSQrQ8EG70riP25iHvZn/2cgAgACJDqA=
Date: Tue, 22 Oct 2013 08:43:38 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC43D@nkgeml506-mbx.china.huawei.com>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC189@nkgeml506-mbx.china.huawei.com> <alpine.DEB.2.02.1310221010170.8663@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1310221010170.8663@uplift.swm.pp.se>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.132]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 22 Oct 2013 08:44:09 -0000

Hi, Mikael

Thanks for your quick comments. See inline.

> -----Original Message-----
> From: Mikael Abrahamsson [mailto:swmike@swm.pp.se]
> Sent: Tuesday, October 22, 2013 4:16 PM
> To: Liubing (Leo)
> Cc: 6man WG
> Subject: Re: ND Option for NMS Discovery-//FW: New Version Notification
> for draft-liu-6man-nd-nms-discovery-00.txt
>=20
> On Tue, 22 Oct 2013, Liubing (Leo) wrote:
>=20
> > Your comments would be appreciated much.
>=20
> We have posted a similar kind of draft in Netconf-WG:
>=20
> http://datatracker.ietf.org/doc/draft-fa-netconf-dhcpv6-option
>=20
> I think your suggestion lacks for instance what kind of transport should
> be used to connect to the NMS, what port, and what kind of services the
> NMS offers. I guess could be expressed in the URL field, so you expect
> this option to be broadcasted in multiples in case the network supports
> multiple different types of NMS and different transport methods?
[Bing] Yes. The ND option is not intend to be only for some specific transp=
ort methods. In this -00 version, we want to emphasize a "neighbor-learning=
" approach based on ND protocol.
But I agree with you the transport/management methods need to be considered=
 in the draft. Will do in the next version.

> My opinion that this information is better carried in DHCPv6 as opposed t=
o
> in ND.
[Bing] I'm afraid I can't agree, some scenarios might not involve DHCP, e.g=
. in the core networks, but ND is always on in IPv6. If the neighbors alrea=
dy knew something, it is quite convenient to propagate the information thro=
ugh ND.
May I ask the specific reasons that you prefer DHCPv6 over ND?

Best regards,
Bing
=20
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se

From swmike@swm.pp.se  Tue Oct 22 02:08:19 2013
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D18321E805D for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 02:08:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d8FghiSdND1z for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 02:08:18 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id 77EAC11E8177 for <ipv6@ietf.org>; Tue, 22 Oct 2013 02:08:18 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id F26E69C; Tue, 22 Oct 2013 11:08:15 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id EADC69A; Tue, 22 Oct 2013 11:08:15 +0200 (CEST)
Date: Tue, 22 Oct 2013 11:08:15 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "Liubing (Leo)" <leo.liubing@huawei.com>
Subject: RE: ND Option for NMS Discovery-//FW: New Version Notification for draft-liu-6man-nd-nms-discovery-00.txt
In-Reply-To: <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC43D@nkgeml506-mbx.china.huawei.com>
Message-ID: <alpine.DEB.2.02.1310221102190.8663@uplift.swm.pp.se>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC189@nkgeml506-mbx.china.huawei.com> <alpine.DEB.2.02.1310221010170.8663@uplift.swm.pp.se> <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC43D@nkgeml506-mbx.china.huawei.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; format=flowed; charset=US-ASCII
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 22 Oct 2013 09:08:19 -0000

On Tue, 22 Oct 2013, Liubing (Leo) wrote:

> [Bing] I'm afraid I can't agree, some scenarios might not involve DHCP, 
> e.g. in the core networks, but ND is always on in IPv6. If the neighbors 
> already knew something, it is quite convenient to propagate the 
> information through ND.

Why stop here then, there are a lot of other things we could put into ND 
that would also be convenient?

> May I ask the specific reasons that you prefer DHCPv6 over ND?

Because before a router knows anything, it's a host, not a router. DHCPv6 
is a "host" protocol. It was designed to do these things. There is no 
reason a router can't use DHCP to aquire knowledge, it's done using for 
instance DHCPv6-PD. Doesn't matter if it's a core router or not.

DHCP is used when someone wants to know something, in ND/RA things are 
announced all the time, periodically. I don't think putting "everything" 
there is a good engineering solution. For better or for worse, we have the 
separation between ND/RA and DHCP for different things, and I think it 
should be continued.

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

From leo.liubing@huawei.com  Tue Oct 22 03:00:45 2013
Return-Path: <leo.liubing@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 992D911E8259 for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 03:00:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.499
X-Spam-Level: 
X-Spam-Status: No, score=-6.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JNB0v1fHtjwm for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 03:00:36 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id D64F611E8192 for <ipv6@ietf.org>; Tue, 22 Oct 2013 03:00:34 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AXB17425; Tue, 22 Oct 2013 10:00:33 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.146.0; Tue, 22 Oct 2013 11:00:19 +0100
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.146.0; Tue, 22 Oct 2013 11:00:28 +0100
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.141]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0146.000; Tue, 22 Oct 2013 18:00:23 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Subject: RE: ND Option for NMS Discovery-//FW: New Version Notification for draft-liu-6man-nd-nms-discovery-00.txt
Thread-Topic: ND Option for NMS Discovery-//FW: New Version Notification for draft-liu-6man-nd-nms-discovery-00.txt
Thread-Index: AQHOzvrQkYnZSQrQ8EG70riP25iHvZn/2cgAgACJDqD//4WTgIAAhzfA
Date: Tue, 22 Oct 2013 10:00:22 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC4B2@nkgeml506-mbx.china.huawei.com>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC189@nkgeml506-mbx.china.huawei.com> <alpine.DEB.2.02.1310221010170.8663@uplift.swm.pp.se> <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC43D@nkgeml506-mbx.china.huawei.com> <alpine.DEB.2.02.1310221102190.8663@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1310221102190.8663@uplift.swm.pp.se>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.132]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 22 Oct 2013 10:00:45 -0000

> From: Mikael Abrahamsson [mailto:swmike@swm.pp.se]
> On Tue, 22 Oct 2013, Liubing (Leo) wrote:
>=20
> > [Bing] I'm afraid I can't agree, some scenarios might not involve DHCP,
> > e.g. in the core networks, but ND is always on in IPv6. If the neighbor=
s
> > already knew something, it is quite convenient to propagate the
> > information through ND.
>=20
> Why stop here then, there are a lot of other things we could put into ND
> that would also be convenient?
[Bing] Let's go back to the specific NMS information, I think it is quite c=
onvenient to propagated between routers through ND.=20

> > May I ask the specific reasons that you prefer DHCPv6 over ND?
>=20
> Because before a router knows anything, it's a host, not a router. DHCPv6
> is a "host" protocol. It was designed to do these things. There is no
> reason a router can't use DHCP to aquire knowledge, it's done using for
> instance DHCPv6-PD. Doesn't matter if it's a core router or not.
[Bing] The router surely could use DHCP. But it implies we need to add addi=
tional DHCP Server configurations to do this. This might more or less incre=
ase the management burden.

> DHCP is used when someone wants to know something, in ND/RA things are
> announced all the time, periodically. I don't think putting "everything"
> there is a good engineering solution.=20
[Bing] I agree never announcing "everything". But I think the NMS could be =
basic information that worth to be announced.
And we could also use RS/NS to pull the information from neighbors.

Best regards,
Bing



From iesg-secretary@ietf.org  Tue Oct 22 06:21:43 2013
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DC8711E838B; Tue, 22 Oct 2013 06:21:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.289
X-Spam-Level: 
X-Spam-Status: No, score=-102.289 tagged_above=-999 required=5 tests=[AWL=0.311, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7dQROk9FnpUS; Tue, 22 Oct 2013 06:21:42 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D85811E8392; Tue, 22 Oct 2013 06:21:41 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'Neighbor Unreachability Detection is too impatient' to Proposed Standard (draft-ietf-6man-impatient-nud-07.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131022132141.6823.82870.idtracker@ietfa.amsl.com>
Date: Tue, 22 Oct 2013 06:21:41 -0700
Cc: 6man chair <6man-chairs@tools.ietf.org>, 6man mailing list <ipv6@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 22 Oct 2013 13:21:43 -0000

The IESG has approved the following document:
- 'Neighbor Unreachability Detection is too impatient'
  (draft-ietf-6man-impatient-nud-07.txt) as Proposed Standard

This document is the product of the IPv6 Maintenance Working Group.

The IESG contact persons are Brian Haberman and Ted Lemon.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-6man-impatient-nud/




Technical Summary:

   IPv6 Neighbor Discovery includes Neighbor Unreachability Detection.
   That function is very useful when a host has an alternative, for
   instance multiple default routers, since it allows the host to switch
   to the alternative in short time.  This time is 3 seconds after the
   node starts probing by default.  However, if there are no
   alternatives, this is far too impatient.  This document specifies
   relaxed rules for Neighbor Discovery retransmissions that allows an
   implementation to choose different timeout behavior based on whether
   or not there are alternatives.  This document updates RFC 4861.

Working Group Summary:

Was there anything in WG process that is worth noting? For example,
was there controversy about particular points or were there decisions
where the consensus was particularly rough?

  Nothing in particular.

Document Quality:

Are there existing implementations of the protocol? Have a significant
number of vendors indicated their plan to implement the specification?
Are there any reviewers that merit special mention as having done a
thorough review, e.g., one that resulted in important changes or a
conclusion that the document had no substantive issues? If there was a
MIB Doctor, Media Type or other expert review, what was its course
(briefly)? In the case of a Media Type review, on what date was the
request posted?

   Multiple vendors have plans to implement the specification.

Personnel:

Ole Troan is the Document Shepherd. 
Brian Haberman is the Responsible Area Director.

From brian.e.carpenter@gmail.com  Tue Oct 22 13:47:31 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB62C11E8245 for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 13:47:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.382
X-Spam-Level: 
X-Spam-Status: No, score=-102.382 tagged_above=-999 required=5 tests=[AWL=0.217, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mFZLWwuwnwVI for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 13:47:31 -0700 (PDT)
Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 4C9EB11E8265 for <ipv6@ietf.org>; Tue, 22 Oct 2013 13:47:28 -0700 (PDT)
Received: by mail-pa0-f46.google.com with SMTP id fa1so16893pad.19 for <ipv6@ietf.org>; Tue, 22 Oct 2013 13:47: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=BoY35vQTxYywjyhsL0OztiN7YOTnu0pjiiUJurNMonw=; b=qo5ntouYLOGi6sTH6a2J5JFaK9DKxvNG3G9HuO/HFm5MMCYLe5p+ixdGuGmtHTijJz O2xA/leQwa1HQxyh14EA1CywkS/wW2QqkaUuw5Mt+qfBhN9q8Euzrnwe7JkooZaHzysY EvBde3j8KdBZVA4cGoAO+9alcFNzL+lXzrfAC5uvgFxP55kQLHhj1WG0poZSoC5p5Dq9 /8VQ6i6nr6xTY5mUcsURlRZSPqvWxUMPIyj/n2RCu93iWzVZ5/ARZ4z4daKlkHx6q3XP 76v4Bv3HLc7KZXuF7gItOGxG6rtPW93flUc1gqPdgq3s47OkRjHWN4PZhKJWyiVL2GP+ AGnQ==
X-Received: by 10.67.1.203 with SMTP id bi11mr10167269pad.137.1382474847774; Tue, 22 Oct 2013 13:47:27 -0700 (PDT)
Received: from [172.24.31.170] (wireless-nat-1.auckland.ac.nz. [130.216.30.112]) by mx.google.com with ESMTPSA id wr10sm26051077pbc.17.2013.10.22.13.47.25 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 22 Oct 2013 13:47:27 -0700 (PDT)
Message-ID: <5266E462.9050901@gmail.com>
Date: Wed, 23 Oct 2013 09:47:30 +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: Need for an overview [was ND Option for NMS Discovery-//FW: New Version Notification for draft-liu-6man-nd-nms-discovery-00.txt]
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC189@nkgeml506-mbx.china.huawei.com>	<alpine.DEB.2.02.1310221010170.8663@uplift.swm.pp.se>	<8AE0F17B87264D4CAC7DE0AA6C406F453D7CC43D@nkgeml506-mbx.china.huawei.com> <alpine.DEB.2.02.1310221102190.8663@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1310221102190.8663@uplift.swm.pp.se>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 22 Oct 2013 20:47:31 -0000

As I said when commenting on the draft charter recently:

I think there's a missing goal, something like

 - Define relationship and boundary between DHCPv6-based and RA/ND-based
   host configuration mechanisms. (This is partly an operational topic, but
   it lies behind a whole bunch of discussions in various WGs).

Unless we get this settled as a general matter, the discussion below will
continue to occur every time an RA/ND extension or a routing-related
DHCPv6 option is proposed.

Regards
   Brian

On 22/10/2013 22:08, Mikael Abrahamsson wrote:
> On Tue, 22 Oct 2013, Liubing (Leo) wrote:
> 
>> [Bing] I'm afraid I can't agree, some scenarios might not involve
>> DHCP, e.g. in the core networks, but ND is always on in IPv6. If the
>> neighbors already knew something, it is quite convenient to propagate
>> the information through ND.
> 
> Why stop here then, there are a lot of other things we could put into ND
> that would also be convenient?
> 
>> May I ask the specific reasons that you prefer DHCPv6 over ND?
> 
> Because before a router knows anything, it's a host, not a router.
> DHCPv6 is a "host" protocol. It was designed to do these things. There
> is no reason a router can't use DHCP to aquire knowledge, it's done
> using for instance DHCPv6-PD. Doesn't matter if it's a core router or not.
> 
> DHCP is used when someone wants to know something, in ND/RA things are
> announced all the time, periodically. I don't think putting "everything"
> there is a good engineering solution. For better or for worse, we have
> the separation between ND/RA and DHCP for different things, and I think
> it should be continued.
> 

From dougb@dougbarton.us  Tue Oct 22 14:03:42 2013
Return-Path: <dougb@dougbarton.us>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5695111E81FF for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 14:03:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fiq2s6sO3pEO for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 14:03:37 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id C80FE11E81EB for <ipv6@ietf.org>; Tue, 22 Oct 2013 14:03:37 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:21f4:5bc9:619d:7002] (unknown [IPv6:2001:470:d:5e7:21f4:5bc9:619d:7002]) by dougbarton.us (Postfix) with ESMTPSA id 631CB22B26 for <ipv6@ietf.org>; Tue, 22 Oct 2013 21:03:37 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1382475817; bh=/T9EBh6C/d4O2kjlA8M/wRrYpeMdAgDm8bmnD6Crh0o=; h=Date:From:To:Subject:References:In-Reply-To; b=YEaQIwXaXcvxqYiYC9A1Mn331Ru6muunwP+eUZj3RNiVpvkRql7FIk5zY5oTC0T0V VgQraULleBxy+t/DHiGgud+477M+jJiYzTsMz7YLiZFq9tce29Vuuvl9LC4nVNm4CV 5Ey841nTFDpZH6izhxFOYbZ5Dd4Vw+R6Nd/Xn6eg=
Message-ID: <5266E828.2000501@dougbarton.us>
Date: Tue, 22 Oct 2013 14:03:36 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: Need for an overview [was ND Option for NMS Discovery-//FW: New Version Notification for draft-liu-6man-nd-nms-discovery-00.txt]
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC189@nkgeml506-mbx.china.huawei.com>	<alpine.DEB.2.02.1310221010170.8663@uplift.swm.pp.se>	<8AE0F17B87264D4CAC7DE0AA6C406F453D7CC43D@nkgeml506-mbx.china.huawei.com>	<alpine.DEB.2.02.1310221102190.8663@uplift.swm.pp.se> <5266E462.9050901@gmail.com>
In-Reply-To: <5266E462.9050901@gmail.com>
X-Enigmail-Version: 1.6
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 22 Oct 2013 21:03:42 -0000

On 10/22/2013 01:47 PM, Brian E Carpenter wrote:
> As I said when commenting on the draft charter recently:
>
> I think there's a missing goal, something like
>
>   - Define relationship and boundary between DHCPv6-based and RA/ND-based
>     host configuration mechanisms. (This is partly an operational topic, but
>     it lies behind a whole bunch of discussions in various WGs).
>
> Unless we get this settled as a general matter, the discussion below will
> continue to occur every time an RA/ND extension or a routing-related
> DHCPv6 option is proposed.

FWIW I agree that this is a good problem to solve, but it should 
probably be a separate document, shouldn't it? Not that I envy anyone 
taking it on, or that I am optimistic for consensus, but it IS a topic 
it would be nice to get resolved.

Doug


From rogerj@gmail.com  Tue Oct 22 14:26:25 2013
Return-Path: <rogerj@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F020111E80F1 for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 14:26:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.268
X-Spam-Level: 
X-Spam-Status: No, score=-2.268 tagged_above=-999 required=5 tests=[AWL=0.032,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q6TWzamJcox0 for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 14:26:24 -0700 (PDT)
Received: from mail-we0-x22c.google.com (mail-we0-x22c.google.com [IPv6:2a00:1450:400c:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 0AA8D11E81FF for <ipv6@ietf.org>; Tue, 22 Oct 2013 14:26:23 -0700 (PDT)
Received: by mail-we0-f172.google.com with SMTP id q58so8922363wes.3 for <ipv6@ietf.org>; Tue, 22 Oct 2013 14:26:23 -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 :cc:content-type; bh=nnFd8ojGVgrmmF0Xq4FAADxvQzqtxLQ3WcLlEKVyq2E=; b=VPUuwBp4Gh7pkW67K5QS2JGw/KepsBFbPeSJG2SmdLsjvIs4MpBv4qXfl583np1WAd fhAd6qC4u6nfJ3HA7QuJfGOr3X7w0SkMbfl5VEJ0/iLNZCGRDlfwR1NRRIhptWkNOvcM KoanxTUFrF9IT5l+sMHXd0qWUWqwp7De2qzHXKFfPH3Y9R+ug/E5kuKITaBeyVYabF6k y/j6woi5cbZUv1rQnJghBpwF8bB/YDqGdkglDQL/a6NFeO97dg8feciPi/u2lcaugcb9 sdiaCv30GMjDVvZ9GA9QPxXeh2ej16EdiK74LOatCo6b/fxflURqUnogqFQ/RLaWUaVz sWGQ==
MIME-Version: 1.0
X-Received: by 10.180.78.167 with SMTP id c7mr16199308wix.25.1382477183089; Tue, 22 Oct 2013 14:26:23 -0700 (PDT)
Received: by 10.216.213.72 with HTTP; Tue, 22 Oct 2013 14:26:23 -0700 (PDT)
In-Reply-To: <5266E828.2000501@dougbarton.us>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC189@nkgeml506-mbx.china.huawei.com> <alpine.DEB.2.02.1310221010170.8663@uplift.swm.pp.se> <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC43D@nkgeml506-mbx.china.huawei.com> <alpine.DEB.2.02.1310221102190.8663@uplift.swm.pp.se> <5266E462.9050901@gmail.com> <5266E828.2000501@dougbarton.us>
Date: Tue, 22 Oct 2013 23:26:23 +0200
Message-ID: <CAKFn1SFcKuw8xNeqTWN4h68XdQDXqv_GmF4rUUNKq2tcSTjByA@mail.gmail.com>
Subject: Re: Need for an overview [was ND Option for NMS Discovery-//FW: New Version Notification for draft-liu-6man-nd-nms-discovery-00.txt]
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: Doug Barton <dougb@dougbarton.us>
Content-Type: text/plain; charset=ISO-8859-1
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 22 Oct 2013 21:26:25 -0000

On Tue, Oct 22, 2013 at 11:03 PM, Doug Barton <dougb@dougbarton.us> wrote:
> On 10/22/2013 01:47 PM, Brian E Carpenter wrote:
>>
>> As I said when commenting on the draft charter recently:
>>
>> I think there's a missing goal, something like
>>
>>   - Define relationship and boundary between DHCPv6-based and RA/ND-based
>>     host configuration mechanisms. (This is partly an operational topic,
>> but
>>     it lies behind a whole bunch of discussions in various WGs).
>>
>> Unless we get this settled as a general matter, the discussion below will
>> continue to occur every time an RA/ND extension or a routing-related
>> DHCPv6 option is proposed.
>
>
> FWIW I agree that this is a good problem to solve, but it should probably be
> a separate document, shouldn't it? Not that I envy anyone taking it on, or
> that I am optimistic for consensus, but it IS a topic it would be nice to
> get resolved.

I used to say we should keep them separate, not add things into DHCPv6
that ND does, and the other way around. And I still belive they're not
really part of the same domain, or use cases.


However, after trying to explain ND and DHCPv6 several times I have to
admit - it was, and still is a good idea, but it's too complicated.
And also, we can not continue to have this discussion every/every odd
year.

I am against adding more to ND, let's keep it clean and neat. But I'm
in favour of adding more into DHCPv6. We probably can get consensus on
changing thing this time around :)

If is a job for this document or not, no opinion yet.



-- 

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

From sarikaya2012@gmail.com  Tue Oct 22 14:39:09 2013
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0C6911E81FF for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 14:39:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.111
X-Spam-Level: 
X-Spam-Status: No, score=-2.111 tagged_above=-999 required=5 tests=[AWL=0.488,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l4aJweAt5Qkt for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 14:39:06 -0700 (PDT)
Received: from mail-lb0-x232.google.com (mail-lb0-x232.google.com [IPv6:2a00:1450:4010:c04::232]) by ietfa.amsl.com (Postfix) with ESMTP id 42A7D11E826C for <ipv6@ietf.org>; Tue, 22 Oct 2013 14:38:20 -0700 (PDT)
Received: by mail-lb0-f178.google.com with SMTP id o14so54751lbi.23 for <ipv6@ietf.org>; Tue, 22 Oct 2013 14:38:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=1tBFlYuXCK0YqBcP/0Xrlc7DP0/jTDUEnFaIDzNBKy8=; b=qCs0XWzk2saY9NoBlEsL3BC3kA/DW0SDgKKVddx+73D3Z+mkAbKvjg8HSSamDSKpLR VU8CGhkkBMTg2FFD+AVx277itOnnqcSOrr3eBSKFuK4kCq6GSkD8eafJBmeD6DPuvuXN RbhHLAPLLNAkTegO3Hu+jQPxf/YBaBOt1fCr9Z0aIn8IKBJC9x0kGtf0b6rFoY8PzoSv SDf0csYT7ZAogjYLs6oX8heoibrngqn4lsv+GmJbyfTmXLKNXYjJ54CLme908AUhHYVz OGR4WHw44qlTbQU2uWa2krC6s+bC35GOJLbE961hn/RWAiKfdl7fLbHQyGwgFW/khYAN w7MA==
MIME-Version: 1.0
X-Received: by 10.152.22.198 with SMTP id g6mr19318793laf.5.1382477899498; Tue, 22 Oct 2013 14:38:19 -0700 (PDT)
Received: by 10.114.98.227 with HTTP; Tue, 22 Oct 2013 14:38:19 -0700 (PDT)
In-Reply-To: <5266E462.9050901@gmail.com>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC189@nkgeml506-mbx.china.huawei.com> <alpine.DEB.2.02.1310221010170.8663@uplift.swm.pp.se> <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC43D@nkgeml506-mbx.china.huawei.com> <alpine.DEB.2.02.1310221102190.8663@uplift.swm.pp.se> <5266E462.9050901@gmail.com>
Date: Tue, 22 Oct 2013 16:38:19 -0500
Message-ID: <CAC8QAcexEdFJmVdNeqL10HiFmbcHU9xr5qLcU58Ud-sb3njC0g@mail.gmail.com>
Subject: Re: Need for an overview [was ND Option for NMS Discovery-//FW: New Version Notification for draft-liu-6man-nd-nms-discovery-00.txt]
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=089e0160bab01c07f004e95b38de
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 22 Oct 2013 21:39:09 -0000

--089e0160bab01c07f004e95b38de
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Oct 22, 2013 at 3:47 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> As I said when commenting on the draft charter recently:
>
> I think there's a missing goal, something like
>
>  - Define relationship and boundary between DHCPv6-based and RA/ND-based
>    host configuration mechanisms. (This is partly an operational topic, but
>    it lies behind a whole bunch of discussions in various WGs).
>
> Unless we get this settled as a general matter, the discussion below will
> continue to occur every time an RA/ND extension or a routing-related
> DHCPv6 option is proposed.
>
>
I think we should separate SLAAC and stateful address configuration with
DHCPv6 versus
RA options for routing as in RFC 4191.

Why? Because the former is already in the RFCs, RFC 4861 and RFC 3315 while
for the latter, the DHCP proposal did not go through.

For the latter, the issue is should we add new RA options?
My answer is we should, the last time this has been done was in RFC 6106.
When new needs come up, why not add new RA options?

Regards,

Behcet

> Regards
>    Brian
>
> On 22/10/2013 22:08, Mikael Abrahamsson wrote:
> > On Tue, 22 Oct 2013, Liubing (Leo) wrote:
> >
> >> [Bing] I'm afraid I can't agree, some scenarios might not involve
> >> DHCP, e.g. in the core networks, but ND is always on in IPv6. If the
> >> neighbors already knew something, it is quite convenient to propagate
> >> the information through ND.
> >
> > Why stop here then, there are a lot of other things we could put into ND
> > that would also be convenient?
> >
> >> May I ask the specific reasons that you prefer DHCPv6 over ND?
> >
> > Because before a router knows anything, it's a host, not a router.
> > DHCPv6 is a "host" protocol. It was designed to do these things. There
> > is no reason a router can't use DHCP to aquire knowledge, it's done
> > using for instance DHCPv6-PD. Doesn't matter if it's a core router or
> not.
> >
> > DHCP is used when someone wants to know something, in ND/RA things are
> > announced all the time, periodically. I don't think putting "everything"
> > there is a good engineering solution. For better or for worse, we have
> > the separation between ND/RA and DHCP for different things, and I think
> > it should be continued.
> >
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

--089e0160bab01c07f004e95b38de
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Tue, Oct 22, 2013 at 3:47 PM, Brian E Carpenter <span dir=3D"ltr=
">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">bria=
n.e.carpenter@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">As I said when commenting on the draft chart=
er recently:<br>
<br>
I think there&#39;s a missing goal, something like<br>
<br>
=A0- Define relationship and boundary between DHCPv6-based and RA/ND-based<=
br>
=A0 =A0host configuration mechanisms. (This is partly an operational topic,=
 but<br>
=A0 =A0it lies behind a whole bunch of discussions in various WGs).<br>
<br>
Unless we get this settled as a general matter, the discussion below will<b=
r>
continue to occur every time an RA/ND extension or a routing-related<br>
DHCPv6 option is proposed.<br>
<br></blockquote><div><br></div><div>I think we should separate SLAAC and s=
tateful address configuration with DHCPv6 versus<br></div><div>RA options f=
or routing as in RFC 4191.<br><br></div><div>Why? Because the former is alr=
eady in the RFCs, RFC 4861 and RFC 3315 while for the latter, the DHCP prop=
osal did not go through.<br>
<br></div><div>For the latter, the issue is should we add new RA options?<b=
r></div><div>My answer is we should, the last time this has been done was i=
n RFC 6106. When new needs come up, why not add new RA options?<br><br>
</div><div>Regards,<br><br></div><div>Behcet<br></div><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex">
Regards<br>
=A0 =A0Brian<br>
<br>
On 22/10/2013 22:08, Mikael Abrahamsson wrote:<br>
&gt; On Tue, 22 Oct 2013, Liubing (Leo) wrote:<br>
&gt;<br>
&gt;&gt; [Bing] I&#39;m afraid I can&#39;t agree, some scenarios might not =
involve<br>
&gt;&gt; DHCP, e.g. in the core networks, but ND is always on in IPv6. If t=
he<br>
&gt;&gt; neighbors already knew something, it is quite convenient to propag=
ate<br>
&gt;&gt; the information through ND.<br>
&gt;<br>
&gt; Why stop here then, there are a lot of other things we could put into =
ND<br>
&gt; that would also be convenient?<br>
&gt;<br>
&gt;&gt; May I ask the specific reasons that you prefer DHCPv6 over ND?<br>
&gt;<br>
&gt; Because before a router knows anything, it&#39;s a host, not a router.=
<br>
&gt; DHCPv6 is a &quot;host&quot; protocol. It was designed to do these thi=
ngs. There<br>
&gt; is no reason a router can&#39;t use DHCP to aquire knowledge, it&#39;s=
 done<br>
&gt; using for instance DHCPv6-PD. Doesn&#39;t matter if it&#39;s a core ro=
uter or not.<br>
&gt;<br>
&gt; DHCP is used when someone wants to know something, in ND/RA things are=
<br>
&gt; announced all the time, periodically. I don&#39;t think putting &quot;=
everything&quot;<br>
&gt; there is a good engineering solution. For better or for worse, we have=
<br>
&gt; the separation between ND/RA and DHCP for different things, and I thin=
k<br>
&gt; it should be continued.<br>
&gt;<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></div>

--089e0160bab01c07f004e95b38de--

From kitamura@da.jp.nec.com  Tue Oct 22 19:31:36 2013
Return-Path: <kitamura@da.jp.nec.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4A0E11E82B0 for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 19:31:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.09
X-Spam-Level: 
X-Spam-Status: No, score=-4.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L67HySwAeGDn for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 19:31:32 -0700 (PDT)
Received: from tyo202.gate.nec.co.jp (TYO202.gate.nec.co.jp [202.32.8.206]) by ietfa.amsl.com (Postfix) with ESMTP id 5878D11E8275 for <ipv6@ietf.org>; Tue, 22 Oct 2013 19:31:32 -0700 (PDT)
Received: from mailgate3.nec.co.jp ([10.7.69.195]) by tyo202.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id r9N2VPtB016526;  Wed, 23 Oct 2013 11:31:25 +0900 (JST)
Received: from mailsv4.nec.co.jp (imss63.nec.co.jp [10.7.69.158]) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) with ESMTP id r9N2VPE08708; Wed, 23 Oct 2013 11:31:25 +0900 (JST)
Received: from mail03.kamome.nec.co.jp (mail03.kamome.nec.co.jp [10.25.43.7]) by mailsv4.nec.co.jp (8.13.8/8.13.4) with ESMTP id r9N2VP8Q013646; Wed, 23 Oct 2013 11:31:25 +0900 (JST)
Received: from bpxc99gp.gisp.nec.co.jp ([10.38.151.134] [10.38.151.134]) by mail02.kamome.nec.co.jp with ESMTP id BT-MMP-159365; Wed, 23 Oct 2013 11:30:39 +0900
Received: from BPXM02GP.gisp.nec.co.jp ([169.254.1.234]) by BPXC06GP.gisp.nec.co.jp ([10.38.151.134]) with mapi id 14.02.0328.011; Wed, 23 Oct 2013 11:30:38 +0900
From: Hiroshi Kitamura <kitamura@da.jp.nec.com>
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: I-D Action: draft-kitamura-ipv6-zoneid-free-01.txt
Thread-Topic: I-D Action: draft-kitamura-ipv6-zoneid-free-01.txt
Thread-Index: AQHOzhgGds9FjF+FCk6iX/lupzk4+JoBkQLA
Date: Wed, 23 Oct 2013 02:30:38 +0000
Message-ID: <8392F9BAC6AD5F47920216A6D7853F7E1D57D48A@BPXM02GP.gisp.nec.co.jp>
References: <20131021044241.22753.19800.idtracker@ietfa.amsl.com>
In-Reply-To: <20131021044241.22753.19800.idtracker@ietfa.amsl.com>
Accept-Language: ja-JP, en-US
Content-Language: ja-JP
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.56.48.28]
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Hiroshi Kitamura <kitamura@da.jp.nec.com>, "Ata, Shingo \(ata@info.eng.osaka-cu.ac.jp\)" <ata@info.eng.osaka-cu.ac.jp>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 23 Oct 2013 02:31:36 -0000

Dear All,

We have submitted the following I-D.
  Title           : Free from Using Zone Identifier for IPv6 Link-Local Add=
ress
  Filename        : draft-kitamura-ipv6-zoneid-free-01.txt

This I-D describes "Zone-ID Free" functions that make end users free from u=
sing zone identifiers (Zone-ID) for IPv6 link-local addresses.
This idea have been implemented and verified under Linux OS.

We think this issue must be very interesting for 6man WG.

Please, let us know your comments or interest on this idea.

Best Regards,
Hiroshi


> -----Original Message-----
> From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org=
] On Behalf Of internet-drafts@ietf.org
> Sent: Monday, October 21, 2013 1:43 PM
> To: i-d-announce@ietf.org
> Subject: I-D Action: draft-kitamura-ipv6-zoneid-free-01.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
>=20
>=20
> 	Title           : Free from Using Zone Identifier for IPv6 Link-Local Ad=
dress
> 	Author(s)       : Hiroshi Kitamura
>                           Shingo Ata
>                           Masayuki Murata
> 	Filename        : draft-kitamura-ipv6-zoneid-free-01.txt
> 	Pages           : 14
> 	Date            : 2013-10-20
>=20
> Abstract:
>    This document describes "Zone-ID Free" functions that make end
>    users free from using zone identifiers (Zone-ID) for IPv6 link-
>    local addresses.
>=20
>    When users deal with IPv6 link-local addresses, it is thought that
>    it is mandatory thing to specify accompanied Zone-IDs. For end
>    users, however, it is troublesome and nuisance thing to do it.
>    Because it is very hard for normal end users to find appropriate
>    Zone-IDs for this purpose.
>=20
>    From another viewpoint, the usage of IPv6 link-local addresses
>    accompanied with Zone-IDs is quite different from the traditional
>    usage of global addresses. Therefore many problems related with
>    Zone-ID are caused and new specifications are required to fix these
>    problems.
>=20
>    This document explores and describes how "Zone-ID Free" functions
>    work and how end users are released from using Zone-IDs when they
>    deal with IPv6 link-local addresses.
>=20
>    The "Zone-ID Free" functions are upper compatible with the current
>    usages of dealing with IPv6 link-local addresses and harmless to
>    the existing communications.
>=20
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-kitamura-ipv6-zoneid-free
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-kitamura-ipv6-zoneid-free-01
>=20
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-kitamura-ipv6-zoneid-free-01
>=20
>=20
> Please note that it may take a couple of minutes from the time of submiss=
ion 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

From Tina.Tsou.Zouting@huawei.com  Tue Oct 22 19:37:49 2013
Return-Path: <Tina.Tsou.Zouting@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4962311E8297 for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 19:37:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.31
X-Spam-Level: 
X-Spam-Status: No, score=-6.31 tagged_above=-999 required=5 tests=[AWL=0.288,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nqs+bNvgVSGZ for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 19:37:44 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5F31B11E80D9 for <ipv6@ietf.org>; Tue, 22 Oct 2013 19:37:43 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AZI83792; Wed, 23 Oct 2013 02:37:41 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 23 Oct 2013 03:37:39 +0100
Received: from SJCEML402-HUB.china.huawei.com (10.212.94.43) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.146.0; Wed, 23 Oct 2013 03:37:39 +0100
Received: from SJCEML501-MBS.china.huawei.com ([169.254.2.123]) by sjceml402-hub.china.huawei.com ([10.212.94.43]) with mapi id 14.03.0158.001; Tue, 22 Oct 2013 19:37:34 -0700
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: "<sarikaya@ieee.org>" <sarikaya@ieee.org>
Subject: Re: Need for an overview [was ND Option for NMS Discovery-//FW: New Version Notification for draft-liu-6man-nd-nms-discovery-00.txt]
Thread-Topic: Need for an overview [was ND Option for NMS Discovery-//FW: New	Version Notification for draft-liu-6man-nd-nms-discovery-00.txt]
Thread-Index: AQHOz2gC55K+DEixkEuGFhp1puicbJoBtJSA///eRa4=
Date: Wed, 23 Oct 2013 02:37:34 +0000
Message-ID: <107C239B-C80A-41EF-B6AF-765D3E3746E9@huawei.com>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC189@nkgeml506-mbx.china.huawei.com> <alpine.DEB.2.02.1310221010170.8663@uplift.swm.pp.se> <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC43D@nkgeml506-mbx.china.huawei.com> <alpine.DEB.2.02.1310221102190.8663@uplift.swm.pp.se> <5266E462.9050901@gmail.com>, <CAC8QAcexEdFJmVdNeqL10HiFmbcHU9xr5qLcU58Ud-sb3njC0g@mail.gmail.com>
In-Reply-To: <CAC8QAcexEdFJmVdNeqL10HiFmbcHU9xr5qLcU58Ud-sb3njC0g@mail.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_107C239BC80A41EFB6AF765D3E3746E9huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 23 Oct 2013 02:37:49 -0000

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

Dear all,
IMHO, it is related to http://datatracker.ietf.org/doc/draft-schoenw-opsawg=
-nm-dhc<http://datatracker.ietf.org/doc/draft-schoenw-opsawg-nm-dhc/>/
What do u think about this?

Thank you,
Tina

On Oct 22, 2013, at 2:39 PM, "Behcet Sarikaya" <sarikaya2012@gmail.com<mail=
to:sarikaya2012@gmail.com>> wrote:




On Tue, Oct 22, 2013 at 3:47 PM, Brian E Carpenter <brian.e.carpenter@gmail=
.com<mailto:brian.e.carpenter@gmail.com>> wrote:
As I said when commenting on the draft charter recently:

I think there's a missing goal, something like

 - Define relationship and boundary between DHCPv6-based and RA/ND-based
   host configuration mechanisms. (This is partly an operational topic, but
   it lies behind a whole bunch of discussions in various WGs).

Unless we get this settled as a general matter, the discussion below will
continue to occur every time an RA/ND extension or a routing-related
DHCPv6 option is proposed.


I think we should separate SLAAC and stateful address configuration with DH=
CPv6 versus
RA options for routing as in RFC 4191.

Why? Because the former is already in the RFCs, RFC 4861 and RFC 3315 while=
 for the latter, the DHCP proposal did not go through.

For the latter, the issue is should we add new RA options?
My answer is we should, the last time this has been done was in RFC 6106. W=
hen new needs come up, why not add new RA options?

Regards,

Behcet
Regards
   Brian

On 22/10/2013 22:08, Mikael Abrahamsson wrote:
> On Tue, 22 Oct 2013, Liubing (Leo) wrote:
>
>> [Bing] I'm afraid I can't agree, some scenarios might not involve
>> DHCP, e.g. in the core networks, but ND is always on in IPv6. If the
>> neighbors already knew something, it is quite convenient to propagate
>> the information through ND.
>
> Why stop here then, there are a lot of other things we could put into ND
> that would also be convenient?
>
>> May I ask the specific reasons that you prefer DHCPv6 over ND?
>
> Because before a router knows anything, it's a host, not a router.
> DHCPv6 is a "host" protocol. It was designed to do these things. There
> is no reason a router can't use DHCP to aquire knowledge, it's done
> using for instance DHCPv6-PD. Doesn't matter if it's a core router or not=
.
>
> DHCP is used when someone wants to know something, in ND/RA things are
> announced all the time, periodically. I don't think putting "everything"
> there is a good engineering solution. For better or for worse, we have
> the separation between ND/RA and DHCP for different things, and I think
> it should be continued.
>
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org<mailto:ipv6@ietf.org>
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------


--_000_107C239BC80A41EFB6AF765D3E3746E9huaweicom_
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></span></div>
<div>
<div style=3D"-webkit-text-size-adjust: auto; ">Dear all,</div>
<div><span style=3D"-webkit-text-size-adjust: auto;">IMHO, i</span><span st=
yle=3D"background-color: rgba(255, 255, 255, 0); -webkit-text-size-adjust: =
auto; ">t is related to&nbsp;</span><a href=3D"http://datatracker.ietf.org/=
doc/draft-schoenw-opsawg-nm-dhc/" x-apple-data-detectors=3D"true" x-apple-d=
ata-detectors-type=3D"link" x-apple-data-detectors-result=3D"1" style=3D"-w=
ebkit-text-size-adjust: auto; ">http://datatracker.ietf.org/doc/draft-schoe=
nw-opsawg-nm-dhc</a>/<br>
What do u think about this?<br>
<div style=3D"-webkit-text-size-adjust: auto; "><br>
</div>
<div style=3D"-webkit-text-size-adjust: auto; ">Thank you,</div>
<span style=3D"-webkit-text-size-adjust: auto;">Tina</span></div>
<div style=3D"-webkit-text-size-adjust: auto; "><br>
On Oct 22, 2013, at 2:39 PM, &quot;Behcet Sarikaya&quot; &lt;<a href=3D"mai=
lto:sarikaya2012@gmail.com">sarikaya2012@gmail.com</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite" style=3D"-webkit-text-size-adjust: auto; ">
<div>
<div dir=3D"ltr"><br>
<div class=3D"gmail_extra"><br>
<br>
<div class=3D"gmail_quote">On Tue, Oct 22, 2013 at 3:47 PM, Brian E Carpent=
er <span dir=3D"ltr">
&lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">brian.=
e.carpenter@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
As I said when commenting on the draft charter recently:<br>
<br>
I think there's a missing goal, something like<br>
<br>
&nbsp;- Define relationship and boundary between DHCPv6-based and RA/ND-bas=
ed<br>
&nbsp; &nbsp;host configuration mechanisms. (This is partly an operational =
topic, but<br>
&nbsp; &nbsp;it lies behind a whole bunch of discussions in various WGs).<b=
r>
<br>
Unless we get this settled as a general matter, the discussion below will<b=
r>
continue to occur every time an RA/ND extension or a routing-related<br>
DHCPv6 option is proposed.<br>
<br>
</blockquote>
<div><br>
</div>
<div>I think we should separate SLAAC and stateful address configuration wi=
th DHCPv6 versus<br>
</div>
<div>RA options for routing as in RFC 4191.<br>
<br>
</div>
<div>Why? Because the former is already in the RFCs, RFC 4861 and RFC 3315 =
while for the latter, the DHCP proposal did not go through.<br>
<br>
</div>
<div>For the latter, the issue is should we add new RA options?<br>
</div>
<div>My answer is we should, the last time this has been done was in RFC 61=
06. When new needs come up, why not add new RA options?<br>
<br>
</div>
<div>Regards,<br>
<br>
</div>
<div>Behcet<br>
</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Regards<br>
&nbsp; &nbsp;Brian<br>
<br>
On 22/10/2013 22:08, Mikael Abrahamsson wrote:<br>
&gt; On Tue, 22 Oct 2013, Liubing (Leo) wrote:<br>
&gt;<br>
&gt;&gt; [Bing] I'm afraid I can't agree, some scenarios might not involve<=
br>
&gt;&gt; DHCP, e.g. in the core networks, but ND is always on in IPv6. If t=
he<br>
&gt;&gt; neighbors already knew something, it is quite convenient to propag=
ate<br>
&gt;&gt; the information through ND.<br>
&gt;<br>
&gt; Why stop here then, there are a lot of other things we could put into =
ND<br>
&gt; that would also be convenient?<br>
&gt;<br>
&gt;&gt; May I ask the specific reasons that you prefer DHCPv6 over ND?<br>
&gt;<br>
&gt; Because before a router knows anything, it's a host, not a router.<br>
&gt; DHCPv6 is a &quot;host&quot; protocol. It was designed to do these thi=
ngs. There<br>
&gt; is no reason a router can't use DHCP to aquire knowledge, it's done<br=
>
&gt; using for instance DHCPv6-PD. Doesn't matter if it's a core router or =
not.<br>
&gt;<br>
&gt; DHCP is used when someone wants to know something, in ND/RA things are=
<br>
&gt; announced all the time, periodically. I don't think putting &quot;ever=
ything&quot;<br>
&gt; there is a good engineering solution. For better or for worse, we have=
<br>
&gt; the separation between ND/RA and DHCP for different things, and I thin=
k<br>
&gt; it should be continued.<br>
&gt;<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>
</div>
</div>
</blockquote>
<blockquote type=3D"cite" style=3D"-webkit-text-size-adjust: auto; ">
<div></div>
</blockquote>
</div>
</body>
</html>

--_000_107C239BC80A41EFB6AF765D3E3746E9huaweicom_--

From nalini.elkins@insidethestack.com  Tue Oct 22 19:47:49 2013
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2712311E80F6 for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 19:47:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level: 
X-Spam-Status: No, score=-2.382 tagged_above=-999 required=5 tests=[AWL=0.216,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fyW69Sfyd-1r for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 19:47:49 -0700 (PDT)
Received: from nm15-vm10.access.bullet.mail.bf1.yahoo.com (nm15-vm10.access.bullet.mail.bf1.yahoo.com [216.109.115.41]) by ietfa.amsl.com (Postfix) with ESMTP id B577411E82BC for <ipv6@ietf.org>; Tue, 22 Oct 2013 19:47:42 -0700 (PDT)
Received: from [66.196.81.163] by nm15.access.bullet.mail.bf1.yahoo.com with NNFMP; 23 Oct 2013 02:47:42 -0000
Received: from [66.196.81.137] by tm9.access.bullet.mail.bf1.yahoo.com with NNFMP; 23 Oct 2013 02:47:42 -0000
Received: from [127.0.0.1] by omp1013.access.mail.bf1.yahoo.com with NNFMP; 23 Oct 2013 02:47:42 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 5998.63438.bm@omp1013.access.mail.bf1.yahoo.com
Received: (qmail 47023 invoked by uid 60001); 23 Oct 2013 02:47:41 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1382496461; bh=cp/HBCX/azKn4xEzvCECFX47EmKLyeH/PkzW2nQkVfg=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=cCILD0lcg4yCQrbCKIsOasldBSmzwrTwj00/2xYq+zJyjhhy6n3Cf5eMNxUWwt01dbFxx0V6L9Bz02kC8gSPYcH27aQlZXRuFHSS5R12P1bDmuwMFSb5Tu1pqV/ecSbv2ZNdO3lx3MZm0XAqscPSdZmaEKL+ZqQTSnbg3bDyZ20=
X-YMail-OSG: QPQC_PsVM1kZD_X6gftynY4P1O7fpNe3sXgZmv80zWVACon 0c4YSAvjLK7lrM9GBYC1tsImxDhj_Yv_c9JUzlt89s57taT5hkZaFLU3wura dbkpAoGoL398Wp_SPxc6_I5D8ZqfG2.auj7MojOJvR.m6gH7_i1JjdrNoKAW KskYXNZCdRS.xDt2RdTzdHoQq2FFHxACNh3gXI3OAQpAnek2xNd96ar0Fb0y G3T9Llgg_uvxyqa_4kkh3_FFtTwno0mVzqPSfsH5c6fFo6hvdA2g5OdHpDVD 8moyZzinaLOczBgi6tiUzZU9vrCtcx2_FkiB4KuwpHr0nKtpC4i5mp8NQbLZ ydi5VRWZ2QxsuV7DwQ5.VA.2PBKscBTAy5xUmi5d568mNhbjvUE.KuFWXUIC dDlNxkMQaR_dHsLO9f9L_vK3On292mgnHeNomXnjjTjkikPpCCpnhG7Hkmn. xVLQmLtyHx.y1jy8PitoDE4wJQuqOJmDa.0K9xSPXID3gu_DzAS12QmtSjsb CpIWqr1JMPLCSwVgFmkczX7Vzwsr8exMm__v5fIfD3TbT_1kih2VQJFwGrQK PXoNxb6DajkwKdVcCiJj_xJ1Aspkil4VXwKHorw--
Received: from [24.130.37.147] by web2802.biz.mail.ne1.yahoo.com via HTTP; Tue, 22 Oct 2013 19:47:40 PDT
X-Rocket-MIMEInfo: 002.001, Cgo.IE5hbGluaSBFbGtpbnMgPG1haWx0bzpuYWxpbmkuZWxraW5zQGluc2lkZXRoZXN0YWNrLmNvbT4KPiAyMiBPY3RvYmVyIDIwMTMgMDA6NTgKPj7CoCAxKSBlbmNvZGluZyBoYXMgdG8gYmUgZmFzdCwgYnV0IGRlY29kaW5nIGRvZXMgbm90Cj4KPiBUcnVlCj4KPj7CoCAyKSBhIG5vZGUncyBjbG9jayBjb3VsZCBiZSBlaXRoZXIgaW4gb3VyIG91dCBvZiBzeW5jaCB3aXRoIHNvbWUgbm90aW9uYWwKPj7CoCBtYXN0ZXIgY2xvY2sgKGUuZy4gdmlhIE5UUCkKPj7CoCAzKSB0d28gY2xvY2tzIGNvdWxkIGJlIGkBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.160.587
References: <20131017032024.5051.20799.idtracker@ietfa.amsl.com> <1381980305.36254.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com> <5263C783.1080001@globis.net> <1382396300.22968.YahooMailNeo@web2801.biz.mail.ne1.yahoo.com> <526616C4.40304@globis.net>
Message-ID: <1382496460.46942.YahooMailNeo@web2802.biz.mail.ne1.yahoo.com>
Date: Tue, 22 Oct 2013 19:47:40 -0700 (PDT)
From: Nalini Elkins <nalini.elkins@insidethestack.com>
Subject: Re: [v6ops] Fw: New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-04.txt
To: Ray Hunter <v6ops@globis.net>
In-Reply-To: <526616C4.40304@globis.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-153701192-410707112-1382496460=:46942"
Cc: v6ops WG <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Nalini Elkins <nalini.elkins@insidethestack.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: Wed, 23 Oct 2013 02:47:49 -0000

---153701192-410707112-1382496460=:46942
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

=0A=0A> Nalini Elkins <mailto:nalini.elkins@insidethestack.com>=0A> 22 Octo=
ber 2013 00:58=0A>>=A0 1) encoding has to be fast, but decoding does not=0A=
>=0A> True=0A>=0A>>=A0 2) a node's clock could be either in our out of sync=
h with some notional=0A>>=A0 master clock (e.g. via NTP)=0A>>=A0 3) two clo=
cks could be in synch to a master source, but the master=0A>>=A0 sources ma=
y themselves not share a common source (one sourced from GPS,=0A>> one from=
 DCF77)=0A>> 4) the key to being able to perform the end to end calculation=
s is=0A>> whether two communicating nodes are synchronised to the same mast=
er=0A>> clock (within some level of error/jitter)=0A>> 5) the absolute time=
 is not particularly important=0A>=0A>=0A> This is true for PDM 1 only.=A0 =
PDM 2 does not require time synchronization.=0A>=0A>>=A0 Q1. Why do you wan=
t to encode differences as deltas in the case of an unsynchronised/ free ru=
nning clock?=0A>>=A0 Isn't that slow, and difficult for hardware implementa=
tions to achieve (e.g. TCP offload)? Doesn't it also require maintaining la=
rge amounts of state in the sending node.=0A>>=0A>=0A> 1. I think that it i=
s going to be interesting to see how hardware is going to handle TCP offloa=
d with IPv6 extension headers.=A0  I do not see why PDM 2 would be so much =
harder than PDM 1 for an OS.=0A> Can you tell me which end host operating s=
ystems are doing TCP offload in hardware?=A0 =0A=0A=0A>IMHO Not a relevant =
question. As a standards body we should be looking=0A>to the future. There =
are many operations that are delegated to microcode.=0A=0A>If you specified=
 the packet with one single way of encapsulating=0A>timestamps, then hardwa=
re or interface microcode could add the timestamp=0A>at the last possible m=
oment before the packet reached the wire, without=0A>having to examine the =
original packet contents, or knowing the context=0A>of the communicating no=
des. I think that's very desirable.=0A=0ASure. =A0 Sounds good! =A0Also loo=
king to the future, then I will speculate that we will likely have more and=
 better time synchronization also.=0A=0A=0A> I know some OS's which process=
 TCP segmentation in hardware.=A0 =A0 But at this point, the packet is alre=
ady crafted.=A0 Also some do IP checksum offload in hardware but that does =
not apply to IPv6 as there is no IP header checksum.=0A=0A>=0A>=0A> 2.=A0 E=
nd hosts already maintain quite a bit of state.=A0 Every OS has control blo=
cks to handle events such as TCP duplicate packets, round trip time, conges=
tion window, etc.=A0  We are NOT suggesting=0A> that the PDM headers be use=
d in middle boxes.=A0 That is, we are NOT asking routers to maintain state.=
=0A=0A=0A>So what? Why add to the problem?=0A=0AYes. =A0Just saying that we=
 are not CREATING the problem.=0A=0A>Why does the timestamp require synchro=
nisation with that other TCP state?=0A=0AIt doesn't. =A0Just mentioning oth=
er reasons why state is maintained.=0A=0A>Isn't it better to define a solut=
ion that is independent of the upper=A0layer header transport protocol?=0A=
=0AYes. =A0Our solution IS independent. =A0I think my analogy actually conf=
used the issue!=0A=0A><heresy>=A0 Why not allow middleboxes (or node hardwa=
re) to insert the=A0timestamp header on the fly?</heresy>=0A=0AInteresting =
idea!=0A=0A>=0A>>=A0 Why not just encode the timestamp as-is and perform th=
e appropriate difference calculation during decoding?=0A>=0A> If clocks are=
 out of synch, you could end up having it look like you received the packet=
 before you sent it.=0A=0A>=A0No. I'm not suggesting you use the same decod=
ing algorithm: only that=A0you define a single common encoding algorithm th=
at combines all the=A0information required for PDM 1 and PDM 2 calculations=
. Having to chose=0A>which packet encoding to use in advance is problematic=
 IMHO.=A0=0A=0AWe will look at this. =A0 I am also meeting with a couple of=
 the end host OS vendors to get their viewpoint on the PDMs. =A0 Their engi=
neers have good opinions on what the problems might be with actually creati=
ng PDMs.=0AI should have that info before Vancouver.=0A=0A>>=A0 Q2. Why do =
you need two separate packet formats at all?=0A>=0A>>=A0 Why not have a com=
mon format for all cases, containing a timestamp based=0A>> on the local cl=
ock, plus an optional field containing a flag that states=0A>> if the local=
 timestamp is coordinated to some master clock, plus an=0A>> identifier for=
 the master clock.=0A>=0A>> You could then encode whether a node had a free=
-running clock (case 2),=0A>> a synchronised clock (case 1), and whether it=
 was synched via NTP to=0A>> some stratum 0 source e.g. GPS, and also some =
identification of the=0A>> stratum 1 source (IPv6 address).=0A>=0A>> Two co=
mmunicating nodes could then use e.g. NTP trace to see if they=0A>> shared =
a common clock source or not, before performing their calculations.=0A>=0A>=
 We are trying to craft a solution with PDM 2 for those situations where ti=
me synchronization is not practical, possible or desired.=0A=0A>I understan=
d the aim, but let me ask my question a different way.=0A=0A>Imagine there =
are nodes A&B that with clocks synched to DCF77.=0A>Imagine there are nodes=
 C&D that with clocks=A0 synched to GPS.=0A>Node E has free running clock (=
possibly because the GPS receiver is down).=0A=0A>Which packet format PDM t=
ype 1 or PDM type 2 do you use between each=0A>pair of nodes, and how does =
the sending node know that?=0A=0A>Scale this solution to 100K hosts.=0A=0AG=
ood question. =A0We were thinking that each node would start with PDM 1 and=
 then if the other side could not do PDM 1, then it would drop back to PDM =
2.=0ABut, the clock issue is good. =A0Now,=A0my understanding is that clock=
 difference has more to do with Stratum levels. =A0 =A0But, I am not the NT=
P expert in the group.=A0=0AI am just wondering (leaving off Node E) how mu=
ch clock difference would there be? =A0 What do you think?=A0I have a meeti=
ng with my team tomorrow &=A0will bring this up for discussion.=0A=0A>=0A> =
------------------------------------------------------------------------=0A=
=0A=0A-- =0ARegards,=0ARayH
---153701192-410707112-1382496460=:46942
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:ar=
ial, helvetica, sans-serif;font-size:12pt"><div><br></div><div style=3D"fon=
t-family: arial, helvetica, sans-serif; font-size: 12pt;"><div style=3D"fon=
t-family: 'times new roman', 'new york', times, serif; font-size: 12pt;"><d=
iv class=3D"y_msg_container">=0A&gt; Nalini Elkins &lt;mailto:<a ymailto=3D=
"mailto:nalini.elkins@insidethestack.com" href=3D"mailto:nalini.elkins@insi=
dethestack.com">nalini.elkins@insidethestack.com</a>&gt;<br>&gt; 22 October=
 2013 00:58<br>&gt;&gt;&nbsp; 1) encoding has to be fast, but decoding does=
 not<br>&gt;<br>&gt; True<br>&gt;<br>&gt;&gt;&nbsp; 2) a node's clock could=
 be either in our out of synch with some notional<br>&gt;&gt;&nbsp; master =
clock (e.g. via NTP)<br>&gt;&gt;&nbsp; 3) two clocks could be in synch to a=
 master source, but the master<br>&gt;&gt;&nbsp; sources may themselves not=
 share a common source (one sourced from GPS,<br>&gt;&gt; one from DCF77)<b=
r>&gt;&gt; 4) the key to being able to perform the end to end calculations =
is<br>&gt;&gt; whether two communicating nodes are synchronised to the same=
 master<br>&gt;&gt; clock (within some level of error/jitter)<br>&gt;&gt; 5=
) the absolute time is not particularly important<br>&gt;<br>&gt;<br>&gt; T=
his is true for PDM 1
 only.&nbsp; PDM 2 does not require time synchronization.<br>&gt;<br>&gt;&g=
t;&nbsp; Q1. Why do you want to encode differences as deltas in the case of=
 an unsynchronised/ free running clock?<br>&gt;&gt;&nbsp; Isn't that slow, =
and difficult for hardware implementations to achieve (e.g. TCP offload)? D=
oesn't it also require maintaining large amounts of state in the sending no=
de.<br>&gt;&gt;<br>&gt;<br>&gt; 1. I think that it is going to be interesti=
ng to see how hardware is going to handle TCP offload with IPv6 extension h=
eaders.&nbsp;  I do not see why PDM 2 would be so much harder than PDM 1 fo=
r an OS.<br>&gt; Can you tell me which end host operating systems are doing=
 TCP offload in hardware?&nbsp;  <br><br></div><div class=3D"y_msg_containe=
r">&gt;IMHO Not a relevant question. As a standards body we should be looki=
ng<br>&gt;to the future. There are many operations that are delegated to mi=
crocode.<br><br>&gt;If you specified the packet with one single way of
 encapsulating<br>&gt;timestamps, then hardware or interface microcode coul=
d add the timestamp<br>&gt;at the last possible moment before the packet re=
ached the wire, without<br>&gt;having to examine the original packet conten=
ts, or knowing the context<br>&gt;of the communicating nodes. I think that'=
s very desirable.</div><div class=3D"y_msg_container"><br></div><div class=
=3D"y_msg_container">Sure. &nbsp; Sounds good! &nbsp;Also looking to the fu=
ture, then I will speculate that we will likely have more and better time s=
ynchronization also.<br></div><div class=3D"y_msg_container"><br></div><div=
 class=3D"y_msg_container"><span style=3D"font-size: 12pt;">&gt; I know som=
e OS's which process TCP segmentation in hardware.&nbsp; &nbsp; But at this=
 point, the packet is already crafted.&nbsp; Also some do IP checksum offlo=
ad in hardware but that does not apply to IPv6 as there is no IP header che=
cksum.</span><br></div><div class=3D"y_msg_container">&gt;<br>&gt;<br>&gt;
 2.&nbsp; End hosts already maintain quite a bit of state.&nbsp; Every OS h=
as control blocks to handle events such as TCP duplicate packets, round tri=
p time, congestion window, etc.&nbsp;  We are NOT suggesting<br>&gt; that t=
he PDM headers be used in middle boxes.&nbsp; That is, we are NOT asking ro=
uters to maintain state.<br><br></div><div class=3D"y_msg_container">&gt;So=
 what? Why add to the problem?<br><br>Yes. &nbsp;Just saying that we are no=
t CREATING the problem.<br><br><span style=3D"font-size: 12pt;">&gt;Why doe=
s the timestamp require synchronisation with that other TCP state?</span></=
div><div class=3D"y_msg_container"><br></div><div class=3D"y_msg_container"=
>It doesn't. &nbsp;Just mentioning other reasons why state is maintained.</=
div><div class=3D"y_msg_container"><br></div><div class=3D"y_msg_container"=
>&gt;Isn't it better to define a solution that is independent of the upper&=
nbsp;layer header transport protocol?</div><div
 class=3D"y_msg_container"><br></div><div class=3D"y_msg_container">Yes. &n=
bsp;Our solution IS independent. &nbsp;I think my analogy actually confused=
 the issue!</div><div class=3D"y_msg_container"><br></div><div class=3D"y_m=
sg_container">&gt;<span style=3D"font-size: 12pt;">&lt;heresy&gt;&nbsp; Why=
 not allow middleboxes (or node hardware) to insert the&nbsp;</span><span s=
tyle=3D"font-size: 12pt;">timestamp header on the fly?&lt;/heresy&gt;</span=
></div><div class=3D"y_msg_container"><span style=3D"font-size: 12pt;"><br>=
</span></div><div class=3D"y_msg_container"><span style=3D"font-size: 12pt;=
">Interesting idea!</span></div><div class=3D"y_msg_container"><span style=
=3D"font-size: 12pt;"><br></span></div><div class=3D"y_msg_container">&gt;<=
br>&gt;&gt;&nbsp; Why not just encode the timestamp as-is and perform the a=
ppropriate difference calculation during decoding?<br>&gt;<br>&gt; If clock=
s are out of synch, you could end up having it look like you received the p=
acket before you
 sent it.<br><br>&gt;&nbsp;No. I'm not suggesting you use the same decoding=
 algorithm: only that&nbsp;you define a single common encoding algorithm th=
at combines all the&nbsp;information required for PDM 1 and PDM 2 calculati=
ons. Having to chose</div><div class=3D"y_msg_container">&gt;which packet e=
ncoding to use in advance is problematic IMHO.&nbsp;</div><div class=3D"y_m=
sg_container"><br></div><div class=3D"y_msg_container">We will look at this=
. &nbsp; I am also meeting with a couple of the end host OS vendors to get =
their viewpoint on the PDMs. &nbsp; Their engineers have good opinions on w=
hat the problems might be with actually creating PDMs.</div><div class=3D"y=
_msg_container">I should have that info before Vancouver.<br><br>&gt;&gt;&n=
bsp; Q2. Why do you need two separate packet formats at all?<br>&gt;<br>&gt=
;&gt;&nbsp; Why not have a common format for all cases, containing a timest=
amp based<br>&gt;&gt; on the local clock, plus an optional field containing
 a flag that states<br>&gt;&gt; if the local timestamp is coordinated to so=
me master clock, plus an<br>&gt;&gt; identifier for the master clock.<br>&g=
t;<br>&gt;&gt; You could then encode whether a node had a free-running cloc=
k (case 2),<br>&gt;&gt; a synchronised clock (case 1), and whether it was s=
ynched via NTP to<br>&gt;&gt; some stratum 0 source e.g. GPS, and also some=
 identification of the<br>&gt;&gt; stratum 1 source (IPv6 address).<br>&gt;=
<br>&gt;&gt; Two communicating nodes could then use e.g. NTP trace to see i=
f they<br>&gt;&gt; shared a common clock source or not, before performing t=
heir calculations.<br>&gt;<br>&gt; We are trying to craft a solution with P=
DM 2 for those situations where time synchronization is not practical, poss=
ible or desired.<br><br>&gt;I understand the aim, but let me ask my questio=
n a different way.<br><br>&gt;Imagine there are nodes A&amp;B that with clo=
cks synched to DCF77.<br>&gt;Imagine there are nodes C&amp;D that
 with clocks&nbsp; synched to GPS.</div><div class=3D"y_msg_container">&gt;=
Node E has free running clock (possibly because the GPS receiver is down).<=
br><br>&gt;Which packet format PDM type 1 or PDM type 2 do you use between =
each</div><div class=3D"y_msg_container">&gt;pair of nodes, and how does th=
e sending node know that?</div><div class=3D"y_msg_container"><br></div><di=
v class=3D"y_msg_container">&gt;Scale this solution to 100K hosts.</div><di=
v class=3D"y_msg_container"><br></div><div class=3D"y_msg_container">Good q=
uestion. &nbsp;We were thinking that each node would start with PDM 1 and t=
hen if the other side could not do PDM 1, then it would drop back to PDM 2.=
</div><div class=3D"y_msg_container"><span style=3D"font-size: 12pt;">But, =
the clock issue is good. &nbsp;</span><span style=3D"font-size: 12pt;">Now,=
&nbsp;</span><span style=3D"font-size: 12pt;">my understanding is that cloc=
k difference has more to do with Stratum levels. &nbsp; &nbsp;But, I am not=
 the NTP
 expert in the group.&nbsp;</span></div><div class=3D"y_msg_container"><spa=
n style=3D"font-size: 12pt;">I am just wondering (l</span><span style=3D"fo=
nt-size: 12pt;">eaving off Node E) how much clock difference would there be=
? &nbsp; What do you think?&nbsp;</span><span style=3D"font-size: 12pt;">I =
have a meeting with my team tomorrow &amp;&nbsp;</span><span style=3D"font-=
size: 12pt;">will bring this up for discussion.</span></div><div class=3D"y=
_msg_container"><br>&gt;<br>&gt; ------------------------------------------=
------------------------------<br><br><br>-- <br>Regards,<br>RayH<br><br><b=
r><br></div> </div> </div>  </div></body></html>
---153701192-410707112-1382496460=:46942--

From swmike@swm.pp.se  Tue Oct 22 20:44:57 2013
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1060C11E82C6 for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 20:44:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mi4wk1bfMmiU for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 20:44:56 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id 608F311E82B9 for <ipv6@ietf.org>; Tue, 22 Oct 2013 20:44:56 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id EEB1B9C; Wed, 23 Oct 2013 05:44:51 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id E2ED99A for <ipv6@ietf.org>; Wed, 23 Oct 2013 05:44:51 +0200 (CEST)
Date: Wed, 23 Oct 2013 05:44:51 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: 6man WG <ipv6@ietf.org>
Subject: Re: Need for an overview [was ND Option for NMS Discovery-//FW: New Version Notification for draft-liu-6man-nd-nms-discovery-00.txt]
In-Reply-To: <CAC8QAcexEdFJmVdNeqL10HiFmbcHU9xr5qLcU58Ud-sb3njC0g@mail.gmail.com>
Message-ID: <alpine.DEB.2.02.1310230542410.1838@uplift.swm.pp.se>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC189@nkgeml506-mbx.china.huawei.com> <alpine.DEB.2.02.1310221010170.8663@uplift.swm.pp.se> <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC43D@nkgeml506-mbx.china.huawei.com> <alpine.DEB.2.02.1310221102190.8663@uplift.swm.pp.se> <5266E462.9050901@gmail.com> <CAC8QAcexEdFJmVdNeqL10HiFmbcHU9xr5qLcU58Ud-sb3njC0g@mail.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
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 23 Oct 2013 03:44:57 -0000

On Tue, 22 Oct 2013, Behcet Sarikaya wrote:

> When new needs come up, why not add new RA options?

Of course we should add, it just depends on definition when it's "needed". 
Why not put NTP server in there? TFTP server? DNSSEC KSK bootstrapping? IP 
address for Facebook (everybody uses that, right?!).

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

From leo.liubing@huawei.com  Tue Oct 22 20:56:03 2013
Return-Path: <leo.liubing@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D11CB11E8125 for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 20:56:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.508
X-Spam-Level: 
X-Spam-Status: No, score=-6.508 tagged_above=-999 required=5 tests=[AWL=0.090,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id svAQnMAaIley for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 20:55:58 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8EF2711E8112 for <ipv6@ietf.org>; Tue, 22 Oct 2013 20:55:54 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AXB83828; Wed, 23 Oct 2013 03:55:53 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 23 Oct 2013 04:55:52 +0100
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; Wed, 23 Oct 2013 04:55:52 +0100
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.141]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.03.0146.000; Wed, 23 Oct 2013 11:55:42 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>, "<sarikaya@ieee.org>" <sarikaya@ieee.org>
Subject: RE: Need for an overview [was ND Option for NMS Discovery-//FW: New Version Notification for draft-liu-6man-nd-nms-discovery-00.txt]
Thread-Topic: Need for an overview [was ND Option for NMS Discovery-//FW: New	Version Notification for draft-liu-6man-nd-nms-discovery-00.txt]
Thread-Index: AQHOz28rh7rcUg1akU66p7/AtxZ+GpoBDK0AgACV11A=
Date: Wed, 23 Oct 2013 03:55:41 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC82F@nkgeml506-mbx.china.huawei.com>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC189@nkgeml506-mbx.china.huawei.com> <alpine.DEB.2.02.1310221010170.8663@uplift.swm.pp.se> <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC43D@nkgeml506-mbx.china.huawei.com> <alpine.DEB.2.02.1310221102190.8663@uplift.swm.pp.se> <5266E462.9050901@gmail.com>, <CAC8QAcexEdFJmVdNeqL10HiFmbcHU9xr5qLcU58Ud-sb3njC0g@mail.gmail.com> <107C239B-C80A-41EF-B6AF-765D3E3746E9@huawei.com>
In-Reply-To: <107C239B-C80A-41EF-B6AF-765D3E3746E9@huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.132]
Content-Type: multipart/alternative; boundary="_000_8AE0F17B87264D4CAC7DE0AA6C406F453D7CC82Fnkgeml506mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 23 Oct 2013 03:56:03 -0000

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

Hi, Tina & All

I think both your draft  http://datatracker.ietf.org/doc/draft-schoenw-opsa=
wg-nm-dhc<http://datatracker.ietf.org/doc/draft-schoenw-opsawg-nm-dhc/>

and Mikael's draft: http://datatracker.ietf.org/doc/draft-fa-netconf-dhcpv6=
-option
are related.

For my own understanding, the two drafts are regarding specific NMS types/m=
ethod, one is for SNMP the other is for Netconf.
The ND option document is intend to be a general usage, whatever the NMS is=
, when a device is getting online, the neighbors could tell it.

Regards,
Bing

From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of Tin=
a TSOU
Sent: Wednesday, October 23, 2013 10:38 AM
To: <sarikaya@ieee.org>
Cc: 6man WG
Subject: Re: Need for an overview [was ND Option for NMS Discovery-//FW: Ne=
w Version Notification for draft-liu-6man-nd-nms-discovery-00.txt]

Dear all,
IMHO, it is related to http://datatracker.ietf.org/doc/draft-schoenw-opsawg=
-nm-dhc<http://datatracker.ietf.org/doc/draft-schoenw-opsawg-nm-dhc/>/
What do u think about this?

Thank you,
Tina

On Oct 22, 2013, at 2:39 PM, "Behcet Sarikaya" <sarikaya2012@gmail.com<mail=
to:sarikaya2012@gmail.com>> wrote:


On Tue, Oct 22, 2013 at 3:47 PM, Brian E Carpenter <brian.e.carpenter@gmail=
.com<mailto:brian.e.carpenter@gmail.com>> wrote:
As I said when commenting on the draft charter recently:

I think there's a missing goal, something like

 - Define relationship and boundary between DHCPv6-based and RA/ND-based
   host configuration mechanisms. (This is partly an operational topic, but
   it lies behind a whole bunch of discussions in various WGs).

Unless we get this settled as a general matter, the discussion below will
continue to occur every time an RA/ND extension or a routing-related
DHCPv6 option is proposed.

I think we should separate SLAAC and stateful address configuration with DH=
CPv6 versus
RA options for routing as in RFC 4191.
Why? Because the former is already in the RFCs, RFC 4861 and RFC 3315 while=
 for the latter, the DHCP proposal did not go through.
For the latter, the issue is should we add new RA options?
My answer is we should, the last time this has been done was in RFC 6106. W=
hen new needs come up, why not add new RA options?
Regards,
Behcet
Regards
   Brian

On 22/10/2013 22:08, Mikael Abrahamsson wrote:
> On Tue, 22 Oct 2013, Liubing (Leo) wrote:
>
>> [Bing] I'm afraid I can't agree, some scenarios might not involve
>> DHCP, e.g. in the core networks, but ND is always on in IPv6. If the
>> neighbors already knew something, it is quite convenient to propagate
>> the information through ND.
>
> Why stop here then, there are a lot of other things we could put into ND
> that would also be convenient?
>
>> May I ask the specific reasons that you prefer DHCPv6 over ND?
>
> Because before a router knows anything, it's a host, not a router.
> DHCPv6 is a "host" protocol. It was designed to do these things. There
> is no reason a router can't use DHCP to aquire knowledge, it's done
> using for instance DHCPv6-PD. Doesn't matter if it's a core router or not=
.
>
> DHCP is used when someone wants to know something, in ND/RA things are
> announced all the time, periodically. I don't think putting "everything"
> there is a good engineering solution. For better or for worse, we have
> the separation between ND/RA and DHCP for different things, and I think
> it should be continued.
>
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org<mailto:ipv6@ietf.org>
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:m=3D"http://schema=
s.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html=
40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"\7EAF\6587\672C Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.Char
	{mso-style-name:"\7EAF\6587\672C Char";
	mso-style-priority:99;
	mso-style-link:\7EAF\6587\672C;
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"ZH-CN" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi, Tina &=
amp; All<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">I think bo=
th your draft
</span><span lang=3D"EN-US">&nbsp;<a href=3D"http://datatracker.ietf.org/do=
c/draft-schoenw-opsawg-nm-dhc/">http://datatracker.ietf.org/doc/draft-schoe=
nw-opsawg-nm-dhc</a></span><span lang=3D"EN-US" style=3D"font-size:10.5pt;f=
ont-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p><=
/o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"color:#1F497D">and =
Mikael&#8217;s draft:
</span><span lang=3D"EN-US"><a href=3D"http://datatracker.ietf.org/doc/draf=
t-fa-netconf-dhcpv6-option">http://datatracker.ietf.org/doc/draft-fa-netcon=
f-dhcpv6-option</a><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">are relate=
d.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">For my own=
 understanding, the two drafts are regarding specific NMS types/method, one=
 is for SNMP the other is for Netconf.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">The ND opt=
ion document is intend to be a general usage, whatever the NMS is, when a d=
evice is getting online, the neighbors could tell it.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Regards,<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Bing<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org]
<b>On Behalf Of </b>Tina TSOU<br>
<b>Sent:</b> Wednesday, October 23, 2013 10:38 AM<br>
<b>To:</b> &lt;sarikaya@ieee.org&gt;<br>
<b>Cc:</b> 6man WG<br>
<b>Subject:</b> Re: Need for an overview [was ND Option for NMS Discovery-/=
/FW: New Version Notification for draft-liu-6man-nd-nms-discovery-00.txt]<o=
:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Dear all,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">IMHO, it is related to&nbsp;<a =
href=3D"http://datatracker.ietf.org/doc/draft-schoenw-opsawg-nm-dhc/">http:=
//datatracker.ietf.org/doc/draft-schoenw-opsawg-nm-dhc</a>/<br>
What do u think about this?<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Thank you,<o:p></o:p></span></p=
>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Tina<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
<br>
On Oct 22, 2013, at 2:39 PM, &quot;Behcet Sarikaya&quot; &lt;<a href=3D"mai=
lto:sarikaya2012@gmail.com">sarikaya2012@gmail.com</a>&gt; wrote:<o:p></o:p=
></span></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt;-webkit-text-size=
-adjust: auto">
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
<o:p>&nbsp;</o:p></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">On Tue, Oct 22, 2013 at 3:47 PM=
, Brian E Carpenter &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" targ=
et=3D"_blank">brian.e.carpenter@gmail.com</a>&gt; wrote:<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
As I said when commenting on the draft charter recently:<br>
<br>
I think there's a missing goal, something like<br>
<br>
&nbsp;- Define relationship and boundary between DHCPv6-based and RA/ND-bas=
ed<br>
&nbsp; &nbsp;host configuration mechanisms. (This is partly an operational =
topic, but<br>
&nbsp; &nbsp;it lies behind a whole bunch of discussions in various WGs).<b=
r>
<br>
Unless we get this settled as a general matter, the discussion below will<b=
r>
continue to occur every time an RA/ND extension or a routing-related<br>
DHCPv6 option is proposed.<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I think we should separate SLAA=
C and stateful address configuration with DHCPv6 versus<o:p></o:p></span></=
p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
RA options for routing as in RFC 4191.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
Why? Because the former is already in the RFCs, RFC 4861 and RFC 3315 while=
 for the latter, the DHCP proposal did not go through.<o:p></o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">For the latter, the issue is sh=
ould we add new RA options?<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
My answer is we should, the last time this has been done was in RFC 6106. W=
hen new needs come up, why not add new RA options?<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
Regards,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Behcet<o:p></o:p></span></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class=3D"MsoNormal"><span lang=3D"EN-US">Regards<br>
&nbsp; &nbsp;Brian<br>
<br>
On 22/10/2013 22:08, Mikael Abrahamsson wrote:<br>
&gt; On Tue, 22 Oct 2013, Liubing (Leo) wrote:<br>
&gt;<br>
&gt;&gt; [Bing] I'm afraid I can't agree, some scenarios might not involve<=
br>
&gt;&gt; DHCP, e.g. in the core networks, but ND is always on in IPv6. If t=
he<br>
&gt;&gt; neighbors already knew something, it is quite convenient to propag=
ate<br>
&gt;&gt; the information through ND.<br>
&gt;<br>
&gt; Why stop here then, there are a lot of other things we could put into =
ND<br>
&gt; that would also be convenient?<br>
&gt;<br>
&gt;&gt; May I ask the specific reasons that you prefer DHCPv6 over ND?<br>
&gt;<br>
&gt; Because before a router knows anything, it's a host, not a router.<br>
&gt; DHCPv6 is a &quot;host&quot; protocol. It was designed to do these thi=
ngs. There<br>
&gt; is no reason a router can't use DHCP to aquire knowledge, it's done<br=
>
&gt; using for instance DHCPv6-PD. Doesn't matter if it's a core router or =
not.<br>
&gt;<br>
&gt; DHCP is used when someone wants to know something, in ND/RA things are=
<br>
&gt; announced all the time, periodically. I don't think putting &quot;ever=
ything&quot;<br>
&gt; there is a good engineering solution. For better or for worse, we have=
<br>
&gt; the separation between ND/RA and DHCP for different things, and I thin=
k<br>
&gt; it should be continued.<br>
&gt;<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>
--------------------------------------------------------------------<o:p></=
o:p></span></p>
</blockquote>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</body>
</html>

--_000_8AE0F17B87264D4CAC7DE0AA6C406F453D7CC82Fnkgeml506mbxchi_--

From brian.e.carpenter@gmail.com  Tue Oct 22 20:56:08 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2009A11E8234 for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 20:56:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.536
X-Spam-Level: 
X-Spam-Status: No, score=-102.536 tagged_above=-999 required=5 tests=[AWL=0.063, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hf8aVWe2lf0V for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 20:56:07 -0700 (PDT)
Received: from mail-pb0-x231.google.com (mail-pb0-x231.google.com [IPv6:2607:f8b0:400e:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id A785C11E8112 for <ipv6@ietf.org>; Tue, 22 Oct 2013 20:56:04 -0700 (PDT)
Received: by mail-pb0-f49.google.com with SMTP id xb12so304636pbc.36 for <ipv6@ietf.org>; Tue, 22 Oct 2013 20:56:04 -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=OGSyWRrfbNNGPtAB5QU/GgdpKc9eDz46hqnfiUt/gU4=; b=faZhXbwsFNhUPeqxhTd0uTwlVU7QlzYkT6Tk1BCFCGIjuYYwsLk0Pmk/yNKTPJBB9P WdkMBImCFk89xLjGsUsb6Z3FeHoCcer2bGSNfvs7CilFKF0GEds6NCNWRfg68e6r2ouT /E9N5jqYXBghVrV+ued8zfUKoLikov6nsVS8Lv5qJmYTztqlh1c/PeaNzTUV4YN+NKiF EDE30fLbngTHZfZTovKVLS6DnHOZrCy1zJR85bvNg4dfco9XxAudyzjS9lOxRMpXMbAU QaHos2PqnAT2xuJ2yDTL7JQjXTbA7C5qkHISDSHGa0QbdvUiUcYV9FltHqzvPz59fXw2 NZdw==
X-Received: by 10.66.119.78 with SMTP id ks14mr1112259pab.140.1382500564219; Tue, 22 Oct 2013 20:56:04 -0700 (PDT)
Received: from [192.168.178.20] (178.193.69.111.dynamic.snap.net.nz. [111.69.193.178]) by mx.google.com with ESMTPSA id at4sm1233380pbc.30.2013.10.22.20.56.01 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 22 Oct 2013 20:56:03 -0700 (PDT)
Message-ID: <526748D7.6000701@gmail.com>
Date: Wed, 23 Oct 2013 16:56:07 +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: Need for an overview [was ND Option for NMS Discovery-//FW: New Version Notification for draft-liu-6man-nd-nms-discovery-00.txt]
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC189@nkgeml506-mbx.china.huawei.com>	<alpine.DEB.2.02.1310221010170.8663@uplift.swm.pp.se>	<8AE0F17B87264D4CAC7DE0AA6C406F453D7CC43D@nkgeml506-mbx.china.huawei.com>	<alpine.DEB.2.02.1310221102190.8663@uplift.swm.pp.se>	<5266E462.9050901@gmail.com>	<CAC8QAcexEdFJmVdNeqL10HiFmbcHU9xr5qLcU58Ud-sb3njC0g@mail.gmail.com> <alpine.DEB.2.02.1310230542410.1838@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1310230542410.1838@uplift.swm.pp.se>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 23 Oct 2013 03:56:08 -0000

On 23/10/2013 16:44, Mikael Abrahamsson wrote:
> On Tue, 22 Oct 2013, Behcet Sarikaya wrote:
> 
>> When new needs come up, why not add new RA options?
> 
> Of course we should add, it just depends on definition when it's
> "needed". Why not put NTP server in there? TFTP server? DNSSEC KSK
> bootstrapping? IP address for Facebook (everybody uses that, right?!).
> 

The problem is getting new options implemented and deployed.
RFC 6016 is hardly available, for example (see recent
discussion on the ipv6-ops@lists.cluenet.de list).

I'm not saying the situation is any better with new DHCPv6 options,
but duplication of solutions definitely makes deployment harder.

   Brian

From lorenzo@google.com  Tue Oct 22 21:20:43 2013
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38AD711E811D for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 21:20:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.927
X-Spam-Level: 
X-Spam-Status: No, score=-1.927 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PxT5lGv3ue0E for <ipv6@ietfa.amsl.com>; Tue, 22 Oct 2013 21:20:42 -0700 (PDT)
Received: from mail-ie0-x22b.google.com (mail-ie0-x22b.google.com [IPv6:2607:f8b0:4001:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 88A8111E8119 for <ipv6@ietf.org>; Tue, 22 Oct 2013 21:20:39 -0700 (PDT)
Received: by mail-ie0-f171.google.com with SMTP id tp5so443356ieb.30 for <ipv6@ietf.org>; Tue, 22 Oct 2013 21:20:38 -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=PUo+sCKfQMh6A3Wr8SIEaIpsctd6AOyxe6RSiZTx3GI=; b=cS2PV+QOdsDutLgZqfLhHXVTCSNx/9odj7O00eKIrzi2P1OZRLMePw+CeO8PxwV/zM xlQUvn/IyZfUUUW0/wiDKK/dFOhCW9EJz/FEOxCeG3AXOZhtpe27BK5Afxks2NZTlKe+ KMggwNP447i4iA0d6bNelFclmTbmMV/1u3SVVIevi/yGMta/BJmuWWii6vdnK4OmGKBb GeXeAX+6GKFC1MELscf2LfrKKQsCCL/gjrEY/n/hCT1UOoEUMUF+eoXn25e5/t5FGrPt Mz+5y69eJQl1doO8LQMsqYKQOWRnjl3tVuIJjkc6qqqMMma0xGguLlXI1n82n9Pf5Oj5 4AGA==
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=PUo+sCKfQMh6A3Wr8SIEaIpsctd6AOyxe6RSiZTx3GI=; b=NmGsMzUo/qeQVHzg4Kt0iA90B5uLKWS8t9HNndHLv2gActny6I4pKo/wSdAmmOgCTN JZbUkPOc9enscEGrFb/jQOcIN0JgI73SOnhZHpJcamSvlFPsy37PeOoWkVsNZ0K1CHYZ cIaITSOWDgv7rhgncHldY0bPZbuCthxvifzmAtsWHpOCo71OQriPZTo6zYgA9+E/zXh5 eI7LcYPbzDdoEpKADVpOFhFudPMbh5bkYTj84ZXjnSJpF+ksvuvlKb7gfovlPnOYwCwh mDibxGnOOK5i24VUcuGrp4y1ciGGIVamq/P/GFyHVrfAXjj/5S5npute/Mp3UsEqv/7m RORQ==
X-Gm-Message-State: ALoCoQmNOueoTmFvrPlTkP2fzkBRv0xfMKha6kn8KiLuEuzbJTWwWoGP76LX+KpSadQj7P45pCaWrZVO0/clXxK1RtMtrephY7VmFH6VyTMHyxeISox1VDaEl2cziGCLShG2YxVsJSKfp1NgfFejSdPtnRpMfFn/84dnF2VSIosD7bSCbsAho0oVVACD17nTRC5bhNC8uH0A
X-Received: by 10.42.227.72 with SMTP id iz8mr4110010icb.27.1382502038621; Tue, 22 Oct 2013 21:20:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.86.106 with HTTP; Tue, 22 Oct 2013 21:20:18 -0700 (PDT)
In-Reply-To: <8392F9BAC6AD5F47920216A6D7853F7E1D57D48A@BPXM02GP.gisp.nec.co.jp>
References: <20131021044241.22753.19800.idtracker@ietfa.amsl.com> <8392F9BAC6AD5F47920216A6D7853F7E1D57D48A@BPXM02GP.gisp.nec.co.jp>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 23 Oct 2013 13:20:18 +0900
Message-ID: <CAKD1Yr24yJzGruR5N2Ja4XPTCqD6K=4CmGuHztVmHcynG5AUiQ@mail.gmail.com>
Subject: Re: I-D Action: draft-kitamura-ipv6-zoneid-free-01.txt
To: Hiroshi Kitamura <kitamura@da.jp.nec.com>
Content-Type: multipart/alternative; boundary=001a11c3d304e9efe104e960d64d
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "Ata, Shingo \(ata@info.eng.osaka-cu.ac.jp\)" <ata@info.eng.osaka-cu.ac.jp>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 23 Oct 2013 04:20:43 -0000

--001a11c3d304e9efe104e960d64d
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Oct 23, 2013 at 11:30 AM, Hiroshi Kitamura
<kitamura@da.jp.nec.com>wrote:

> Please, let us know your comments or interest on this idea.
>

The reason why scope IDs exist is that the same address might exist on more
than one interface. The document does not solve this problem.

Example: what if there is a fe80::1 on two different interfaces? Sending a
packet to fe80::1 will cause two NSes to be transmitted, and two ND cache
entries to be created. What happens then? Do data packets also sent to both
neighbours? If so, which one? And if not, why not?

It might help if the document had a clear use case. But there are no real
examples of where this is a problem. The draft does says that the scope ID
is hard to type, and that cannot be shared, and can change, but it doesn't
say why the network is using link-local addresses instead of global
addresses or ULA.

If the justification is "to make it simpler for end users to deal with
link-local addresses", then why not use names (e.g., via link-local
multicast DNS)? Exposing end users to IPv6 addresses does not seem like a
good solution.

--001a11c3d304e9efe104e960d64d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Wed, Oct 23, 2013 at 11:30 AM, Hiroshi Kitamura <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:kitamura@da.jp.nec.com" target=3D"_blank">=
kitamura@da.jp.nec.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra">=
<div class=3D"gmail_quote">

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Please, let us know your comments or interes=
t on this idea.<br></blockquote><div><br></div><div>The reason why scope ID=
s exist is that the same address might exist on more than one interface. Th=
e document does not solve this problem.</div>

<div><br></div><div>Example: what if there is a fe80::1 on two different in=
terfaces? Sending a packet to fe80::1 will cause two NSes to be transmitted=
, and two ND cache entries to be created. What happens then? Do data packet=
s also sent to both neighbours? If so, which one? And if not, why not?</div=
>

<div><br></div><div>It might help if the document had a clear use case. But=
 there are no real examples of where this is a problem. The draft does says=
 that the scope ID is hard to type, and that cannot be shared, and can chan=
ge, but it doesn&#39;t say why the network is using link-local addresses in=
stead of global addresses or ULA.</div>

<div><br></div><div>If the justification is &quot;to make it simpler for en=
d users to deal with link-local addresses&quot;, then why not use names (e.=
g., via link-local multicast DNS)? Exposing end users to IPv6 addresses doe=
s not seem like a good solution.</div>

</div></div></div>

--001a11c3d304e9efe104e960d64d--

From dougb@dougbarton.us  Wed Oct 23 00:34:44 2013
Return-Path: <dougb@dougbarton.us>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59E3411E8318 for <ipv6@ietfa.amsl.com>; Wed, 23 Oct 2013 00:34:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lUHP6PN6jogx for <ipv6@ietfa.amsl.com>; Wed, 23 Oct 2013 00:34:43 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id 64F5E11E815A for <ipv6@ietf.org>; Wed, 23 Oct 2013 00:34:43 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:80a5:a6bf:ce73:5730] (unknown [IPv6:2001:470:d:5e7:80a5:a6bf:ce73:5730]) by dougbarton.us (Postfix) with ESMTPSA id C9EB622B26 for <ipv6@ietf.org>; Wed, 23 Oct 2013 07:34:42 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1382513682; bh=gEVy8+kk0RupZT5QOMPxdfwmXhWtYQQnbTlsoNL+Fzo=; h=Date:From:To:Subject:References:In-Reply-To; b=PnTPGnuDF5xPAgqaSbnTab9DuyoEXD1r8oP7Z5rr4SXBlXXNhB+fntgrpOsnMmSkf F9HMGkrr4IQVqnqNFDbVdFXYIvk0r1SUNYe4FoT/cFFDT5rnYITEDuboGq6QKAHQte Net8C9oi4xR26ZBX/srxiwJeD45hV4JjYF2uL6Zc=
Message-ID: <52677C12.5040802@dougbarton.us>
Date: Wed, 23 Oct 2013 00:34:42 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: 6man <ipv6@ietf.org>
Subject: Re: Need for an overview [was ND Option for NMS Discovery-//FW: New Version Notification for draft-liu-6man-nd-nms-discovery-00.txt]
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC189@nkgeml506-mbx.china.huawei.com>	<alpine.DEB.2.02.1310221010170.8663@uplift.swm.pp.se>	<8AE0F17B87264D4CAC7DE0AA6C406F453D7CC43D@nkgeml506-mbx.china.huawei.com>	<alpine.DEB.2.02.1310221102190.8663@uplift.swm.pp.se>	<5266E462.9050901@gmail.com>	<5266E828.2000501@dougbarton.us> <CAKFn1SFcKuw8xNeqTWN4h68XdQDXqv_GmF4rUUNKq2tcSTjByA@mail.gmail.com>
In-Reply-To: <CAKFn1SFcKuw8xNeqTWN4h68XdQDXqv_GmF4rUUNKq2tcSTjByA@mail.gmail.com>
X-Enigmail-Version: 1.6
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 23 Oct 2013 07:34:44 -0000

On 10/22/2013 02:26 PM, Roger Jørgensen wrote:
>
> I used to say we should keep them separate, not add things into DHCPv6
> that ND does, and the other way around. And I still belive they're not
> really part of the same domain, or use cases.

In a sense I think you're right about them being different use cases, 
but keeping them totally separate isn't the right answer. "The market" 
has been asking for full-featured DHCPv6 basically since day 1. We still 
haven't delivered on that.

> I am against adding more to ND, let's keep it clean and neat. But I'm
> in favour of adding more into DHCPv6. We probably can get consensus on
> changing thing this time around :)

One can only hope. :)

Doug


From rogerj@gmail.com  Wed Oct 23 00:48:44 2013
Return-Path: <rogerj@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1A7A11E8171 for <ipv6@ietfa.amsl.com>; Wed, 23 Oct 2013 00:48:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.274
X-Spam-Level: 
X-Spam-Status: No, score=-2.274 tagged_above=-999 required=5 tests=[AWL=0.026,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oDF25mAg2Rh8 for <ipv6@ietfa.amsl.com>; Wed, 23 Oct 2013 00:48:43 -0700 (PDT)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 9606411E816B for <ipv6@ietf.org>; Wed, 23 Oct 2013 00:48:40 -0700 (PDT)
Received: by mail-wi0-f172.google.com with SMTP id ez12so6888889wid.5 for <ipv6@ietf.org>; Wed, 23 Oct 2013 00:48:39 -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 :cc:content-type:content-transfer-encoding; bh=QqdbWK0khhEzPx26o+jhQFXXOj41vp4rxUP/XdJLWAM=; b=v+CRfeVPpYGwvNEl85cfTFMfBkEjR/ySRoPEc6Hsd2G1eMsI4F7+UN/982vITlxzyi aIkRWrMBII9VFkfnqJMOxjH/a1UA0cwhXzTFoiX8phHukk0a0QGh/659uZ2QzthDY5Te R6QS78udgWUWck7Q5eCnaHNRIvYMR3aIodqWWqK3+GJga46pL8CHVVNvF4m8htvHe0ev 4Ic9spkNXWr/sxwKL3FdJ1WL8CwUftuzeFvB0FvS5Fv5BZpkE8qQPbGv4//sKnL6/Qje ovzUn+2xO8FH+2fgq3W/3Snu0zABlNlkMHsfeF4M+FidjS4WmZVQPAuNN2SMFZHWgcRG pdvg==
MIME-Version: 1.0
X-Received: by 10.194.20.230 with SMTP id q6mr204959wje.49.1382514519925; Wed, 23 Oct 2013 00:48:39 -0700 (PDT)
Received: by 10.216.213.72 with HTTP; Wed, 23 Oct 2013 00:48:39 -0700 (PDT)
In-Reply-To: <52677C12.5040802@dougbarton.us>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC189@nkgeml506-mbx.china.huawei.com> <alpine.DEB.2.02.1310221010170.8663@uplift.swm.pp.se> <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC43D@nkgeml506-mbx.china.huawei.com> <alpine.DEB.2.02.1310221102190.8663@uplift.swm.pp.se> <5266E462.9050901@gmail.com> <5266E828.2000501@dougbarton.us> <CAKFn1SFcKuw8xNeqTWN4h68XdQDXqv_GmF4rUUNKq2tcSTjByA@mail.gmail.com> <52677C12.5040802@dougbarton.us>
Date: Wed, 23 Oct 2013 09:48:39 +0200
Message-ID: <CAKFn1SH97aX0BUqvoZpQX=j6vzVNafP5Z2BexZ1NNQ_Fd2zgng@mail.gmail.com>
Subject: Re: Need for an overview [was ND Option for NMS Discovery-//FW: New Version Notification for draft-liu-6man-nd-nms-discovery-00.txt]
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: Doug Barton <dougb@dougbarton.us>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 23 Oct 2013 07:48:45 -0000

On Wed, Oct 23, 2013 at 9:34 AM, Doug Barton <dougb@dougbarton.us> wrote:
> On 10/22/2013 02:26 PM, Roger J=F8rgensen wrote:

>> I used to say we should keep them separate, not add things into DHCPv6
>> that ND does, and the other way around. And I still belive they're not
>> really part of the same domain, or use cases.
>
>
> In a sense I think you're right about them being different use cases, but
> keeping them totally separate isn't the right answer. "The market" has be=
en
> asking for full-featured DHCPv6 basically since day 1. We still haven't
> delivered on that.

I think it's time we give them full-featured DHCPv6.


>> I am against adding more to ND, let's keep it clean and neat. But I'm
>> in favour of adding more into DHCPv6. We probably can get consensus on
>> changing thing this time around :)
>
>
> One can only hope. :)

let's give it a go? I know of other that also think it's about time to
get this done now.
I'm more than happy to discuss and help out with ideas, but I'm not
there yet that I can write drafts... sort of language has never been
one of my strongest side :(



--=20

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

From tom.taylor.stds@gmail.com  Wed Oct 23 05:06:38 2013
Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6E1011E8183 for <ipv6@ietfa.amsl.com>; Wed, 23 Oct 2013 05:06:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.636
X-Spam-Level: 
X-Spam-Status: No, score=-2.636 tagged_above=-999 required=5 tests=[AWL=-0.036, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O4I2zh2zzE2u for <ipv6@ietfa.amsl.com>; Wed, 23 Oct 2013 05:06:38 -0700 (PDT)
Received: from mail-ie0-x234.google.com (mail-ie0-x234.google.com [IPv6:2607:f8b0:4001:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id B155F11E818B for <ipv6@ietf.org>; Wed, 23 Oct 2013 05:06:28 -0700 (PDT)
Received: by mail-ie0-f180.google.com with SMTP id e14so1055505iej.25 for <ipv6@ietf.org>; Wed, 23 Oct 2013 05:06:27 -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=//nlixOOFf0jjF0cd6CfX8lLKoTq02/PEidxGAyc3nk=; b=qQip6CIfYZD6ucxvnQON323JFMr0omvohcrMBiYAbRltMFEdIwxZ7tkPWxLuInA7U0 cxJgZ9qEM2ExHhbJZ6E3MCBk0Olw6P1Rjp5sydNf3fs4cmxV3BlX65Pk16xBniHigoXR qonyKXxW/jm/xjyW8ylsuoRhlUcQR8HR94AJmnMK4Et7hbt7BSqtaZ24tS4Pep37ULQp mv/XOaK8mrX6o7I9JW+QVaNOWKBrNjyVq0Klgrj/YVEgfl7Hw7D3moR2IpP9cKfSTXxH dqjz2ISm53c9hoyZk3OMZofJWh+uXvZdida6TcX0gNT0y2Cn2bQxub7lhOJybtlwq52P BP9g==
X-Received: by 10.50.6.99 with SMTP id z3mr621008igz.27.1382529987799; Wed, 23 Oct 2013 05:06:27 -0700 (PDT)
Received: from [192.168.1.69] (dsl-173-206-11-102.tor.primus.ca. [173.206.11.102]) by mx.google.com with ESMTPSA id i3sm7113718igh.0.2013.10.23.05.06.26 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 23 Oct 2013 05:06:27 -0700 (PDT)
Message-ID: <5267BBC0.2020904@gmail.com>
Date: Wed, 23 Oct 2013 08:06:24 -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.0.1
MIME-Version: 1.0
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
Subject: Re: Need for an overview [was ND Option for NMS Discovery-//FW: New Version Notification for draft-liu-6man-nd-nms-discovery-00.txt]
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC189@nkgeml506-mbx.china.huawei.com>	<alpine.DEB.2.02.1310221010170.8663@uplift.swm.pp.se>	<8AE0F17B87264D4CAC7DE0AA6C406F453D7CC43D@nkgeml506-mbx.china.huawei.com>	<alpine.DEB.2.02.1310221102190.8663@uplift.swm.pp.se>	<5266E462.9050901@gmail.com>, <CAC8QAcexEdFJmVdNeqL10HiFmbcHU9xr5qLcU58Ud-sb3njC0g@mail.gmail.com> <107C239B-C80A-41EF-B6AF-765D3E3746E9@huawei.com>
In-Reply-To: <107C239B-C80A-41EF-B6AF-765D3E3746E9@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 23 Oct 2013 12:06:39 -0000

In fact, it addresses the bootstrapping problem first identified in 
draft-tsou-network-configuration-problem-statement and then in the 
ill-fated draft-ietf-opsawg-automated-network-configuration. Round and 
round we go!

Tom Taylor

On 22/10/2013 10:37 PM, Tina TSOU wrote:
> Dear all,
> IMHO, it is related to http://datatracker.ietf.org/doc/draft-schoenw-opsawg-nm-dhc<http://datatracker.ietf.org/doc/draft-schoenw-opsawg-nm-dhc/>/
> What do u think about this?
>
> Thank you,
> Tina
>
...

From brian@innovationslab.net  Wed Oct 23 05:43:53 2013
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7607011E821C for <ipv6@ietfa.amsl.com>; Wed, 23 Oct 2013 05:43:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oW9ZMpHRe3GL for <ipv6@ietfa.amsl.com>; Wed, 23 Oct 2013 05:43:48 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 24CBE11E81A1 for <ipv6@ietf.org>; Wed, 23 Oct 2013 05:43:47 -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 D7467880A4 for <ipv6@ietf.org>; Wed, 23 Oct 2013 05:43:46 -0700 (PDT)
Received: from 10252520.rudm1.ra.johnshopkins.edu (addr16212925014.ippl.jhmi.edu [162.129.250.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 982B0130003 for <ipv6@ietf.org>; Wed, 23 Oct 2013 05:43:46 -0700 (PDT)
Message-ID: <5267C47B.9070605@innovationslab.net>
Date: Wed, 23 Oct 2013 08:43:39 -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.0.1
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: Need for an overview [was ND Option for NMS Discovery-//FW: New Version Notification for draft-liu-6man-nd-nms-discovery-00.txt]
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC189@nkgeml506-mbx.china.huawei.com>	<alpine.DEB.2.02.1310221010170.8663@uplift.swm.pp.se>	<8AE0F17B87264D4CAC7DE0AA6C406F453D7CC43D@nkgeml506-mbx.china.huawei.com>	<alpine.DEB.2.02.1310221102190.8663@uplift.swm.pp.se> <5266E462.9050901@gmail.com>
In-Reply-To: <5266E462.9050901@gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="4bRo34oKcGHRVC2M6rCXgsW27BXAtcmTT"
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 23 Oct 2013 12:43:53 -0000

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

Hi Brian,
     The re-chartering effort for 6man is really focused on making the
WG flexible enough to address these types of issues as they come up.
Given that flexibility, other ADs wanted to avoid having specific work
items listed in the *charter*.  Current work items can be easily
identified in the milestones.

      Given the above approach, I would suggest that convincing the WG
to adopt a draft focused on defining that relationship is the first
step.  If the WG adopts it, I would have no problems working with the
chairs to add it to the milestones.

Regards,
Brian

On 10/22/13 4:47 PM, Brian E Carpenter wrote:
> As I said when commenting on the draft charter recently:
>=20
> I think there's a missing goal, something like
>=20
>  - Define relationship and boundary between DHCPv6-based and RA/ND-base=
d
>    host configuration mechanisms. (This is partly an operational topic,=
 but
>    it lies behind a whole bunch of discussions in various WGs).
>=20
> Unless we get this settled as a general matter, the discussion below wi=
ll
> continue to occur every time an RA/ND extension or a routing-related
> DHCPv6 option is proposed.
>=20
> Regards
>    Brian
>=20
> On 22/10/2013 22:08, Mikael Abrahamsson wrote:
>> On Tue, 22 Oct 2013, Liubing (Leo) wrote:
>>
>>> [Bing] I'm afraid I can't agree, some scenarios might not involve
>>> DHCP, e.g. in the core networks, but ND is always on in IPv6. If the
>>> neighbors already knew something, it is quite convenient to propagate=

>>> the information through ND.
>>
>> Why stop here then, there are a lot of other things we could put into =
ND
>> that would also be convenient?
>>
>>> May I ask the specific reasons that you prefer DHCPv6 over ND?
>>
>> Because before a router knows anything, it's a host, not a router.
>> DHCPv6 is a "host" protocol. It was designed to do these things. There=

>> is no reason a router can't use DHCP to aquire knowledge, it's done
>> using for instance DHCPv6-PD. Doesn't matter if it's a core router or =
not.
>>
>> DHCP is used when someone wants to know something, in ND/RA things are=

>> announced all the time, periodically. I don't think putting "everythin=
g"
>> there is a good engineering solution. For better or for worse, we have=

>> the separation between ND/RA and DHCP for different things, and I thin=
k
>> it should be continued.
>>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20


--4bRo34oKcGHRVC2M6rCXgsW27BXAtcmTT
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

iQEcBAEBCgAGBQJSZ8SBAAoJEBOZRqCi7goqAW0IAILr1fGKfUTmDesWH/UPAarL
HFdO1/hdP19nJH0iRxZJyQnSpWRaTiBmqpzGjqiBai75p5KkB8PY9FOHy4HbxeSm
/UkfvNDFYj4VqW+EHjm6VLmowyvrejwjXqs7nR6c6Ipn88SFxDno6opUnUcsDkKz
8ib5xFHnmjuW+ePMxXYNJS3AFCelAF0Fm3QtUhRQQrOUJZrPl1vHZLUHmuB+e1y1
A2kwuZaw/uyplJs7LjQ5+6XhmEcYM3NtgK2IRwNjx/L2dl0rs46CEPecUtS+gS7I
T1EeKhUsN1X+znHET1Ck1IG7JVhOh6OjDU7LxQTMxwfjjJdK8KbFHn85+R3GKgk=
=SYW/
-----END PGP SIGNATURE-----

--4bRo34oKcGHRVC2M6rCXgsW27BXAtcmTT--

From bjones@vt.edu  Wed Oct 23 06:16:45 2013
Return-Path: <bjones@vt.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F2D611E837D for <ipv6@ietfa.amsl.com>; Wed, 23 Oct 2013 06:16:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J5UP2x4pgavu for <ipv6@ietfa.amsl.com>; Wed, 23 Oct 2013 06:16:40 -0700 (PDT)
Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213]) by ietfa.amsl.com (Postfix) with ESMTP id 4375D11E8257 for <ipv6@ietf.org>; Wed, 23 Oct 2013 06:16:40 -0700 (PDT)
Received: from mr1.cc.vt.edu (mr1.cc.vt.edu [198.82.141.12]) by lennier.cc.vt.edu (8.13.8/8.13.8) with ESMTP id r9NDG8Qv031446 for <ipv6@ietf.org>; Wed, 23 Oct 2013 09:16:08 -0400
Received: from mail-qe0-f42.google.com (mail-qe0-f42.google.com [209.85.128.42]) by mr1.cc.vt.edu (8.14.4/8.14.4) with ESMTP id r9NDG8ra029571 for <ipv6@ietf.org>; Wed, 23 Oct 2013 09:16:08 -0400
Received: by mail-qe0-f42.google.com with SMTP id gc15so442971qeb.15 for <ipv6@ietf.org>; Wed, 23 Oct 2013 06:16:08 -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:from:date :message-id:subject:to:cc:content-type; bh=uR6Azx1HPy0IpzY2INDY6OkxWY31+M6bSka1RiZxEbU=; b=iUqGTV7yfFA2iMKe5VZBNoGY7ueXBgUlvCh6++TDEgS41X/xw0KneYlGZRuMSJUGtw 7lRB9cstlL5KA6sTNQknuf9VkQFNB9BbRokau1n2isK69oxqwOTkulCqTdtFjsuIW4Ha efnVNRqKC7/gjQDQG4kaD5vqiESGKQLfh7LhgofZLrH7ErH1xFQtWsAitN2/a+sZcHc6 l9XDY7tN7KtKH1l1YTiCkf8IkBcyPso50gc2jSqZGdcKSbln3vCm9C0t+6QW9YYi+CUn xgQOhx9GdC3okYjH1DlRQXwOnnroxwgfKrR9BeqWaqFhuoMREsaZTkZGzk3j2C50R9HF 3iQQ==
X-Gm-Message-State: ALoCoQmyyIH9I9wjMl3LFLuuPEq7M458WLuwEI2+t5D6pu9s1rGFMtaHmMReuJ6QmAMzsk7kCU7rMj7PuxbkcDTn6RLz1Oi1P3cmwDPoEbpvgNsrBujN+tbcec4XrkwWTg3NADjtWpkT
X-Received: by 10.224.172.132 with SMTP id l4mr3855117qaz.22.1382534168286; Wed, 23 Oct 2013 06:16:08 -0700 (PDT)
X-Received: by 10.224.172.132 with SMTP id l4mr3855100qaz.22.1382534168187; Wed, 23 Oct 2013 06:16:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.96.214.66 with HTTP; Wed, 23 Oct 2013 06:15:48 -0700 (PDT)
In-Reply-To: <CAKD1Yr24yJzGruR5N2Ja4XPTCqD6K=4CmGuHztVmHcynG5AUiQ@mail.gmail.com>
References: <20131021044241.22753.19800.idtracker@ietfa.amsl.com> <8392F9BAC6AD5F47920216A6D7853F7E1D57D48A@BPXM02GP.gisp.nec.co.jp> <CAKD1Yr24yJzGruR5N2Ja4XPTCqD6K=4CmGuHztVmHcynG5AUiQ@mail.gmail.com>
From: Brian Jones <bjones@g.mail.vt.edu>
Date: Wed, 23 Oct 2013 09:15:48 -0400
Message-ID: <CANyqO+FqOjExv5JGGpKghs-CDMBMMSB7VxCpw+kt95bZYbRNHw@mail.gmail.com>
Subject: Re: I-D Action: draft-kitamura-ipv6-zoneid-free-01.txt
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: multipart/alternative; boundary=001a11c253c0fc1ec604e96851c7
Cc: Hiroshi Kitamura <kitamura@da.jp.nec.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "Ata, Shingo \(ata@info.eng.osaka-cu.ac.jp\)" <ata@info.eng.osaka-cu.ac.jp>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 23 Oct 2013 13:16:45 -0000

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

On Wed, Oct 23, 2013 at 12:20 AM, Lorenzo Colitti <lorenzo@google.com>wrote=
:

> On Wed, Oct 23, 2013 at 11:30 AM, Hiroshi Kitamura <kitamura@da.jp.nec.co=
m
> > wrote:
>
>> Please, let us know your comments or interest on this idea.
>>
>
> The reason why scope IDs exist is that the same address might exist on
> more than one interface. The document does not solve this problem.
>
> Example: what if there is a fe80::1 on two different interfaces? Sending =
a
> packet to fe80::1 will cause two NSes to be transmitted, and two ND cache
> entries to be created. What happens then? Do data packets also sent to bo=
th
> neighbours? If so, which one? And if not, why not?
>
> It might help if the document had a clear use case. But there are no real
> examples of where this is a problem. The draft does says that the scope I=
D
> is hard to type, and that cannot be shared, and can change, but it doesn'=
t
> say why the network is using link-local addresses instead of global
> addresses or ULA.
>
> If the justification is "to make it simpler for end users to deal with
> link-local addresses", then why not use names (e.g., via link-local
> multicast DNS)? Exposing end users to IPv6 addresses does not seem like a
> good solution.
>

=E2=80=8BNames would definitely make addresses more recognizable at a glanc=
e and
therefore easier to use... We want to promote IPv6 adoption and IPv6
addresses can be scary looking to end users...
fwiw
=E2=80=8B
 __=E2=80=8B
=E2=80=8Bbej=E2=80=8B


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

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small"><br=
></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Wed=
, Oct 23, 2013 at 12:20 AM, Lorenzo Colitti <span dir=3D"ltr">&lt;<a href=
=3D"mailto:lorenzo@google.com" target=3D"_blank">lorenzo@google.com</a>&gt;=
</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"im">On Wed, O=
ct 23, 2013 at 11:30 AM, Hiroshi Kitamura <span dir=3D"ltr">&lt;<a href=3D"=
mailto:kitamura@da.jp.nec.com" target=3D"_blank">kitamura@da.jp.nec.com</a>=
&gt;</span> wrote:<br>

</div><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div class=3D"i=
m">

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Please, let us know your comments or interes=
t on this idea.<br></blockquote><div><br></div></div><div>The reason why sc=
ope IDs exist is that the same address might exist on more than one interfa=
ce. The document does not solve this problem.</div>



<div><br></div><div>Example: what if there is a fe80::1 on two different in=
terfaces? Sending a packet to fe80::1 will cause two NSes to be transmitted=
, and two ND cache entries to be created. What happens then? Do data packet=
s also sent to both neighbours? If so, which one? And if not, why not?</div=
>



<div><br></div><div>It might help if the document had a clear use case. But=
 there are no real examples of where this is a problem. The draft does says=
 that the scope ID is hard to type, and that cannot be shared, and can chan=
ge, but it doesn&#39;t say why the network is using link-local addresses in=
stead of global addresses or ULA.</div>



<div><br></div><div>If the justification is &quot;to make it simpler for en=
d users to deal with link-local addresses&quot;, then why not use names (e.=
g., via link-local multicast DNS)? Exposing end users to IPv6 addresses doe=
s not seem like a good solution.</div>

</div></div></div></blockquote><div><br><div class=3D"gmail_default" style=
=3D"font-size:small;display:inline">=E2=80=8BNames would definitely make ad=
dresses more recognizable at a glance and therefore easier to use... We wan=
t to promote IPv6 adoption and IPv6 addresses can be scary looking to end u=
sers...<br>

</div><div class=3D"gmail_default" style=3D"font-size:small;display:inline"=
>fwiw<br></div><div class=3D"gmail_default" style=3D"font-size:small;displa=
y:inline">=E2=80=8B</div>=C2=A0__=E2=80=8B<br><div class=3D"gmail_default" =
style=3D"font-size:small">=E2=80=8Bbej=E2=80=8B</div>

<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gma=
il_extra"><div class=3D"gmail_quote">

</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></div>

--001a11c253c0fc1ec604e96851c7--

From lorenzo@google.com  Wed Oct 23 10:13:55 2013
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECB2011E83C3 for <ipv6@ietfa.amsl.com>; Wed, 23 Oct 2013 10:13:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.786
X-Spam-Level: 
X-Spam-Status: No, score=-1.786 tagged_above=-999 required=5 tests=[AWL=-0.124, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1Bo-4S1nqsyn for <ipv6@ietfa.amsl.com>; Wed, 23 Oct 2013 10:13:55 -0700 (PDT)
Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id 44AB811E8176 for <ipv6@ietf.org>; Wed, 23 Oct 2013 10:13:54 -0700 (PDT)
Received: by mail-ie0-f177.google.com with SMTP id e14so1784628iej.8 for <ipv6@ietf.org>; Wed, 23 Oct 2013 10:13:54 -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=Z/EktJoTj9xPnTWOdpbu8FNhVQVSYbSdo7kZph22NZg=; b=lYsy8d4KKtbrnv2A/KkFwFmCt3rTKXUecTzfGzNpTIDKRHKqIjcTGhHHp2IcAOOI0S B2Sc++1uke7zv5Fm2oPCQxeDo2nC1h5J2SADadHY+f1rCP4VEoghxLhB74SgXS3sgt45 in2FirQoufqtJJzXIw2AO2jzEE9HiwV/qN5R+zaxFCwWM/KGRpe2yuVcKk3Qeb9RZURh QHlpFc7iM11oe4FJFrUtccUPiDaz8v5vM9zfgbwihO8E8CGWARv6uZW2+7rcrEgDY1pC QRy+hEWEyznkAfpk8qQ/LlRhCaVWdfOsOplE5U38/RhB4rxqXTITFCJQ6riOrWrGkz44 4ZGg==
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=Z/EktJoTj9xPnTWOdpbu8FNhVQVSYbSdo7kZph22NZg=; b=er8WDIeyZGXBVeJCyV7fQxVW01kHYpCHn/NJpOTKdea45jtvQLpY1fzYwqR+kK/nkD oQ4sf9dy4kweyN6N0byw8b7iDl3QEseJTYEAsIX/IA0S9nWLxsqB3t6NL6v7iGWxqjlm rxK4N7OhXm/ZcW6oXjwb8T8m5SnDqHA/VJRLE/qW0swCRpicNss00+gWb1kQ24MJvL6Y 5CBiXoXFRmizL718BZhT+gdS9UysPlsZOXT9/tUU/ZyNpqdktdH7Lw1/VJsLITi0E1J1 riGzBEx9xFhohHhJUS8JRl2URjcbtsnhRa2yNrDL5ZG74ZQIYGjq/1ozGrnjqCMX6p31 waPA==
X-Gm-Message-State: ALoCoQnZScXC0/jgfav8UNXbJG5uUR7Vk/ANjFMnryV+DHhSXeO9XRf2qZgNH92Ai6/a9tpn5eOtg6QblK9rXQ298Zd+uV5SHRxUNcJW2c5j3JHXVKtFxqPzR76OWUs5G9M6O+8UyBo3w/AN+9vK7c4SI0Iq3J2vcrZOwvKzXhdrePYp3Ws9SH7QUfRBO/8XtqjqzKk0WqrC
X-Received: by 10.50.22.101 with SMTP id c5mr1367710igf.17.1382548434537; Wed, 23 Oct 2013 10:13:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.86.106 with HTTP; Wed, 23 Oct 2013 10:13:34 -0700 (PDT)
In-Reply-To: <5267C47B.9070605@innovationslab.net>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC189@nkgeml506-mbx.china.huawei.com> <alpine.DEB.2.02.1310221010170.8663@uplift.swm.pp.se> <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC43D@nkgeml506-mbx.china.huawei.com> <alpine.DEB.2.02.1310221102190.8663@uplift.swm.pp.se> <5266E462.9050901@gmail.com> <5267C47B.9070605@innovationslab.net>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 24 Oct 2013 02:13:34 +0900
Message-ID: <CAKD1Yr3wWfzy2T6nLwJQPKX0MSbL+EZ6Q2j0qWQmbH5jgOcKyA@mail.gmail.com>
Subject: Re: Need for an overview [was ND Option for NMS Discovery-//FW: New Version Notification for draft-liu-6man-nd-nms-discovery-00.txt]
To: Brian Haberman <brian@innovationslab.net>
Content-Type: multipart/alternative; boundary=047d7b10c9cb5370c404e96ba4b4
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 23 Oct 2013 17:13:56 -0000

--047d7b10c9cb5370c404e96ba4b4
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Oct 23, 2013 at 9:43 PM, Brian Haberman <brian@innovationslab.net>wrote:

>       Given the above approach, I would suggest that convincing the WG
> to adopt a draft focused on defining that relationship is the first
> step.  If the WG adopts it, I would have no problems working with the
> chairs to add it to the milestones.
>

I agree that we're about due to attempt to have this conversation again.
Who knows, now that we have more operational and deployment experience than
we did last time, the outcome might be different.

Rather than have an argument based on single use cases, what might be
useful is to start with a document that lists the basic technical
properties / semantics of the mechanisms themselves. For example:

RA option: sent by the router; requires no server; hard to relay / apply
policy; easy to update at any time, even if the original router has
crashed; scales with router CPU; shares fate with routing; supports merging
multiple sources of information.

Stateless DHCPv6 option: sent by a server; requires a server; easy to relay
/ apply policy; scales with server CPU (which can be better or worse than
router CPU depending on how many thousands/millions of clients you send to
a single server); very hard to update from network side; doesn't share fate
with routing; doesn't support merging multiple sources of information.

"We do it this way in IPv4" or "the market is asking for it" (which are
mostly, though perhaps not entirely, the same argument) would explicitly
not be a part of this document because they're not technical properties of
the protocols.

The hope would be that we don't fundamentally disagree on the properties of
the two provisioning protocols, only on which characteristics are more
important in which deployment scenarios. If that's true, and we were able
to agree on this document describing the properties, then we might later be
able to move towards deciding what kinds of options go into which protocol.

--047d7b10c9cb5370c404e96ba4b4
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Wed, Oct 23, 2013 at 9:43 PM, Brian Haberman <span dir=
=3D"ltr">&lt;<a href=3D"mailto:brian@innovationslab.net" target=3D"_blank">=
brian@innovationslab.net</a>&gt;</span> wrote:<br><div class=3D"gmail_extra=
"><div class=3D"gmail_quote">

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">=A0 =A0 =A0 Given the above approach, I woul=
d suggest that convincing the WG<br>
to adopt a draft focused on defining that relationship is the first<br>
step. =A0If the WG adopts it, I would have no problems working with the<br>
chairs to add it to the milestones.<br></blockquote><div><br></div><div>I a=
gree that we&#39;re about due to attempt to have this conversation again. W=
ho knows, now that we have more operational and deployment experience than =
we did last time, the outcome might be different.</div>

<div><br></div><div>Rather than have an argument based on single use cases,=
 what might be useful is to start with a document that lists the basic tech=
nical properties / semantics of the mechanisms themselves. For example:</di=
v>

<div><br></div><div>RA option: sent by the router; requires no server; hard=
 to relay / apply policy; easy to update at any time, even if the original =
router has crashed; scales with router CPU; shares fate with routing; suppo=
rts merging multiple sources of information.</div>

<div><br></div><div>Stateless DHCPv6 option: sent by a server; requires a s=
erver; easy to relay / apply policy; scales with server CPU (which can be b=
etter or worse than router CPU depending on how many thousands/millions of =
clients you send to a single server); very hard to update from network side=
; doesn&#39;t share fate with routing; doesn&#39;t support merging multiple=
 sources of information.</div>

<div><br></div><div>&quot;We do it this way in IPv4&quot; or &quot;the mark=
et is asking for it&quot; (which are mostly, though perhaps not entirely, t=
he same argument) would explicitly not be a part of this document because t=
hey&#39;re not technical properties of the protocols.</div>

<div><br></div><div>The hope would be that we don&#39;t fundamentally disag=
ree on the properties of the two provisioning protocols, only on which char=
acteristics are more important in which deployment scenarios. If that&#39;s=
 true, and we were able to agree on this document describing the properties=
, then we might later be able to move towards deciding what kinds of option=
s go into which protocol.</div>

</div></div></div>

--047d7b10c9cb5370c404e96ba4b4--

From brian.e.carpenter@gmail.com  Wed Oct 23 12:15:49 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93B9911E8210 for <ipv6@ietfa.amsl.com>; Wed, 23 Oct 2013 12:15:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.38
X-Spam-Level: 
X-Spam-Status: No, score=-102.38 tagged_above=-999 required=5 tests=[AWL=-0.096, BAYES_00=-2.599, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18wAnfvwlYLN for <ipv6@ietfa.amsl.com>; Wed, 23 Oct 2013 12:15:49 -0700 (PDT)
Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id E0BD211E8203 for <ipv6@ietf.org>; Wed, 23 Oct 2013 12:15:48 -0700 (PDT)
Received: by mail-pa0-f44.google.com with SMTP id fb1so1380178pad.31 for <ipv6@ietf.org>; Wed, 23 Oct 2013 12:15:48 -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=2F85fwHW9PWzLOz3hGPOEiQPUKcMkuv3zUsia7TMPx4=; b=BSuDUXnm4zuaehbteV3M0bh/mj+/kWU/O0ax9EFQeEtMTPPita1mDDPpEh6+Hfy3GH 1tH5waO4qDqoeoL64FdUAz3d0yc6oCpb5Dt/PasHOOyz9GBy4zt42nGt9FUsK4iQs14v QEe4ZUrUg1BqjiLt6UoP2Ly3AkPVDNeN6dnLA40rrd9XmZSQjLHOu/mOAPm5o3eS0HqG ixoAsagkCvPYwi1FqmKTPJMWo4SJjNMlr1y7dcD7c7S2wOG320AsGYDG+tSd7lwZx9Ha vnBoStnaf2eXCl0nmmF21Hy3yT1J2hwMmy7aL8wRKkWB2jE4fWZI1m/1CVQJ2sU8MQrH c8Jw==
X-Received: by 10.66.119.78 with SMTP id ks14mr4827534pab.140.1382555748628; Wed, 23 Oct 2013 12:15:48 -0700 (PDT)
Received: from [192.168.178.20] (186.201.69.111.dynamic.snap.net.nz. [111.69.201.186]) by mx.google.com with ESMTPSA id hu10sm6259137pbc.11.2013.10.23.12.15.46 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 23 Oct 2013 12:15:48 -0700 (PDT)
Message-ID: <52682068.7060409@gmail.com>
Date: Thu, 24 Oct 2013 08:15: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: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: Need for an overview [was ND Option for NMS Discovery-//FW: New Version Notification for draft-liu-6man-nd-nms-discovery-00.txt]
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC189@nkgeml506-mbx.china.huawei.com>	<alpine.DEB.2.02.1310221010170.8663@uplift.swm.pp.se>	<8AE0F17B87264D4CAC7DE0AA6C406F453D7CC43D@nkgeml506-mbx.china.huawei.com>	<alpine.DEB.2.02.1310221102190.8663@uplift.swm.pp.se>	<5266E462.9050901@gmail.com> <5267C47B.9070605@innovationslab.net> <CAKD1Yr3wWfzy2T6nLwJQPKX0MSbL+EZ6Q2j0qWQmbH5jgOcKyA@mail.gmail.com>
In-Reply-To: <CAKD1Yr3wWfzy2T6nLwJQPKX0MSbL+EZ6Q2j0qWQmbH5jgOcKyA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Brian Haberman <brian@innovationslab.net>, IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 23 Oct 2013 19:15:49 -0000

Ack. By definition it's too late to do anything before Vancouver,
but I agree that a draft is needed. It's on my list...

Regards
   Brian

On 24/10/2013 06:13, Lorenzo Colitti wrote:
> On Wed, Oct 23, 2013 at 9:43 PM, Brian Haberman <brian@innovationslab.net>wrote:
> 
>>       Given the above approach, I would suggest that convincing the WG
>> to adopt a draft focused on defining that relationship is the first
>> step.  If the WG adopts it, I would have no problems working with the
>> chairs to add it to the milestones.
>>
> 
> I agree that we're about due to attempt to have this conversation again.
> Who knows, now that we have more operational and deployment experience than
> we did last time, the outcome might be different.
> 
> Rather than have an argument based on single use cases, what might be
> useful is to start with a document that lists the basic technical
> properties / semantics of the mechanisms themselves. For example:
> 
> RA option: sent by the router; requires no server; hard to relay / apply
> policy; easy to update at any time, even if the original router has
> crashed; scales with router CPU; shares fate with routing; supports merging
> multiple sources of information.
> 
> Stateless DHCPv6 option: sent by a server; requires a server; easy to relay
> / apply policy; scales with server CPU (which can be better or worse than
> router CPU depending on how many thousands/millions of clients you send to
> a single server); very hard to update from network side; doesn't share fate
> with routing; doesn't support merging multiple sources of information.
> 
> "We do it this way in IPv4" or "the market is asking for it" (which are
> mostly, though perhaps not entirely, the same argument) would explicitly
> not be a part of this document because they're not technical properties of
> the protocols.
> 
> The hope would be that we don't fundamentally disagree on the properties of
> the two provisioning protocols, only on which characteristics are more
> important in which deployment scenarios. If that's true, and we were able
> to agree on this document describing the properties, then we might later be
> able to move towards deciding what kinds of options go into which protocol.
> 
> 
> 
> ------------------------------------------------------------------------
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

From rdroms.ietf@gmail.com  Wed Oct 23 12:56:51 2013
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 499C611E820C; Wed, 23 Oct 2013 12:56:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.45
X-Spam-Level: 
X-Spam-Status: No, score=-102.45 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pidO2NNw1obz; Wed, 23 Oct 2013 12:56:50 -0700 (PDT)
Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id 901D711E81DF; Wed, 23 Oct 2013 12:56:50 -0700 (PDT)
Received: by mail-qc0-f182.google.com with SMTP id n7so793129qcx.13 for <multiple recipients>; Wed, 23 Oct 2013 12:56:50 -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 :content-transfer-encoding:message-id:references:to; bh=UmW/mIxx9X6QYWSAXE22eUDeKdx7DexynDZnExTzkqI=; b=NCc8dMC6PYKGoJBTO8/G32t4FV4W01v59iXwVGwJtIktdNTC4IgtG2hU6jtMUzie3q CGbsx/3BOnyx/yfbGTqTff/7lxP68ZQy0NQD0C0VDcvbO4UEdaD22qjLxYOjjZ2XwCbm LPbLxtwMuD8kToCmG+Y/mfXOPdBeJg5eup9z/ZqjjU2yl9ZEsjOd32fpJRugQOf9Oj+a zfRy7zgXZ/MgoSD3dW6shszMAuxf+Pm6PKjmc84KdrabTWWBRzYDb+JEtJA/R041B9hI v507avft212l+SAG3l8FQsld3l4edCw0OnZJ6hbG0QCRLUZQivu+g1/gw6ZDKp0ZAuDJ E1RQ==
X-Received: by 10.224.54.66 with SMTP id p2mr6292079qag.87.1382558209989; Wed, 23 Oct 2013 12:56:49 -0700 (PDT)
Received: from ?IPv6:2001:420:2c52:1316:143:7974:fe17:7855? ([2001:420:2c52:1316:143:7974:fe17:7855]) by mx.google.com with ESMTPSA id x1sm64785236qai.6.2013.10.23.12.56.47 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 23 Oct 2013 12:56:48 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re: [Roll] [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope value of 3 - subnet-local)
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <CAJE_bqdL3v4XK+dJPx1ZVFoRS+yjFDZEwVZ64fhYW6QUWVS6JA@mail.gmail.com>
Date: Wed, 23 Oct 2013 15:56:46 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <52FECA00-C316-4693-A821-7EA6510AC0F8@gmail.com>
References: <3599.1381852752@sandelman.ca> <CE82BA46.24343%d.sturek@att.net> <CABOxzu2nLuny5uySEEdb6ji9ucE6xqGZ6DLe-mc6KUqVszNfFg@mail.gmail.com> <525DC6C9.2010808@gridmerge.com> <CABOxzu2apwBRpU1h4mKJwpO+U+Y9Q_q-h5AhZ+hGzAdjdPdmUQ@mail.gmail.com> <525E5064.4050109@gridmerge.com> <CABOxzu0L-EY0iDGpAJ+ER15CPL-3v8F77ewn-G=gZYODixevZg@mail.gmail.com> <3CC8783F-F4DA-47B9-A051-DBBA6EF00C19@gmail.com> <CAJE_bqdL3v4XK+dJPx1ZVFoRS+yjFDZEwVZ64fhYW6QUWVS6JA@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.1510)
Cc: Routing Over Low power and Lossy networks <roll@ietf.org>, 6man@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 23 Oct 2013 19:56:51 -0000

On Oct 21, 2013, at 3:00 PM 10/21/13, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89=
 <jinmei@wide.ad.jp> wrote:

> At Thu, 17 Oct 2013 09:10:50 -0700,
> Ralph Droms <rdroms.ietf@gmail.com> wrote:
>=20
>> Noting this conflict, I propose adding a bit of text to
>> draft-ietf-6man-multicast-scopes to update RFC 4007 for consistency
>> with RFC 4291:
>=20
> I think making these consistent is a good idea.
>=20
>> OLD:
>>=20
>>   o  The boundaries of zones of a scope other than interface-local,
>>      link-local, and global must be defined and configured by network
>>      administrators.
>>=20
>> NEW:
>>=20
>>   o  Admin-Local scope is the smallest scope that must be
>>      administratively configured, i.e., not automatically derived
>>      from physical connectivity or other, non-multicast-related
>>      configuration.
>=20
> I'm okay with the proposed text, but on a closer look I've noticed
> a couple of subtle points you may want to consider:
>=20
> - I see a slight difference between the OLD (RFC 4007) and NEW (RFC
>  4291) even after fixing the obvious inconsistency, in that the NEW
>  version does not necessarily say how the scopes larger than
>  admin-local scope is configured; technically it only states
>  interface-local and link-local (and "Realm-Local" if assigned)
>  would not be automatically configured.  In fact, the global scope
>  shouldn't be "administratively" configured, which is crystal clear
>  from the OLD version, but not necessarily in the NEW version.
>=20
> - should we worry about possible future updates to the addressing
>  architecture and scope architecture documents?  If we keep these
>  documents separately and have a copy of the text in both, we may need
>  to update both copies when we need to make a change on this point as
>  more "currently reserved" scopes are assigned.

Both good points.  As long as we have to make an update to RFC 4007, =
let's make sure the update is correct.

>=20
> These are probably too minor and maybe we can simply ignore the
> subtlety.  If that's our consensus I'm okay with that.  But if we want
> to address these points, maybe:
>=20
> OLD:
>=20
>   o  The boundaries of zones of a scope other than interface-local,
>      link-local, and global must be defined and configured by network
>      administrators.
>=20
> NEW:
>=20
>   o  The boundaries of zones of an interface-local, link-local, or
>      global scope automatically derived from physical connectivity.
>      For zones of other types of scopes, the IPv6 addressing
>      architecture specification defines how their boundaries must be
>      determined, whether automatically derived or administratively
>      configured.

Perhaps we want to go a step farther and take the zone boundary text out =
of RFC 4007 altogether?

OLD:

  o  The boundaries of zones of a scope other than interface-local,
     link-local, and global must be defined and configured by network
     administrators

NEW:

  o  The boundaries of zones of a scope are defined by the IPv6
     addressing architecture.

- Ralph


>=20
> --
> JINMEI, Tatuya


From jinmei.tatuya@gmail.com  Wed Oct 23 14:21:18 2013
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6301A11E8241; Wed, 23 Oct 2013 14:21:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.222
X-Spam-Level: *
X-Spam-Status: No, score=1.222 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zQL4SoUvRKmo; Wed, 23 Oct 2013 14:21:18 -0700 (PDT)
Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 9312711E821A; Wed, 23 Oct 2013 14:21:17 -0700 (PDT)
Received: by mail-wg0-f47.google.com with SMTP id c11so1459355wgh.14 for <multiple recipients>; Wed, 23 Oct 2013 14:21:16 -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=QkZvQBlQAyOoTKz/4ac6WYSVeH/tIOr56sH8bz9Wpf8=; b=f4TsX/CVAuMqRVMSGDSp2YJ68hbkzCtUqbCNAmw7aUnPIaZtHMJvqUkmpwdL5RLAcI aj0iaOFQyVtOPBdk6NUvWrUJuD2MJNKTbyP4i4QeM6Toc++VV2eIHmO2Dfy8jmzn+6Vq mJkelwVnwtUtFLBPE1WiQDQnPDy21td5vQbH3MuJ2iW5FXCC0njL/sYFD3LEBQGpxu9m KO9HII5U376vNPdc6uSCQJv/HGzBZRW6ch8dayOStskc4kr3WhkgwOssQBN3hCgKKPNy Jup63nPwVbs0q2/88gm+f39ATb6ZW+aGggPLqabL2Wl6x2enRmRoheoGaXGBeP0tT2GL L00A==
MIME-Version: 1.0
X-Received: by 10.194.175.66 with SMTP id by2mr3319478wjc.59.1382563276700; Wed, 23 Oct 2013 14:21:16 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.120.167 with HTTP; Wed, 23 Oct 2013 14:21:16 -0700 (PDT)
In-Reply-To: <52FECA00-C316-4693-A821-7EA6510AC0F8@gmail.com>
References: <3599.1381852752@sandelman.ca> <CE82BA46.24343%d.sturek@att.net> <CABOxzu2nLuny5uySEEdb6ji9ucE6xqGZ6DLe-mc6KUqVszNfFg@mail.gmail.com> <525DC6C9.2010808@gridmerge.com> <CABOxzu2apwBRpU1h4mKJwpO+U+Y9Q_q-h5AhZ+hGzAdjdPdmUQ@mail.gmail.com> <525E5064.4050109@gridmerge.com> <CABOxzu0L-EY0iDGpAJ+ER15CPL-3v8F77ewn-G=gZYODixevZg@mail.gmail.com> <3CC8783F-F4DA-47B9-A051-DBBA6EF00C19@gmail.com> <CAJE_bqdL3v4XK+dJPx1ZVFoRS+yjFDZEwVZ64fhYW6QUWVS6JA@mail.gmail.com> <52FECA00-C316-4693-A821-7EA6510AC0F8@gmail.com>
Date: Wed, 23 Oct 2013 14:21:16 -0700
X-Google-Sender-Auth: 9r766Kso1DOa8mTJr0OgNTJrxjI
Message-ID: <CAJE_bqcvQSiNTbbOvUEBvLC1uK5kAFfF04ZbQ=DFpwKb+ynATw@mail.gmail.com>
Subject: Re: draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re: [Roll] [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope value of 3 - subnet-local)
From: =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>
To: Ralph Droms <rdroms.ietf@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Routing Over Low power and Lossy networks <roll@ietf.org>, "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 23 Oct 2013 21:21:18 -0000

At Wed, 23 Oct 2013 15:56:46 -0400,
Ralph Droms <rdroms.ietf@gmail.com> wrote:

> Perhaps we want to go a step farther and take the zone boundary text
> out of RFC 4007 altogether?

Basically works for me.

> OLD:
>
>   o  The boundaries of zones of a scope other than interface-local,
>      link-local, and global must be defined and configured by network
>      administrators
>
> NEW:
>
>   o  The boundaries of zones of a scope are defined by the IPv6
>      addressing architecture.

With a reference (it's currently RFC 4291)?

I'd also note that not all points described in the RFC 4007 text are
described in RFC 4291 (at least not very clearly).  So, not just
remove the text from RFC 4007, I'd like to unify it in the address
architecture, e.g. update the following part of RFC 4291:

         Admin-Local scope is the smallest scope that must be
         administratively configured, i.e., not automatically derived
         from physical connectivity or other, non-multicast-related
         configuration.

as follows:

         Admin-Local scope is the smallest scope that must be
         administratively configured, i.e., not automatically derived
         from physical connectivity or other, non-multicast-related
         configuration.  For all non-reserved scopes except the global
         scope, the zone boundaries must also be administratively
         configured.

--
JINMEI, Tatuya

From kerlyn2001@gmail.com  Wed Oct 23 14:38:19 2013
Return-Path: <kerlyn2001@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C870C11E825B; Wed, 23 Oct 2013 14:38:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.101
X-Spam-Level: 
X-Spam-Status: No, score=-1.101 tagged_above=-999 required=5 tests=[AWL=-0.876, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s7qAPlLeCY4O; Wed, 23 Oct 2013 14:38:15 -0700 (PDT)
Received: from mail-ob0-x234.google.com (mail-ob0-x234.google.com [IPv6:2607:f8b0:4003:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 3F10C11E8181; Wed, 23 Oct 2013 14:38:10 -0700 (PDT)
Received: by mail-ob0-f180.google.com with SMTP id wo20so1484406obc.11 for <multiple recipients>; Wed, 23 Oct 2013 14:38:07 -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=WFKYjAmQ4nr9G1lcaLcyAVnAUYOqkzPKrb+YD0sFrtE=; b=wGBBtan1X6n2EkjZ5j+5oOJkcDUeIbHKsj4egRY2Sok5dfhjyGPbkevrhCv+uthdyJ WoEslCwLQXBcX7BMWsaHfPaaMnnNK6vB2rsx172TMQXAA3xmYeF8ApJzwkbcYwZV92qY /s594eh+wsBOdJgTPq2QDWzavmSeBWGEjxc5TY6LB2mYNy4pt37X8koaP/vobekRw8f9 k3dPgOQgpC2qh1fLBikJufvlTwy7B6prc02CrEnFzKVIDY6bPeTFTZzsUgVWvah5GRHo DVSb2rz0DGsR/6Mmwl07Dlx2Tw/LbiAwaqz+etXUlEsT/44xapSsB31Ys9sZo2pvOX1m Mc5g==
MIME-Version: 1.0
X-Received: by 10.182.246.74 with SMTP id xu10mr3755288obc.23.1382564287673; Wed, 23 Oct 2013 14:38:07 -0700 (PDT)
Sender: kerlyn2001@gmail.com
Received: by 10.60.73.6 with HTTP; Wed, 23 Oct 2013 14:38:07 -0700 (PDT)
In-Reply-To: <CAJE_bqcvQSiNTbbOvUEBvLC1uK5kAFfF04ZbQ=DFpwKb+ynATw@mail.gmail.com>
References: <3599.1381852752@sandelman.ca> <CE82BA46.24343%d.sturek@att.net> <CABOxzu2nLuny5uySEEdb6ji9ucE6xqGZ6DLe-mc6KUqVszNfFg@mail.gmail.com> <525DC6C9.2010808@gridmerge.com> <CABOxzu2apwBRpU1h4mKJwpO+U+Y9Q_q-h5AhZ+hGzAdjdPdmUQ@mail.gmail.com> <525E5064.4050109@gridmerge.com> <CABOxzu0L-EY0iDGpAJ+ER15CPL-3v8F77ewn-G=gZYODixevZg@mail.gmail.com> <3CC8783F-F4DA-47B9-A051-DBBA6EF00C19@gmail.com> <CAJE_bqdL3v4XK+dJPx1ZVFoRS+yjFDZEwVZ64fhYW6QUWVS6JA@mail.gmail.com> <52FECA00-C316-4693-A821-7EA6510AC0F8@gmail.com> <CAJE_bqcvQSiNTbbOvUEBvLC1uK5kAFfF04ZbQ=DFpwKb+ynATw@mail.gmail.com>
Date: Wed, 23 Oct 2013 17:38:07 -0400
X-Google-Sender-Auth: 49IQKZyZDA0hkIuuNaDVCXN-aH8
Message-ID: <CABOxzu20qONjQ71EWyob2Th+PJGpFz_Cw8jhvbmiEtojd+ihHg@mail.gmail.com>
Subject: Re: draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re: [Roll] [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope value of 3 - subnet-local)
From: Kerry Lynn <kerlyn@ieee.org>
To: =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>
Content-Type: multipart/alternative; boundary=001a11c2e6083efebb04e96f5567
Cc: Routing Over Low power and Lossy networks <roll@ietf.org>, "6man@ietf.org" <6man@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 23 Oct 2013 21:38:21 -0000

--001a11c2e6083efebb04e96f5567
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit

On Wed, Oct 23, 2013 at 5:21 PM, $B?@L@C#:H(B <jinmei@wide.ad.jp> wrote:

> At Wed, 23 Oct 2013 15:56:46 -0400,
> Ralph Droms <rdroms.ietf@gmail.com> wrote:
>
> > Perhaps we want to go a step farther and take the zone boundary text
> > out of RFC 4007 altogether?
>
> Basically works for me.
>
> > OLD:
> >
> >   o  The boundaries of zones of a scope other than interface-local,
> >      link-local, and global must be defined and configured by network
> >      administrators
> >
> > NEW:
> >
> >   o  The boundaries of zones of a scope are defined by the IPv6
> >      addressing architecture.
>
> With a reference (it's currently RFC 4291)?
>
> I'd also note that not all points described in the RFC 4007 text are
> described in RFC 4291 (at least not very clearly).  So, not just
> remove the text from RFC 4007, I'd like to unify it in the address
> architecture, e.g. update the following part of RFC 4291:
>
>          Admin-Local scope is the smallest scope that must be
>          administratively configured, i.e., not automatically derived
>          from physical connectivity or other, non-multicast-related
>          configuration.
>
> as follows:
>
>          Admin-Local scope is the smallest scope that must be
>          administratively configured, i.e., not automatically derived
>          from physical connectivity or other, non-multicast-related
>          configuration.  For all non-reserved scopes except the global
>          scope, the zone boundaries must also be administratively
>          configured.
>
> I think this statement is self-contradictory.  When automatic
configuration is
discussed, it is in relation to zone boundaries.  Here's an attempt to
explain
this without negations:

    Interface-Local, Link-Local, and Realm-Local scope boundaries are
automatically
    derived from physical connectivity or other, non-multicast related
configuration.
    Global scope has no boundary.  The boundaries of all other non-reserved
scopes
    are administratively configured.

BTW, just my opinion, but "Realm-Local" might be more meaningfully named
"Multilink-Local"

-K-

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

--001a11c2e6083efebb04e96f5567
Content-Type: text/html; charset=ISO-2022-JP
Content-Transfer-Encoding: base64

PGRpdiBkaXI9Imx0ciI+T24gV2VkLCBPY3QgMjMsIDIwMTMgYXQgNToyMSBQTSwgGyRCP0BMQEMj
OkgbKEIgPHNwYW4gZGlyPSJsdHIiPiZsdDs8YSBocmVmPSJtYWlsdG86amlubWVpQHdpZGUuYWQu
anAiIHRhcmdldD0iX2JsYW5rIj5qaW5tZWlAd2lkZS5hZC5qcDwvYT4mZ3Q7PC9zcGFuPiB3cm90
ZTo8YnI+PGRpdiBjbGFzcz0iZ21haWxfZXh0cmEiPjxkaXYgY2xhc3M9ImdtYWlsX3F1b3RlIj48
YmxvY2txdW90ZSBjbGFzcz0iZ21haWxfcXVvdGUiIHN0eWxlPSJtYXJnaW46MHB4IDBweCAwcHgg
MC44ZXg7Ym9yZGVyLWxlZnQ6MXB4IHNvbGlkIHJnYigyMDQsMjA0LDIwNCk7cGFkZGluZy1sZWZ0
OjFleCI+DQpBdCBXZWQsIDIzIE9jdCAyMDEzIDE1OjU2OjQ2IC0wNDAwLDxicj4NCjxkaXYgY2xh
c3M9ImltIj5SYWxwaCBEcm9tcyAmbHQ7PGEgaHJlZj0ibWFpbHRvOnJkcm9tcy5pZXRmQGdtYWls
LmNvbSI+cmRyb21zLmlldGZAZ21haWwuY29tPC9hPiZndDsgd3JvdGU6PGJyPg0KPGJyPg0KJmd0
OyBQZXJoYXBzIHdlIHdhbnQgdG8gZ28gYSBzdGVwIGZhcnRoZXIgYW5kIHRha2UgdGhlIHpvbmUg
Ym91bmRhcnkgdGV4dDxicj4NCiZndDsgb3V0IG9mIFJGQyA0MDA3IGFsdG9nZXRoZXI/PGJyPg0K
PGJyPg0KPC9kaXY+QmFzaWNhbGx5IHdvcmtzIGZvciBtZS48YnI+DQo8ZGl2IGNsYXNzPSJpbSI+
PGJyPg0KJmd0OyBPTEQ6PGJyPg0KJmd0Ozxicj4NCiZndDsgJm5ic3A7IG8gJm5ic3A7VGhlIGJv
dW5kYXJpZXMgb2Ygem9uZXMgb2YgYSBzY29wZSBvdGhlciB0aGFuIGludGVyZmFjZS1sb2NhbCw8
YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgJm5ic3A7bGluay1sb2NhbCwgYW5kIGdsb2JhbCBtdXN0
IGJlIGRlZmluZWQgYW5kIGNvbmZpZ3VyZWQgYnkgbmV0d29yazxicj4NCiZndDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDthZG1pbmlzdHJhdG9yczxicj4NCiZndDs8YnI+DQomZ3Q7IE5FVzo8YnI+DQom
Z3Q7PGJyPg0KJmd0OyAmbmJzcDsgbyAmbmJzcDtUaGUgYm91bmRhcmllcyBvZiB6b25lcyBvZiBh
IHNjb3BlIGFyZSBkZWZpbmVkIGJ5IHRoZSBJUHY2PGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7ICZu
YnNwO2FkZHJlc3NpbmcgYXJjaGl0ZWN0dXJlLjxicj4NCjxicj4NCjwvZGl2PldpdGggYSByZWZl
cmVuY2UgKGl0JiMzOTtzIGN1cnJlbnRseSBSRkMgNDI5MSk/PGJyPg0KPGJyPg0KSSYjMzk7ZCBh
bHNvIG5vdGUgdGhhdCBub3QgYWxsIHBvaW50cyBkZXNjcmliZWQgaW4gdGhlIFJGQyA0MDA3IHRl
eHQgYXJlPGJyPg0KZGVzY3JpYmVkIGluIFJGQyA0MjkxIChhdCBsZWFzdCBub3QgdmVyeSBjbGVh
cmx5KS4gJm5ic3A7U28sIG5vdCBqdXN0PGJyPg0KcmVtb3ZlIHRoZSB0ZXh0IGZyb20gUkZDIDQw
MDcsIEkmIzM5O2QgbGlrZSB0byB1bmlmeSBpdCBpbiB0aGUgYWRkcmVzczxicj4NCmFyY2hpdGVj
dHVyZSwgZS5nLiB1cGRhdGUgdGhlIGZvbGxvd2luZyBwYXJ0IG9mIFJGQyA0MjkxOjxicj4NCjxk
aXYgY2xhc3M9ImltIj48YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7QWRt
aW4tTG9jYWwgc2NvcGUgaXMgdGhlIHNtYWxsZXN0IHNjb3BlIHRoYXQgbXVzdCBiZTxicj4NCiZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDthZG1pbmlzdHJhdGl2ZWx5IGNvbmZpZ3Vy
ZWQsIGkuZS4sIG5vdCBhdXRvbWF0aWNhbGx5IGRlcml2ZWQ8YnI+DQombmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ZnJvbSBwaHlzaWNhbCBjb25uZWN0aXZpdHkgb3Igb3RoZXIsIG5v
bi1tdWx0aWNhc3QtcmVsYXRlZDxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDtjb25maWd1cmF0aW9uLjxicj4NCjxicj4NCjwvZGl2PmFzIGZvbGxvd3M6PGJyPg0KPGRpdiBj
bGFzcz0iaW0iPjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtBZG1pbi1M
b2NhbCBzY29wZSBpcyB0aGUgc21hbGxlc3Qgc2NvcGUgdGhhdCBtdXN0IGJlPGJyPg0KJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO2FkbWluaXN0cmF0aXZlbHkgY29uZmlndXJlZCwg
aS5lLiwgbm90IGF1dG9tYXRpY2FsbHkgZGVyaXZlZDxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDtmcm9tIHBoeXNpY2FsIGNvbm5lY3Rpdml0eSBvciBvdGhlciwgbm9uLW11
bHRpY2FzdC1yZWxhdGVkPGJyPg0KPC9kaXY+Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwO2NvbmZpZ3VyYXRpb24uICZuYnNwO0ZvciBhbGwgbm9uLXJlc2VydmVkIHNjb3BlcyBleGNl
cHQgdGhlIGdsb2JhbDxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtzY29w
ZSwgdGhlIHpvbmUgYm91bmRhcmllcyBtdXN0IGFsc28gYmUgYWRtaW5pc3RyYXRpdmVseTxicj4N
CiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtjb25maWd1cmVkLjxicj4NCjxkaXYg
Y2xhc3M9IiI+PGRpdiBjbGFzcz0iaDUiPjxicj48L2Rpdj48L2Rpdj48L2Jsb2NrcXVvdGU+PGRp
dj5JIHRoaW5rIHRoaXMgc3RhdGVtZW50IGlzIHNlbGYtY29udHJhZGljdG9yeS4mbmJzcDsgV2hl
biBhdXRvbWF0aWMgY29uZmlndXJhdGlvbiBpczxicj5kaXNjdXNzZWQsIGl0IGlzIGluIHJlbGF0
aW9uIHRvIHpvbmUgYm91bmRhcmllcy4mbmJzcDsgSGVyZSYjMzk7cyBhbiBhdHRlbXB0IHRvIGV4
cGxhaW48YnI+DQo8L2Rpdj48ZGl2PnRoaXMgd2l0aG91dCBuZWdhdGlvbnM6PGJyPjxicj48L2Rp
dj48ZGl2PiZuYnNwOyAmbmJzcDsgSW50ZXJmYWNlLUxvY2FsLCBMaW5rLUxvY2FsLCBhbmQgUmVh
bG0tTG9jYWwgc2NvcGUgYm91bmRhcmllcyBhcmUgYXV0b21hdGljYWxseTxicj48L2Rpdj48ZGl2
PiZuYnNwOyZuYnNwOyZuYnNwOyBkZXJpdmVkIGZyb20gcGh5c2ljYWwgY29ubmVjdGl2aXR5IG9y
IG90aGVyLCBub24tbXVsdGljYXN0IHJlbGF0ZWQgY29uZmlndXJhdGlvbi48YnI+DQo8L2Rpdj48
ZGl2PiZuYnNwOyZuYnNwOyZuYnNwOyBHbG9iYWwgc2NvcGUgaGFzIG5vIGJvdW5kYXJ5LiZuYnNw
OyBUaGUgYm91bmRhcmllcyBvZiBhbGwgb3RoZXIgbm9uLXJlc2VydmVkIHNjb3Blczxicj48L2Rp
dj48ZGl2PiZuYnNwOyZuYnNwOyZuYnNwOyBhcmUgYWRtaW5pc3RyYXRpdmVseSBjb25maWd1cmVk
Ljxicj48YnI+PC9kaXY+PGRpdj5CVFcsIGp1c3QgbXkgb3BpbmlvbiwgYnV0ICZxdW90O1JlYWxt
LUxvY2FsJnF1b3Q7IG1pZ2h0IGJlIG1vcmUgbWVhbmluZ2Z1bGx5IG5hbWVkPGJyPg0KPC9kaXY+
PGRpdj4mcXVvdDtNdWx0aWxpbmstTG9jYWwmcXVvdDs8YnI+PGJyPjwvZGl2PjxkaXY+LUstPGJy
Pjxicj48L2Rpdj48YmxvY2txdW90ZSBjbGFzcz0iZ21haWxfcXVvdGUiIHN0eWxlPSJtYXJnaW46
MHB4IDBweCAwcHggMC44ZXg7Ym9yZGVyLWxlZnQ6MXB4IHNvbGlkIHJnYigyMDQsMjA0LDIwNCk7
cGFkZGluZy1sZWZ0OjFleCI+PGRpdiBjbGFzcz0iIj48ZGl2IGNsYXNzPSJoNSI+DQoNCi0tPGJy
Pg0KSklOTUVJLCBUYXR1eWE8YnI+DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTxicj4NCklFVEYgSVB2NiB3b3JraW5n
IGdyb3VwIG1haWxpbmcgbGlzdDxicj4NCjxhIGhyZWY9Im1haWx0bzppcHY2QGlldGYub3JnIj5p
cHY2QGlldGYub3JnPC9hPjxicj4NCkFkbWluaXN0cmF0aXZlIFJlcXVlc3RzOiA8YSBocmVmPSJo
dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lwdjYiIHRhcmdldD0iX2JsYW5r
Ij5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lwdjY8L2E+PGJyPg0KLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS08YnI+DQo8L2Rpdj48L2Rpdj48L2Jsb2NrcXVvdGU+PC9kaXY+PGJyPjwvZGl2Pjwv
ZGl2Pg0K
--001a11c2e6083efebb04e96f5567--

From jiangsheng@huawei.com  Wed Oct 23 19:18:15 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A4A011E80F2 for <ipv6@ietfa.amsl.com>; Wed, 23 Oct 2013 19:18:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.409
X-Spam-Level: 
X-Spam-Status: No, score=-6.409 tagged_above=-999 required=5 tests=[AWL=-0.126, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6y1iTI5Wlf9p for <ipv6@ietfa.amsl.com>; Wed, 23 Oct 2013 19:18:11 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 286DA11E81C6 for <ipv6@ietf.org>; Wed, 23 Oct 2013 19:18:09 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AZK18136; Thu, 24 Oct 2013 02:18:08 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 24 Oct 2013 03:18:03 +0100
Received: from nkgeml409-hub.china.huawei.com (10.98.56.40) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 24 Oct 2013 03:18:05 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.191]) by nkgeml409-hub.china.huawei.com ([10.98.56.40]) with mapi id 14.03.0146.000; Thu, 24 Oct 2013 10:17:59 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Lorenzo Colitti <lorenzo@google.com>, Brian Haberman <brian@innovationslab.net>
Subject: RE: Need for an overview [was ND Option for NMS Discovery-//FW: New Version Notification for draft-liu-6man-nd-nms-discovery-00.txt]
Thread-Topic: Need for an overview [was ND Option for NMS Discovery-//FW: New	Version Notification for draft-liu-6man-nd-nms-discovery-00.txt]
Thread-Index: AQHOz2gDM3gFfvS6oUiao7LdCu6juZoBthKAgABLagCAARzu4A==
Date: Thu, 24 Oct 2013 02:17:59 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AD4D0FD@nkgeml512-mbx.china.huawei.com>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC189@nkgeml506-mbx.china.huawei.com> <alpine.DEB.2.02.1310221010170.8663@uplift.swm.pp.se> <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC43D@nkgeml506-mbx.china.huawei.com> <alpine.DEB.2.02.1310221102190.8663@uplift.swm.pp.se> <5266E462.9050901@gmail.com> <5267C47B.9070605@innovationslab.net> <CAKD1Yr3wWfzy2T6nLwJQPKX0MSbL+EZ6Q2j0qWQmbH5jgOcKyA@mail.gmail.com>
In-Reply-To: <CAKD1Yr3wWfzy2T6nLwJQPKX0MSbL+EZ6Q2j0qWQmbH5jgOcKyA@mail.gmail.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: multipart/alternative; boundary="_000_5D36713D8A4E7348A7E10DF7437A4B923AD4D0FDnkgeml512mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 24 Oct 2013 02:18:15 -0000

--_000_5D36713D8A4E7348A7E10DF7437A4B923AD4D0FDnkgeml512mbxchi_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

PlN0YXRlbGVzcyBESENQdjYgb3B0aW9uOiB2ZXJ5IGhhcmQgdG8gdXBkYXRlIGZyb20gbmV0d29y
ayBzaWRlDQoNClJlcGx5IHRvIHRoaXMgc2luZ2xlIHBvaW50OiB3ZSBoYXZlIGlkZW50aWZpZWQg
dGhpcyBpc3N1ZSBhbmQgIHdvcmtpbmcgb24gaXQuIEEgbmV3IGRyYWZ0IGhhcyBiZWVuIHN1Ym1p
dHRlZCB0byBESEMgV0cgYW5kIHdvdWxkIGJlIGRpc2N1c3NlZCBpbiBWYW5jb3V2ZXINCg0KaHR0
cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtamlhbmctZGhjLXN0YXRlbGVzcy1yZWNvbmZp
Z3VyYXRpb24NCg0KQmVzdCByZWdhcmRzLA0KDQpTaGVuZw0KDQpGcm9tOiBpcHY2LWJvdW5jZXNA
aWV0Zi5vcmcgW21haWx0bzppcHY2LWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBMb3Jl
bnpvIENvbGl0dGkNClNlbnQ6IFRodXJzZGF5LCBPY3RvYmVyIDI0LCAyMDEzIDE6MTQgQU0NClRv
OiBCcmlhbiBIYWJlcm1hbg0KQ2M6IElFVEYgSVB2NiBNYWlsaW5nIExpc3QNClN1YmplY3Q6IFJl
OiBOZWVkIGZvciBhbiBvdmVydmlldyBbd2FzIE5EIE9wdGlvbiBmb3IgTk1TIERpc2NvdmVyeS0v
L0ZXOiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIGRyYWZ0LWxpdS02bWFuLW5kLW5tcy1k
aXNjb3ZlcnktMDAudHh0XQ0KDQpPbiBXZWQsIE9jdCAyMywgMjAxMyBhdCA5OjQzIFBNLCBCcmlh
biBIYWJlcm1hbiA8YnJpYW5AaW5ub3ZhdGlvbnNsYWIubmV0PG1haWx0bzpicmlhbkBpbm5vdmF0
aW9uc2xhYi5uZXQ+PiB3cm90ZToNCiAgICAgIEdpdmVuIHRoZSBhYm92ZSBhcHByb2FjaCwgSSB3
b3VsZCBzdWdnZXN0IHRoYXQgY29udmluY2luZyB0aGUgV0cNCnRvIGFkb3B0IGEgZHJhZnQgZm9j
dXNlZCBvbiBkZWZpbmluZyB0aGF0IHJlbGF0aW9uc2hpcCBpcyB0aGUgZmlyc3QNCnN0ZXAuICBJ
ZiB0aGUgV0cgYWRvcHRzIGl0LCBJIHdvdWxkIGhhdmUgbm8gcHJvYmxlbXMgd29ya2luZyB3aXRo
IHRoZQ0KY2hhaXJzIHRvIGFkZCBpdCB0byB0aGUgbWlsZXN0b25lcy4NCg0KSSBhZ3JlZSB0aGF0
IHdlJ3JlIGFib3V0IGR1ZSB0byBhdHRlbXB0IHRvIGhhdmUgdGhpcyBjb252ZXJzYXRpb24gYWdh
aW4uIFdobyBrbm93cywgbm93IHRoYXQgd2UgaGF2ZSBtb3JlIG9wZXJhdGlvbmFsIGFuZCBkZXBs
b3ltZW50IGV4cGVyaWVuY2UgdGhhbiB3ZSBkaWQgbGFzdCB0aW1lLCB0aGUgb3V0Y29tZSBtaWdo
dCBiZSBkaWZmZXJlbnQuDQoNClJhdGhlciB0aGFuIGhhdmUgYW4gYXJndW1lbnQgYmFzZWQgb24g
c2luZ2xlIHVzZSBjYXNlcywgd2hhdCBtaWdodCBiZSB1c2VmdWwgaXMgdG8gc3RhcnQgd2l0aCBh
IGRvY3VtZW50IHRoYXQgbGlzdHMgdGhlIGJhc2ljIHRlY2huaWNhbCBwcm9wZXJ0aWVzIC8gc2Vt
YW50aWNzIG9mIHRoZSBtZWNoYW5pc21zIHRoZW1zZWx2ZXMuIEZvciBleGFtcGxlOg0KDQpSQSBv
cHRpb246IHNlbnQgYnkgdGhlIHJvdXRlcjsgcmVxdWlyZXMgbm8gc2VydmVyOyBoYXJkIHRvIHJl
bGF5IC8gYXBwbHkgcG9saWN5OyBlYXN5IHRvIHVwZGF0ZSBhdCBhbnkgdGltZSwgZXZlbiBpZiB0
aGUgb3JpZ2luYWwgcm91dGVyIGhhcyBjcmFzaGVkOyBzY2FsZXMgd2l0aCByb3V0ZXIgQ1BVOyBz
aGFyZXMgZmF0ZSB3aXRoIHJvdXRpbmc7IHN1cHBvcnRzIG1lcmdpbmcgbXVsdGlwbGUgc291cmNl
cyBvZiBpbmZvcm1hdGlvbi4NCg0KU3RhdGVsZXNzIERIQ1B2NiBvcHRpb246IHNlbnQgYnkgYSBz
ZXJ2ZXI7IHJlcXVpcmVzIGEgc2VydmVyOyBlYXN5IHRvIHJlbGF5IC8gYXBwbHkgcG9saWN5OyBz
Y2FsZXMgd2l0aCBzZXJ2ZXIgQ1BVICh3aGljaCBjYW4gYmUgYmV0dGVyIG9yIHdvcnNlIHRoYW4g
cm91dGVyIENQVSBkZXBlbmRpbmcgb24gaG93IG1hbnkgdGhvdXNhbmRzL21pbGxpb25zIG9mIGNs
aWVudHMgeW91IHNlbmQgdG8gYSBzaW5nbGUgc2VydmVyKTsgdmVyeSBoYXJkIHRvIHVwZGF0ZSBm
cm9tIG5ldHdvcmsgc2lkZTsgZG9lc24ndCBzaGFyZSBmYXRlIHdpdGggcm91dGluZzsgZG9lc24n
dCBzdXBwb3J0IG1lcmdpbmcgbXVsdGlwbGUgc291cmNlcyBvZiBpbmZvcm1hdGlvbi4NCg0KIldl
IGRvIGl0IHRoaXMgd2F5IGluIElQdjQiIG9yICJ0aGUgbWFya2V0IGlzIGFza2luZyBmb3IgaXQi
ICh3aGljaCBhcmUgbW9zdGx5LCB0aG91Z2ggcGVyaGFwcyBub3QgZW50aXJlbHksIHRoZSBzYW1l
IGFyZ3VtZW50KSB3b3VsZCBleHBsaWNpdGx5IG5vdCBiZSBhIHBhcnQgb2YgdGhpcyBkb2N1bWVu
dCBiZWNhdXNlIHRoZXkncmUgbm90IHRlY2huaWNhbCBwcm9wZXJ0aWVzIG9mIHRoZSBwcm90b2Nv
bHMuDQoNClRoZSBob3BlIHdvdWxkIGJlIHRoYXQgd2UgZG9uJ3QgZnVuZGFtZW50YWxseSBkaXNh
Z3JlZSBvbiB0aGUgcHJvcGVydGllcyBvZiB0aGUgdHdvIHByb3Zpc2lvbmluZyBwcm90b2NvbHMs
IG9ubHkgb24gd2hpY2ggY2hhcmFjdGVyaXN0aWNzIGFyZSBtb3JlIGltcG9ydGFudCBpbiB3aGlj
aCBkZXBsb3ltZW50IHNjZW5hcmlvcy4gSWYgdGhhdCdzIHRydWUsIGFuZCB3ZSB3ZXJlIGFibGUg
dG8gYWdyZWUgb24gdGhpcyBkb2N1bWVudCBkZXNjcmliaW5nIHRoZSBwcm9wZXJ0aWVzLCB0aGVu
IHdlIG1pZ2h0IGxhdGVyIGJlIGFibGUgdG8gbW92ZSB0b3dhcmRzIGRlY2lkaW5nIHdoYXQga2lu
ZHMgb2Ygb3B0aW9ucyBnbyBpbnRvIHdoaWNoIHByb3RvY29sLg0K

--_000_5D36713D8A4E7348A7E10DF7437A4B923AD4D0FDnkgeml512mbxchi_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRvciIgY29udGVu
dD0iTWljcm9zb2Z0IFdvcmQgMTIgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxlPjwhLS0NCi8q
IEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6U2ltU3VuOw0K
CXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWls
eToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0O30NCkBmb250
LWZhY2UNCgl7Zm9udC1mYW1pbHk6VGFob21hOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDMgNSA0IDQg
MiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6U2ltU3VuOw0KCXBhbm9zZS0xOjIgMSA2
IDAgMyAxIDEgMSAxIDE7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBs
aS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9t
Oi4wMDAxcHQ7DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJv
bWFuIiwic2VyaWYiO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQph
OnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnNwYW4u
RW1haWxTdHlsZTE3DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFt
aWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQouTXNvQ2hwRGVm
YXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTt9DQpAcGFnZSBXb3JkU2VjdGlvbjEN
Cgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA5MC4wcHQgNzIuMHB0IDkw
LjBwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5
bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0
IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDld
Pjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRp
dCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVh
ZD4NCjxib2R5IGxhbmc9IlpILUNOIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYg
Y2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2lu
LWxlZnQ6NC44cHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4mZ3Q7U3RhdGVsZXNzIERIQ1B2NiBvcHRp
b246IHZlcnkgaGFyZCB0byB1cGRhdGUgZnJvbSBuZXR3b3JrIHNpZGU8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6NC44cHQiPjxz
cGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6NC44cHQiPjxzcGFuIGxhbmc9IkVOLVVTIj5S
ZXBseSB0byB0aGlzIHNpbmdsZSBwb2ludDogd2UgaGF2ZSBpZGVudGlmaWVkIHRoaXMgaXNzdWUg
YW5kJm5ic3A7IHdvcmtpbmcgb24gaXQuIEEgbmV3IGRyYWZ0IGhhcyBiZWVuIHN1Ym1pdHRlZCB0
byBESEMgV0cgYW5kIHdvdWxkIGJlIGRpc2N1c3NlZCBpbiBWYW5jb3V2ZXI8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6NC44cHQi
PjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6NC44cHQiPjxzcGFuIGxhbmc9IkVOLVVT
Ij48YSBocmVmPSJodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1qaWFuZy1kaGMtc3Rh
dGVsZXNzLXJlY29uZmlndXJhdGlvbiI+aHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQt
amlhbmctZGhjLXN0YXRlbGVzcy1yZWNvbmZpZ3VyYXRpb248L2E+PG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjQuOHB0Ij48c3Bh
biBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjQuOHB0Ij48c3BhbiBsYW5nPSJFTi1VUyI+QmVz
dCByZWdhcmRzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtYXJnaW4tbGVmdDo0LjhwdCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDo0
LjhwdCI+PHNwYW4gbGFuZz0iRU4tVVMiPlNoZW5nPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjQuOHB0Ij48c3BhbiBsYW5nPSJF
Ti1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5v
bmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0
Ij4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0
REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwY20gMGNtIDBjbSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48Yj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkZyb206PC9zcGFu
PjwvYj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiBpcHY2LWJvdW5j
ZXNAaWV0Zi5vcmcgW21haWx0bzppcHY2LWJvdW5jZXNAaWV0Zi5vcmddDQo8Yj5PbiBCZWhhbGYg
T2YgPC9iPkxvcmVuem8gQ29saXR0aTxicj4NCjxiPlNlbnQ6PC9iPiBUaHVyc2RheSwgT2N0b2Jl
ciAyNCwgMjAxMyAxOjE0IEFNPGJyPg0KPGI+VG86PC9iPiBCcmlhbiBIYWJlcm1hbjxicj4NCjxi
PkNjOjwvYj4gSUVURiBJUHY2IE1haWxpbmcgTGlzdDxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTog
TmVlZCBmb3IgYW4gb3ZlcnZpZXcgW3dhcyBORCBPcHRpb24gZm9yIE5NUyBEaXNjb3ZlcnktLy9G
VzogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC1saXUtNm1hbi1uZC1ubXMtZGlz
Y292ZXJ5LTAwLnR4dF08bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+
T24gV2VkLCBPY3QgMjMsIDIwMTMgYXQgOTo0MyBQTSwgQnJpYW4gSGFiZXJtYW4gJmx0OzxhIGhy
ZWY9Im1haWx0bzpicmlhbkBpbm5vdmF0aW9uc2xhYi5uZXQiIHRhcmdldD0iX2JsYW5rIj5icmlh
bkBpbm5vdmF0aW9uc2xhYi5uZXQ8L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8ZGl2Pg0KPGRpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVm
dDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxl
ZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBs
YW5nPSJFTi1VUyI+Jm5ic3A7ICZuYnNwOyAmbmJzcDsgR2l2ZW4gdGhlIGFib3ZlIGFwcHJvYWNo
LCBJIHdvdWxkIHN1Z2dlc3QgdGhhdCBjb252aW5jaW5nIHRoZSBXRzxicj4NCnRvIGFkb3B0IGEg
ZHJhZnQgZm9jdXNlZCBvbiBkZWZpbmluZyB0aGF0IHJlbGF0aW9uc2hpcCBpcyB0aGUgZmlyc3Q8
YnI+DQpzdGVwLiAmbmJzcDtJZiB0aGUgV0cgYWRvcHRzIGl0LCBJIHdvdWxkIGhhdmUgbm8gcHJv
YmxlbXMgd29ya2luZyB3aXRoIHRoZTxicj4NCmNoYWlycyB0byBhZGQgaXQgdG8gdGhlIG1pbGVz
dG9uZXMuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJF
Ti1VUyI+SSBhZ3JlZSB0aGF0IHdlJ3JlIGFib3V0IGR1ZSB0byBhdHRlbXB0IHRvIGhhdmUgdGhp
cyBjb252ZXJzYXRpb24gYWdhaW4uIFdobyBrbm93cywgbm93IHRoYXQgd2UgaGF2ZSBtb3JlIG9w
ZXJhdGlvbmFsIGFuZCBkZXBsb3ltZW50IGV4cGVyaWVuY2UgdGhhbiB3ZSBkaWQgbGFzdCB0aW1l
LCB0aGUgb3V0Y29tZSBtaWdodCBiZSBkaWZmZXJlbnQuPG86cD48L286cD48L3NwYW4+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5SYXRoZXIgdGhhbiBoYXZlIGFuIGFyZ3VtZW50IGJh
c2VkIG9uIHNpbmdsZSB1c2UgY2FzZXMsIHdoYXQgbWlnaHQgYmUgdXNlZnVsIGlzIHRvIHN0YXJ0
IHdpdGggYSBkb2N1bWVudCB0aGF0IGxpc3RzIHRoZSBiYXNpYyB0ZWNobmljYWwgcHJvcGVydGll
cyAvIHNlbWFudGljcyBvZiB0aGUgbWVjaGFuaXNtcyB0aGVtc2VsdmVzLiBGb3IgZXhhbXBsZTo8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPlJBIG9wdGlv
bjogc2VudCBieSB0aGUgcm91dGVyOyByZXF1aXJlcyBubyBzZXJ2ZXI7IGhhcmQgdG8gcmVsYXkg
LyBhcHBseSBwb2xpY3k7IGVhc3kgdG8gdXBkYXRlIGF0IGFueSB0aW1lLCBldmVuIGlmIHRoZSBv
cmlnaW5hbCByb3V0ZXIgaGFzIGNyYXNoZWQ7IHNjYWxlcyB3aXRoIHJvdXRlciBDUFU7IHNoYXJl
cyBmYXRlIHdpdGggcm91dGluZzsgc3VwcG9ydHMgbWVyZ2luZw0KIG11bHRpcGxlIHNvdXJjZXMg
b2YgaW5mb3JtYXRpb24uPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9
IkVOLVVTIj5TdGF0ZWxlc3MgREhDUHY2IG9wdGlvbjogc2VudCBieSBhIHNlcnZlcjsgcmVxdWly
ZXMgYSBzZXJ2ZXI7IGVhc3kgdG8gcmVsYXkgLyBhcHBseSBwb2xpY3k7IHNjYWxlcyB3aXRoIHNl
cnZlciBDUFUgKHdoaWNoIGNhbiBiZSBiZXR0ZXIgb3Igd29yc2UgdGhhbiByb3V0ZXIgQ1BVIGRl
cGVuZGluZyBvbiBob3cgbWFueSB0aG91c2FuZHMvbWlsbGlvbnMgb2YgY2xpZW50cyB5b3UNCiBz
ZW5kIHRvIGEgc2luZ2xlIHNlcnZlcik7IHZlcnkgaGFyZCB0byB1cGRhdGUgZnJvbSBuZXR3b3Jr
IHNpZGU7IGRvZXNuJ3Qgc2hhcmUgZmF0ZSB3aXRoIHJvdXRpbmc7IGRvZXNuJ3Qgc3VwcG9ydCBt
ZXJnaW5nIG11bHRpcGxlIHNvdXJjZXMgb2YgaW5mb3JtYXRpb24uPG86cD48L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4t
VVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj4mcXVvdDtXZSBkbyBpdCB0aGlzIHdheSBp
biBJUHY0JnF1b3Q7IG9yICZxdW90O3RoZSBtYXJrZXQgaXMgYXNraW5nIGZvciBpdCZxdW90OyAo
d2hpY2ggYXJlIG1vc3RseSwgdGhvdWdoIHBlcmhhcHMgbm90IGVudGlyZWx5LCB0aGUgc2FtZSBh
cmd1bWVudCkgd291bGQgZXhwbGljaXRseSBub3QgYmUgYSBwYXJ0IG9mIHRoaXMgZG9jdW1lbnQg
YmVjYXVzZSB0aGV5J3JlIG5vdCB0ZWNobmljYWwgcHJvcGVydGllcw0KIG9mIHRoZSBwcm90b2Nv
bHMuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5UaGUg
aG9wZSB3b3VsZCBiZSB0aGF0IHdlIGRvbid0IGZ1bmRhbWVudGFsbHkgZGlzYWdyZWUgb24gdGhl
IHByb3BlcnRpZXMgb2YgdGhlIHR3byBwcm92aXNpb25pbmcgcHJvdG9jb2xzLCBvbmx5IG9uIHdo
aWNoIGNoYXJhY3RlcmlzdGljcyBhcmUgbW9yZSBpbXBvcnRhbnQgaW4gd2hpY2ggZGVwbG95bWVu
dCBzY2VuYXJpb3MuIElmIHRoYXQncyB0cnVlLCBhbmQgd2Ugd2VyZSBhYmxlDQogdG8gYWdyZWUg
b24gdGhpcyBkb2N1bWVudCBkZXNjcmliaW5nIHRoZSBwcm9wZXJ0aWVzLCB0aGVuIHdlIG1pZ2h0
IGxhdGVyIGJlIGFibGUgdG8gbW92ZSB0b3dhcmRzIGRlY2lkaW5nIHdoYXQga2luZHMgb2Ygb3B0
aW9ucyBnbyBpbnRvIHdoaWNoIHByb3RvY29sLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRt
bD4NCg==

--_000_5D36713D8A4E7348A7E10DF7437A4B923AD4D0FDnkgeml512mbxchi_--

From robert.cragie@gmail.com  Wed Oct 23 23:59:21 2013
Return-Path: <robert.cragie@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F140F11E8159; Wed, 23 Oct 2013 23:59:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.101
X-Spam-Level: 
X-Spam-Status: No, score=-1.101 tagged_above=-999 required=5 tests=[AWL=-0.876, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 808w3twucFbK; Wed, 23 Oct 2013 23:59:10 -0700 (PDT)
Received: from mail-ea0-x229.google.com (mail-ea0-x229.google.com [IPv6:2a00:1450:4013:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 6D62711E82F3; Wed, 23 Oct 2013 23:59:07 -0700 (PDT)
Received: by mail-ea0-f169.google.com with SMTP id k11so966836eaj.0 for <multiple recipients>; Wed, 23 Oct 2013 23:59:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=R3Dhr67wafdDkYy9fVc6IjrkYoYaoOomnNzDFhjXspI=; b=EadZmlt2x5Tc6cv2+i+Epro3UYDTI+UBjgVZ16NTd85K4vTTY/c+7jekVe7le/VpoX cm3RH7jcKojo5WjNgM5vhBX5C5+xuqXDEpbOQvPLBrzHNQF2fLKLTNNsumiKYLlPCKg/ hs6AnRqE/w6UgmOJ2ARRPgcVRcLATH5lnVWIopXX6LnWgKk9IpIQgbDr3TAuPzst7o0h XijtrWFSb4VY/fDc9TrlO5i50XTnMTUobgoVOHbIKJ3FPJF285rjs7L8Q1qIu3FjO/xw iFScm6+Twuk9cNONvG/I8cFhFLDI6nnMIqQHKLEFcuEEYeUpBl0Lz+jhtN+STGl4Tt7g xFvQ==
MIME-Version: 1.0
X-Received: by 10.14.183.2 with SMTP id p2mr1307714eem.44.1382597945813; Wed, 23 Oct 2013 23:59:05 -0700 (PDT)
Sender: robert.cragie@gmail.com
Received: by 10.15.44.1 with HTTP; Wed, 23 Oct 2013 23:59:05 -0700 (PDT)
In-Reply-To: <CABOxzu20qONjQ71EWyob2Th+PJGpFz_Cw8jhvbmiEtojd+ihHg@mail.gmail.com>
References: <3599.1381852752@sandelman.ca> <CE82BA46.24343%d.sturek@att.net> <CABOxzu2nLuny5uySEEdb6ji9ucE6xqGZ6DLe-mc6KUqVszNfFg@mail.gmail.com> <525DC6C9.2010808@gridmerge.com> <CABOxzu2apwBRpU1h4mKJwpO+U+Y9Q_q-h5AhZ+hGzAdjdPdmUQ@mail.gmail.com> <525E5064.4050109@gridmerge.com> <CABOxzu0L-EY0iDGpAJ+ER15CPL-3v8F77ewn-G=gZYODixevZg@mail.gmail.com> <3CC8783F-F4DA-47B9-A051-DBBA6EF00C19@gmail.com> <CAJE_bqdL3v4XK+dJPx1ZVFoRS+yjFDZEwVZ64fhYW6QUWVS6JA@mail.gmail.com> <52FECA00-C316-4693-A821-7EA6510AC0F8@gmail.com> <CAJE_bqcvQSiNTbbOvUEBvLC1uK5kAFfF04ZbQ=DFpwKb+ynATw@mail.gmail.com> <CABOxzu20qONjQ71EWyob2Th+PJGpFz_Cw8jhvbmiEtojd+ihHg@mail.gmail.com>
Date: Thu, 24 Oct 2013 07:59:05 +0100
X-Google-Sender-Auth: EGg-qmv2qUs_f5sC0EbR9R6Dr3c
Message-ID: <CADrU+dJQdxWoEpLdZq_vYf1CcV1nh43v+votYZ4WCqwj+o1r3Q@mail.gmail.com>
Subject: Re: [Roll] draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re: [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope value of 3 - subnet-local)
From: Robert Cragie <robert.cragie@gridmerge.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b343dc46d717704e9772b07
X-Mailman-Approved-At: Thu, 24 Oct 2013 01:04:46 -0700
Cc: "6man@ietf.org" <6man@ietf.org>, =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert.cragie@gridmerge.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: Thu, 24 Oct 2013 06:59:21 -0000

--047d7b343dc46d717704e9772b07
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit

On 23 October 2013 22:38, Kerry Lynn <kerlyn@ieee.org> wrote:

> On Wed, Oct 23, 2013 at 5:21 PM, $B?@L@C#:H(B <jinmei@wide.ad.jp> wrote:
>
>> At Wed, 23 Oct 2013 15:56:46 -0400,
>>
>> Ralph Droms <rdroms.ietf@gmail.com> wrote:
>>
>> > Perhaps we want to go a step farther and take the zone boundary text
>> > out of RFC 4007 altogether?
>>
>> Basically works for me.
>
> <RCC>Me too</RCC>

>
>>
>> > OLD:
>> >
>> >   o  The boundaries of zones of a scope other than interface-local,
>> >      link-local, and global must be defined and configured by network
>> >      administrators
>> >
>> > NEW:
>> >
>> >   o  The boundaries of zones of a scope are defined by the IPv6
>> >      addressing architecture.
>>
>> With a reference (it's currently RFC 4291)?
>>
>> I'd also note that not all points described in the RFC 4007 text are
>> described in RFC 4291 (at least not very clearly).  So, not just
>> remove the text from RFC 4007, I'd like to unify it in the address
>> architecture, e.g. update the following part of RFC 4291:
>>
>>
>>          Admin-Local scope is the smallest scope that must be
>>          administratively configured, i.e., not automatically derived
>>          from physical connectivity or other, non-multicast-related
>>          configuration.
>>
>> as follows:
>>
>>
>>          Admin-Local scope is the smallest scope that must be
>>          administratively configured, i.e., not automatically derived
>>          from physical connectivity or other, non-multicast-related
>>          configuration.  For all non-reserved scopes except the global
>>          scope, the zone boundaries must also be administratively
>>          configured.
>>
>> I think this statement is self-contradictory.  When automatic
> configuration is
> discussed, it is in relation to zone boundaries.  Here's an attempt to
> explain
> this without negations:
>
>     Interface-Local, Link-Local, and Realm-Local scope boundaries are
> automatically
>     derived from physical connectivity or other, non-multicast related
> configuration.
>     Global scope has no boundary.  The boundaries of all other
> non-reserved scopes
>     are administratively configured.
>
<RCC>
That makes it clear. IMO RFC4007 should be changed to something like:

o  Each interface on a node comprises a single zone of interface-local
scope (for multicast only).

o  Each link and the interfaces attached to that link comprise a single
zone of link-local scope (for both unicast and multicast).

o  Multiple links and the interfaces attached to those links may form a
multilink-local scope based on underlying network technology; for example,
[cite the IP-over-IEEE802.15.4 definition].

o  There is a single zone of global scope (for both unicast and multicast)
comprising all the links and interfaces in the Internet.

o  The boundaries of zones of a scope other than interface-local,
link-local, multilink-local and global must be defined and configured by
network administrators.

Either that or just remove the text as Ralph suggested earlier.
</RCC>

>
> BTW, just my opinion, but "Realm-Local" might be more meaningfully named
> "Multilink-Local"
>
<RCC> I agree - it is more meaningful</RCC>

>
>
> -K-
>
>  --
>> JINMEI, Tatuya
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
>
>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>
>

--047d7b343dc46d717704e9772b07
Content-Type: text/html; charset=ISO-2022-JP
Content-Transfer-Encoding: base64

PGRpdiBkaXI9Imx0ciI+PGJyPjxkaXYgY2xhc3M9ImdtYWlsX2V4dHJhIj48YnI+PGJyPjxkaXYg
Y2xhc3M9ImdtYWlsX3F1b3RlIj5PbiAyMyBPY3RvYmVyIDIwMTMgMjI6MzgsIEtlcnJ5IEx5bm4g
PHNwYW4gZGlyPSJsdHIiPiZsdDs8YSBocmVmPSJtYWlsdG86a2VybHluQGllZWUub3JnIiB0YXJn
ZXQ9Il9ibGFuayI+a2VybHluQGllZWUub3JnPC9hPiZndDs8L3NwYW4+IHdyb3RlOjxicj4NCg0K
PGJsb2NrcXVvdGUgY2xhc3M9ImdtYWlsX3F1b3RlIiBzdHlsZT0ibWFyZ2luOjBweCAwcHggMHB4
IDAuOGV4O2JvcmRlci1sZWZ0LXdpZHRoOjFweDtib3JkZXItbGVmdC1jb2xvcjpyZ2IoMjA0LDIw
NCwyMDQpO2JvcmRlci1sZWZ0LXN0eWxlOnNvbGlkO3BhZGRpbmctbGVmdDoxZXgiPjxkaXYgZGly
PSJsdHIiPk9uIFdlZCwgT2N0IDIzLCAyMDEzIGF0IDU6MjEgUE0sIBskQj9ATEBDIzpIGyhCIDxz
cGFuIGRpcj0ibHRyIj4mbHQ7PGEgaHJlZj0ibWFpbHRvOmppbm1laUB3aWRlLmFkLmpwIiB0YXJn
ZXQ9Il9ibGFuayI+amlubWVpQHdpZGUuYWQuanA8L2E+Jmd0Ozwvc3Bhbj4gd3JvdGU6PGJyPg0K
DQo8ZGl2IGNsYXNzPSJnbWFpbF9leHRyYSI+PGRpdiBjbGFzcz0iZ21haWxfcXVvdGUiPjxibG9j
a3F1b3RlIGNsYXNzPSJnbWFpbF9xdW90ZSIgc3R5bGU9Im1hcmdpbjowcHggMHB4IDBweCAwLjhl
eDtib3JkZXItbGVmdC13aWR0aDoxcHg7Ym9yZGVyLWxlZnQtc3R5bGU6c29saWQ7Ym9yZGVyLWxl
ZnQtY29sb3I6cmdiKDIwNCwyMDQsMjA0KTtwYWRkaW5nLWxlZnQ6MWV4Ij4NCkF0IFdlZCwgMjMg
T2N0IDIwMTMgMTU6NTY6NDYgLTA0MDAsPGRpdj48YnI+DQo8ZGl2PlJhbHBoIERyb21zICZsdDs8
YSBocmVmPSJtYWlsdG86cmRyb21zLmlldGZAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+cmRy
b21zLmlldGZAZ21haWwuY29tPC9hPiZndDsgd3JvdGU6PGJyPg0KPGJyPg0KJmd0OyBQZXJoYXBz
IHdlIHdhbnQgdG8gZ28gYSBzdGVwIGZhcnRoZXIgYW5kIHRha2UgdGhlIHpvbmUgYm91bmRhcnkg
dGV4dDxicj4NCiZndDsgb3V0IG9mIFJGQyA0MDA3IGFsdG9nZXRoZXI/PGJyPg0KPGJyPg0KPC9k
aXY+PC9kaXY+QmFzaWNhbGx5IHdvcmtzIGZvciBtZS48L2Jsb2NrcXVvdGU+PC9kaXY+PC9kaXY+
PC9kaXY+PC9ibG9ja3F1b3RlPjxkaXY+Jmx0O1JDQyZndDtNZSB0b28mbHQ7L1JDQyZndDsmbmJz
cDs8L2Rpdj48YmxvY2txdW90ZSBjbGFzcz0iZ21haWxfcXVvdGUiIHN0eWxlPSJtYXJnaW46MHB4
IDBweCAwcHggMC44ZXg7Ym9yZGVyLWxlZnQtd2lkdGg6MXB4O2JvcmRlci1sZWZ0LWNvbG9yOnJn
YigyMDQsMjA0LDIwNCk7Ym9yZGVyLWxlZnQtc3R5bGU6c29saWQ7cGFkZGluZy1sZWZ0OjFleCI+
DQoNCjxkaXYgZGlyPSJsdHIiPjxkaXYgY2xhc3M9ImdtYWlsX2V4dHJhIj48ZGl2IGNsYXNzPSJn
bWFpbF9xdW90ZSI+PGJsb2NrcXVvdGUgY2xhc3M9ImdtYWlsX3F1b3RlIiBzdHlsZT0ibWFyZ2lu
OjBweCAwcHggMHB4IDAuOGV4O2JvcmRlci1sZWZ0LXdpZHRoOjFweDtib3JkZXItbGVmdC1zdHls
ZTpzb2xpZDtib3JkZXItbGVmdC1jb2xvcjpyZ2IoMjA0LDIwNCwyMDQpO3BhZGRpbmctbGVmdDox
ZXgiPg0KPGRpdj48YnI+DQo8ZGl2Pjxicj4NCiZndDsgT0xEOjxicj4NCiZndDs8YnI+DQomZ3Q7
ICZuYnNwOyBvICZuYnNwO1RoZSBib3VuZGFyaWVzIG9mIHpvbmVzIG9mIGEgc2NvcGUgb3RoZXIg
dGhhbiBpbnRlcmZhY2UtbG9jYWwsPGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7ICZuYnNwO2xpbmst
bG9jYWwsIGFuZCBnbG9iYWwgbXVzdCBiZSBkZWZpbmVkIGFuZCBjb25maWd1cmVkIGJ5IG5ldHdv
cms8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgJm5ic3A7YWRtaW5pc3RyYXRvcnM8YnI+DQomZ3Q7
PGJyPg0KJmd0OyBORVc6PGJyPg0KJmd0Ozxicj4NCiZndDsgJm5ic3A7IG8gJm5ic3A7VGhlIGJv
dW5kYXJpZXMgb2Ygem9uZXMgb2YgYSBzY29wZSBhcmUgZGVmaW5lZCBieSB0aGUgSVB2Njxicj4N
CiZndDsgJm5ic3A7ICZuYnNwOyAmbmJzcDthZGRyZXNzaW5nIGFyY2hpdGVjdHVyZS48YnI+DQo8
YnI+DQo8L2Rpdj48L2Rpdj5XaXRoIGEgcmVmZXJlbmNlIChpdCYjMzk7cyBjdXJyZW50bHkgUkZD
IDQyOTEpPzxicj4NCjxicj4NCkkmIzM5O2QgYWxzbyBub3RlIHRoYXQgbm90IGFsbCBwb2ludHMg
ZGVzY3JpYmVkIGluIHRoZSBSRkMgNDAwNyB0ZXh0IGFyZTxicj4NCmRlc2NyaWJlZCBpbiBSRkMg
NDI5MSAoYXQgbGVhc3Qgbm90IHZlcnkgY2xlYXJseSkuICZuYnNwO1NvLCBub3QganVzdDxicj4N
CnJlbW92ZSB0aGUgdGV4dCBmcm9tIFJGQyA0MDA3LCBJJiMzOTtkIGxpa2UgdG8gdW5pZnkgaXQg
aW4gdGhlIGFkZHJlc3M8YnI+DQphcmNoaXRlY3R1cmUsIGUuZy4gdXBkYXRlIHRoZSBmb2xsb3dp
bmcgcGFydCBvZiBSRkMgNDI5MTo8ZGl2Pjxicj4NCjxkaXY+PGJyPg0KJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwO0FkbWluLUxvY2FsIHNjb3BlIGlzIHRoZSBzbWFsbGVzdCBzY29w
ZSB0aGF0IG11c3QgYmU8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7YWRt
aW5pc3RyYXRpdmVseSBjb25maWd1cmVkLCBpLmUuLCBub3QgYXV0b21hdGljYWxseSBkZXJpdmVk
PGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO2Zyb20gcGh5c2ljYWwgY29u
bmVjdGl2aXR5IG9yIG90aGVyLCBub24tbXVsdGljYXN0LXJlbGF0ZWQ8YnI+DQombmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7Y29uZmlndXJhdGlvbi48YnI+DQo8YnI+DQo8L2Rpdj48
L2Rpdj5hcyBmb2xsb3dzOjxkaXY+PGJyPg0KPGRpdj48YnI+DQombmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7QWRtaW4tTG9jYWwgc2NvcGUgaXMgdGhlIHNtYWxsZXN0IHNjb3BlIHRo
YXQgbXVzdCBiZTxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDthZG1pbmlz
dHJhdGl2ZWx5IGNvbmZpZ3VyZWQsIGkuZS4sIG5vdCBhdXRvbWF0aWNhbGx5IGRlcml2ZWQ8YnI+
DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ZnJvbSBwaHlzaWNhbCBjb25uZWN0
aXZpdHkgb3Igb3RoZXIsIG5vbi1tdWx0aWNhc3QtcmVsYXRlZDxicj4NCjwvZGl2PjwvZGl2PiZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtjb25maWd1cmF0aW9uLiAmbmJzcDtGb3Ig
YWxsIG5vbi1yZXNlcnZlZCBzY29wZXMgZXhjZXB0IHRoZSBnbG9iYWw8YnI+DQombmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7c2NvcGUsIHRoZSB6b25lIGJvdW5kYXJpZXMgbXVzdCBh
bHNvIGJlIGFkbWluaXN0cmF0aXZlbHk8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7Y29uZmlndXJlZC48YnI+DQo8ZGl2PjxkaXY+PGJyPjwvZGl2PjwvZGl2PjwvYmxvY2tx
dW90ZT48ZGl2PkkgdGhpbmsgdGhpcyBzdGF0ZW1lbnQgaXMgc2VsZi1jb250cmFkaWN0b3J5LiZu
YnNwOyBXaGVuIGF1dG9tYXRpYyBjb25maWd1cmF0aW9uIGlzPGJyPmRpc2N1c3NlZCwgaXQgaXMg
aW4gcmVsYXRpb24gdG8gem9uZSBib3VuZGFyaWVzLiZuYnNwOyBIZXJlJiMzOTtzIGFuIGF0dGVt
cHQgdG8gZXhwbGFpbjxicj4NCjwvZGl2PjxkaXY+dGhpcyB3aXRob3V0IG5lZ2F0aW9uczo8YnI+
PGJyPjwvZGl2PjxkaXY+Jm5ic3A7ICZuYnNwOyBJbnRlcmZhY2UtTG9jYWwsIExpbmstTG9jYWws
IGFuZCBSZWFsbS1Mb2NhbCBzY29wZSBib3VuZGFyaWVzIGFyZSBhdXRvbWF0aWNhbGx5PGJyPjwv
ZGl2PjxkaXY+Jm5ic3A7Jm5ic3A7Jm5ic3A7IGRlcml2ZWQgZnJvbSBwaHlzaWNhbCBjb25uZWN0
aXZpdHkgb3Igb3RoZXIsIG5vbi1tdWx0aWNhc3QgcmVsYXRlZCBjb25maWd1cmF0aW9uLjxicj4N
Cg0KDQo8L2Rpdj48ZGl2PiZuYnNwOyZuYnNwOyZuYnNwOyBHbG9iYWwgc2NvcGUgaGFzIG5vIGJv
dW5kYXJ5LiZuYnNwOyBUaGUgYm91bmRhcmllcyBvZiBhbGwgb3RoZXIgbm9uLXJlc2VydmVkIHNj
b3Blczxicj48L2Rpdj48ZGl2PiZuYnNwOyZuYnNwOyZuYnNwOyBhcmUgYWRtaW5pc3RyYXRpdmVs
eSBjb25maWd1cmVkLjxicj48L2Rpdj48L2Rpdj48L2Rpdj48L2Rpdj48L2Jsb2NrcXVvdGU+PGRp
dj4mbHQ7UkNDJmd0OzwvZGl2PjxkaXY+VGhhdCBtYWtlcyBpdCBjbGVhci4gSU1PIFJGQzQwMDcg
c2hvdWxkIGJlIGNoYW5nZWQgdG8gc29tZXRoaW5nIGxpa2U6PC9kaXY+DQo8ZGl2Pjxicj48L2Rp
dj48ZGl2PjxkaXY+byAmbmJzcDtFYWNoIGludGVyZmFjZSBvbiBhIG5vZGUgY29tcHJpc2VzIGEg
c2luZ2xlIHpvbmUgb2YgaW50ZXJmYWNlLWxvY2FsIHNjb3BlIChmb3IgbXVsdGljYXN0IG9ubHkp
LjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+byAmbmJzcDtFYWNoIGxpbmsgYW5kIHRoZSBpbnRl
cmZhY2VzIGF0dGFjaGVkIHRvIHRoYXQgbGluayBjb21wcmlzZSBhIHNpbmdsZSB6b25lIG9mIGxp
bmstbG9jYWwgc2NvcGUgKGZvciBib3RoIHVuaWNhc3QgYW5kIG11bHRpY2FzdCkuPC9kaXY+DQo8
ZGl2Pjxicj48L2Rpdj48ZGl2Pm8gJm5ic3A7TXVsdGlwbGUgbGlua3MgYW5kIHRoZSBpbnRlcmZh
Y2VzIGF0dGFjaGVkIHRvIHRob3NlIGxpbmtzIG1heSBmb3JtIGEgbXVsdGlsaW5rLWxvY2FsIHNj
b3BlIGJhc2VkIG9uIHVuZGVybHlpbmcgbmV0d29yayB0ZWNobm9sb2d5OyBmb3IgZXhhbXBsZSwg
W2NpdGUgdGhlIElQLW92ZXItSUVFRTgwMi4xNS40IGRlZmluaXRpb25dLjwvZGl2PjxkaXY+DQo8
YnI+PC9kaXY+PGRpdj5vICZuYnNwO1RoZXJlIGlzIGEgc2luZ2xlIHpvbmUgb2YgZ2xvYmFsIHNj
b3BlIChmb3IgYm90aCB1bmljYXN0IGFuZCBtdWx0aWNhc3QpIGNvbXByaXNpbmcgYWxsIHRoZSBs
aW5rcyBhbmQgaW50ZXJmYWNlcyBpbiB0aGUgSW50ZXJuZXQuPC9kaXY+PGRpdj48YnI+PC9kaXY+
PGRpdj5vICZuYnNwO1RoZSBib3VuZGFyaWVzIG9mIHpvbmVzIG9mIGEgc2NvcGUgb3RoZXIgdGhh
biBpbnRlcmZhY2UtbG9jYWwsIGxpbmstbG9jYWwsIG11bHRpbGluay1sb2NhbCBhbmQgZ2xvYmFs
IG11c3QgYmUgZGVmaW5lZCBhbmQgY29uZmlndXJlZCBieSBuZXR3b3JrIGFkbWluaXN0cmF0b3Jz
LjwvZGl2Pg0KPGRpdj48YnI+PC9kaXY+PGRpdj5FaXRoZXIgdGhhdCBvciBqdXN0IHJlbW92ZSB0
aGUgdGV4dCBhcyBSYWxwaCBzdWdnZXN0ZWQgZWFybGllci48L2Rpdj48ZGl2PiZsdDsvUkNDJmd0
OzwvZGl2PjwvZGl2Pg0KPGJsb2NrcXVvdGUgY2xhc3M9ImdtYWlsX3F1b3RlIiBzdHlsZT0ibWFy
Z2luOjBweCAwcHggMHB4IDAuOGV4O2JvcmRlci1sZWZ0LXdpZHRoOjFweDtib3JkZXItbGVmdC1j
b2xvcjpyZ2IoMjA0LDIwNCwyMDQpO2JvcmRlci1sZWZ0LXN0eWxlOnNvbGlkO3BhZGRpbmctbGVm
dDoxZXgiPjxkaXYgZGlyPSJsdHIiPjxkaXYgY2xhc3M9ImdtYWlsX2V4dHJhIj48ZGl2IGNsYXNz
PSJnbWFpbF9xdW90ZSI+DQo8ZGl2Pjxicj48L2Rpdj48ZGl2PkJUVywganVzdCBteSBvcGluaW9u
LCBidXQgJnF1b3Q7UmVhbG0tTG9jYWwmcXVvdDsgbWlnaHQgYmUgbW9yZSBtZWFuaW5nZnVsbHkg
bmFtZWQ8YnI+DQoNCjwvZGl2PjxkaXY+JnF1b3Q7TXVsdGlsaW5rLUxvY2FsJnF1b3Q7PC9kaXY+
PC9kaXY+PC9kaXY+PC9kaXY+PC9ibG9ja3F1b3RlPjxkaXY+Jmx0O1JDQyZndDsgSSBhZ3JlZSAt
IGl0IGlzIG1vcmUgbWVhbmluZ2Z1bCZsdDsvUkNDJmd0OyZuYnNwOzwvZGl2PjxibG9ja3F1b3Rl
IGNsYXNzPSJnbWFpbF9xdW90ZSIgc3R5bGU9Im1hcmdpbjowcHggMHB4IDBweCAwLjhleDtib3Jk
ZXItbGVmdC13aWR0aDoxcHg7Ym9yZGVyLWxlZnQtY29sb3I6cmdiKDIwNCwyMDQsMjA0KTtib3Jk
ZXItbGVmdC1zdHlsZTpzb2xpZDtwYWRkaW5nLWxlZnQ6MWV4Ij4NCjxkaXYgZGlyPSJsdHIiPjxk
aXYgY2xhc3M9ImdtYWlsX2V4dHJhIj48ZGl2IGNsYXNzPSJnbWFpbF9xdW90ZSI+PGRpdj48c3Bh
bj48Zm9udCBjb2xvcj0iIzg4ODg4OCI+PGJyPjxicj48L2ZvbnQ+PC9zcGFuPjwvZGl2PjxzcGFu
Pjxmb250IGNvbG9yPSIjODg4ODg4Ij48ZGl2Pi1LLTxicj48YnI+PC9kaXY+PGJsb2NrcXVvdGUg
Y2xhc3M9ImdtYWlsX3F1b3RlIiBzdHlsZT0ibWFyZ2luOjBweCAwcHggMHB4IDAuOGV4O2JvcmRl
ci1sZWZ0LXdpZHRoOjFweDtib3JkZXItbGVmdC1zdHlsZTpzb2xpZDtib3JkZXItbGVmdC1jb2xv
cjpyZ2IoMjA0LDIwNCwyMDQpO3BhZGRpbmctbGVmdDoxZXgiPg0KDQo8ZGl2PjxkaXY+DQoNCi0t
PGJyPg0KSklOTUVJLCBUYXR1eWE8YnI+DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTxicj4NCklFVEYgSVB2NiB3b3Jr
aW5nIGdyb3VwIG1haWxpbmcgbGlzdDxicj4NCjxhIGhyZWY9Im1haWx0bzppcHY2QGlldGYub3Jn
IiB0YXJnZXQ9Il9ibGFuayI+aXB2NkBpZXRmLm9yZzwvYT48YnI+DQpBZG1pbmlzdHJhdGl2ZSBS
ZXF1ZXN0czogPGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9p
cHY2IiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m
by9pcHY2PC9hPjxicj4NCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tPGJyPg0KPC9kaXY+PC9kaXY+PC9ibG9ja3F1b3Rl
PjwvZm9udD48L3NwYW4+PC9kaXY+PGJyPjwvZGl2PjwvZGl2Pg0KPGJyPl9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0KUm9sbCBtYWlsaW5nIGxpc3Q8
YnI+DQo8YSBocmVmPSJtYWlsdG86Um9sbEBpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPlJvbGxA
aWV0Zi5vcmc8L2E+PGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9yb2xsIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9yb2xsPC9hPjxicj4NCjxicj48L2Jsb2NrcXVvdGU+PC9kaXY+PGJyPjwvZGl2
PjwvZGl2Pg0K
--047d7b343dc46d717704e9772b07--

From jinmei.tatuya@gmail.com  Thu Oct 24 09:33:41 2013
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBA3811E8349; Thu, 24 Oct 2013 09:33:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.222
X-Spam-Level: *
X-Spam-Status: No, score=1.222 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eQxKRHf65PRT; Thu, 24 Oct 2013 09:33:41 -0700 (PDT)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) by ietfa.amsl.com (Postfix) with ESMTP id AF34011E8354; Thu, 24 Oct 2013 09:33:27 -0700 (PDT)
Received: by mail-wi0-f172.google.com with SMTP id ez12so9296169wid.11 for <multiple recipients>; Thu, 24 Oct 2013 09:33:26 -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=/Xsure6EPP6ZaggnBUeSTccXjIxk5/V7EsZX2JzgeNo=; b=uwaxIZ9LrKyPp720wcXBMBj5Z32gG0QNbLB4lEcotZBB/z0c148rFgKr07JoU1H6n6 VUKuBv7pR00KuVXB4ysvTrkR5b+i0TuCxOS9CXNwuSuPGlejTojZS/AZOeJ1C6gFv4UQ IjWk6I3W+hxDe2enPAitdlJ2S1YGe6awrGKFlQzEbwV3QsXlLRXFbKk6zaj21szyLWIQ inaCen39jSfPri8a8iIuOHLN7yguvEWS8qBf3UuTyM3cN7nAUgkYgWy+apCpB6Kr59/N 0ccVNRhCxDziIPvbdA+cozsnK5zK7FLQ8+vAoBj16uUboO73lLknsvJJvt5K4X6MvbvT RVww==
MIME-Version: 1.0
X-Received: by 10.180.37.134 with SMTP id y6mr2980128wij.48.1382632406615; Thu, 24 Oct 2013 09:33:26 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.120.167 with HTTP; Thu, 24 Oct 2013 09:33:26 -0700 (PDT)
In-Reply-To: <CABOxzu1VMw3EkCCkXRU4h=obSKbO8JSXfS+_NJ-S-vV3bkuP+g@mail.gmail.com>
References: <3599.1381852752@sandelman.ca> <CE82BA46.24343%d.sturek@att.net> <CABOxzu2nLuny5uySEEdb6ji9ucE6xqGZ6DLe-mc6KUqVszNfFg@mail.gmail.com> <525DC6C9.2010808@gridmerge.com> <CABOxzu2apwBRpU1h4mKJwpO+U+Y9Q_q-h5AhZ+hGzAdjdPdmUQ@mail.gmail.com> <525E5064.4050109@gridmerge.com> <CABOxzu0L-EY0iDGpAJ+ER15CPL-3v8F77ewn-G=gZYODixevZg@mail.gmail.com> <3CC8783F-F4DA-47B9-A051-DBBA6EF00C19@gmail.com> <CABOxzu1VMw3EkCCkXRU4h=obSKbO8JSXfS+_NJ-S-vV3bkuP+g@mail.gmail.com>
Date: Thu, 24 Oct 2013 09:33:26 -0700
X-Google-Sender-Auth: uLHtGhqykNJixU7pWi_AetJMmPY
Message-ID: <CAJE_bqes=hu4g4gVG5CrvStSMDy9ADHfuuxLsem3dBLM3v0YZQ@mail.gmail.com>
Subject: Re: [Roll] draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re: [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope value of 3 - subnet-local)
From: =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>
To: Kerry Lynn <kerlyn@ieee.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Routing Over Low power and Lossy networks <roll@ietf.org>, "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 24 Oct 2013 16:33:41 -0000

At Wed, 23 Oct 2013 17:38:07 -0400,
Kerry Lynn <kerlyn@ieee.org> wrote:

> > as follows:
> >
> >          Admin-Local scope is the smallest scope that must be
> >          administratively configured, i.e., not automatically derived
> >          from physical connectivity or other, non-multicast-related
> >          configuration.  For all non-reserved scopes except the global
> >          scope, the zone boundaries must also be administratively
> >          configured.
> >
> > I think this statement is self-contradictory.  When automatic
> configuration is
> discussed, it is in relation to zone boundaries.  Here's an attempt to

I'm not sure how it's self contradictory, but there was one clear
error: I meant "For all non-reserved scopes larger than admin-local
scope except the global scope".  But in any case,

> explain
> this without negations:
>
>     Interface-Local, Link-Local, and Realm-Local scope boundaries are
> automatically
>     derived from physical connectivity or other, non-multicast related
> configuration.
>     Global scope has no boundary.  The boundaries of all other non-reserved
> scopes
>     are administratively configured.

This one works for me, and, I actually don't have a strong opinion of
the wording or where to state it.

--
JINMEI, Tatuya

From mackermann@bcbsm.com  Thu Oct 24 09:52:18 2013
Return-Path: <mackermann@bcbsm.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E625511E8311 for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 09:52:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.057
X-Spam-Level: 
X-Spam-Status: No, score=-6.057 tagged_above=-999 required=5 tests=[AWL=-0.058, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vNs9ycmg7VdN for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 09:52:17 -0700 (PDT)
Received: from mx.z120.zixworks.com (mx.z120.zixworks.com [199.30.235.120]) by ietfa.amsl.com (Postfix) with ESMTP id 7953511E81A6 for <ipv6@ietf.org>; Thu, 24 Oct 2013 09:50:38 -0700 (PDT)
Received: from vmvpm02.z120.zixworks.com (ZixVPM [127.0.0.1]) by Outbound.z120.zixworks.com (Proprietary) with ESMTP id BD98A2FF69C for <ipv6@ietf.org>; Thu, 24 Oct 2013 11:50:17 -0500 (CDT)
Received: from imsva1.bcbsm.com (unknown [12.107.172.80]) by mx.z120.zixworks.com (Proprietary) with SMTP id A162830743A; Thu, 24 Oct 2013 11:50:16 -0500 (CDT)
Received: from imsva1.bcbsm.com (unknown [127.0.0.1]) by IMSVA80 (Postfix) with ESMTP id 4EDEE4F8051; Thu, 24 Oct 2013 12:40:02 -0400 (EDT)
Received: from PWN401EA110.ent.corp.bcbsm.com (unknown [10.64.80.218]) by imsva1.bcbsm.com (Postfix) with ESMTP id 2FEE74F805A; Thu, 24 Oct 2013 12:40:02 -0400 (EDT)
Received: from PWN401EA160.ent.corp.bcbsm.com ([fe80::fdcb:603d:469e:b1db]) by PWN401EA110.ent.corp.bcbsm.com ([fe80::716f:e3f0:b97f:8900%13]) with mapi id 14.01.0438.000; Thu, 24 Oct 2013 12:50:02 -0400
From: "Ackermann, Michael" <MAckermann@bcbsm.com>
To: Ray Hunter <v6ops@globis.net>, Nalini Elkins <nalini.elkins@insidethestack.com>
Subject: RE: [v6ops] Fw: New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-04.txt
Thread-Topic: [v6ops] Fw: New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-04.txt
Thread-Index: AQHOyuiEsp3P94CgjEaaXBige+0sO5n9xySAgAJIKwCAAHiqAIAChzTA
Date: Thu, 24 Oct 2013 16:50:01 +0000
Message-ID: <4FC37E442D05A748896589E468752CAA0CA88734@PWN401EA160.ent.corp.bcbsm.com>
References: <20131017032024.5051.20799.idtracker@ietfa.amsl.com> <1381980305.36254.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com> <5263C783.1080001@globis.net> <1382396300.22968.YahooMailNeo@web2801.biz.mail.ne1.yahoo.com> <526616C4.40304@globis.net>
In-Reply-To: <526616C4.40304@globis.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.64.10.35]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: v6ops WG <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 24 Oct 2013 16:52:18 -0000

Hi Ray.
And thanks again for all your insightful comments/questions.=20

I am a little late in responding, so let me just tack on a little to what =
Nalini and others have already said.=20

Your point 4 seems to indicate that all nodes in a desired time =
synchronization domain need to be synched to the same master clock.   This =
has not been my experience.   As long as the required Stratum level is =
realized, for the level of accuracy required by the situation or =
application, the proper level of time synchronization is achieved.   =
Example would be that if one node in the NTP domain is referencing a GPS =
Stratum 0 and another node is referencing a separate Stratum 0 source, the =
two nodes should be Stratum 1 and within that level of accuracy. =20
This is something we have implemented across several disparate enterprises =
and it has worked well for us.  I am wondering if your experience has =
yielded different results?

You also had two other points/questions, that I believe Nalini already =
responded to, but..............

1. The possibility that =22Middleboxes=22 could utilize PDM, is very =
intriguing to me.  I believe this would be more difficult to =
add/implement, but worth the effort if the Middlebox vendors would =
perceive value and actually use PDM.  Not sure how to determine if this =
would be the case or not?=20

2. It would be ideal to have only 1 PDM format that handles both time =
sycnronized and non synchronized situations.   I do not readily see how to =
achieve this.   Would love to talk to you some more if you have some =
ideas=21 =20

Again, thanks for your great input, thoughts and questions=21=21=21  (and =
hopefully more to come). =20

Mike





-----Original Message-----
From: v6ops-bounces=40ietf.org =5Bmailto:v6ops-bounces=40ietf.org=5D On =
Behalf Of Ray Hunter
Sent: Tuesday, October 22, 2013 2:10 AM
To: Nalini Elkins
Cc: v6ops WG; 6man WG; ippm=40ietf.org
Subject: Re: =5Bv6ops=5D Fw: New Version Notification for =
draft-elkins-6man-ipv6-pdm-dest-option-04.txt

> Nalini Elkins <mailto:nalini.elkins=40insidethestack.com>
> 22 October 2013 00:58
>>  1) encoding has to be fast, but decoding does not
>
> True
>
>>  2) a node's clock could be either in our out of synch with some=20
>> notional  master clock (e.g. via NTP)
>>  3) two clocks could be in synch to a master source, but the master =20
>> sources may themselves not share a common source (one sourced from=20
>> GPS, one from DCF77)
>> 4) the key to being able to perform the end to end calculations is=20
>> whether two communicating nodes are synchronised to the same master=20
>> clock (within some level of error/jitter)
>> 5) the absolute time is not particularly important
>
>
> This is true for PDM 1 only.  PDM 2 does not require time synchronization.
>
>>  Q1. Why do you want to encode differences as deltas in the case of an =
unsynchronised/ free running clock?
>>  Isn't that slow, and difficult for hardware implementations to achieve =
(e.g. TCP offload)? Doesn't it also require maintaining large amounts of =
state in the sending node.
>>
>
> 1. I think that it is going to be interesting to see how hardware is =
going to handle TCP offload with IPv6 extension headers.   I do not see =
why PDM 2 would be so much harder than PDM 1 for an OS.
> Can you tell me which end host operating systems are doing TCP offload =
in hardware?  =20
IMHO Not a relevant question. As a standards body we should be looking to =
the future. There are many operations that are delegated to microcode.

If you specified the packet with one single way of encapsulating =
timestamps, then hardware or interface microcode could add the timestamp =
at the last possible moment before the packet reached the wire, without =
having to examine the original packet contents, or knowing the context of =
the communicating nodes. I think that's very desirable.
> I know some OS's which process TCP segmentation in hardware.    But at =
this point, the packet is already crafted.  Also some do IP checksum =
offload in hardware but that does not apply to IPv6 as there is no IP =
header checksum.
>
>
> 2.  End hosts already maintain quite a bit of state.  Every OS has =
control blocks to handle events such as TCP duplicate packets, round trip =
time, congestion window, etc.   We are NOT suggesting
> that the PDM headers be used in middle boxes.  That is, we are NOT =
asking routers to maintain state.
So what? Why add to the problem?

Why does the timestamp require synchronisation with that other TCP state?

Isn't it better to define a solution that is independent of the upper =
layer header transport protocol?

<heresy>  Why not allow middleboxes (or node hardware) to insert the =
timestamp header on the fly?</heresy>
>
>>  Why not just encode the timestamp as-is and perform the appropriate =
difference calculation during decoding?
>
> If clocks are out of synch, you could end up having it look like you =
received the packet before you sent it.

No. I'm not suggesting you use the same decoding algorithm: only that you =
define a single common encoding algorithm that combines all the =
information required for PDM 1 and PDM 2 calculations. Having to chose =
which packet encoding to use in advance is problematic IMHO.



>>  Q2. Why do you need two separate packet formats at all?
>
>>  Why not have a common format for all cases, containing a timestamp=20
>> based on the local clock, plus an optional field containing a flag=20
>> that states if the local timestamp is coordinated to some master=20
>> clock, plus an identifier for the master clock.
>
>> You could then encode whether a node had a free-running clock (case=20
>> 2), a synchronised clock (case 1), and whether it was synched via NTP=20
>> to some stratum 0 source e.g. GPS, and also some identification of=20
>> the stratum 1 source (IPv6 address).
>
>> Two communicating nodes could then use e.g. NTP trace to see if they=20
>> shared a common clock source or not, before performing their =
calculations.
>
> We are trying to craft a solution with PDM 2 for those situations where =
time synchronization is not practical, possible or desired.

I understand the aim, but let me ask my question a different way.

Imagine there are nodes A&B that with clocks synched to DCF77.
Imagine there are nodes C&D that with clocks  synched to GPS.
Node E has free running clock (possibly because the GPS receiver is down).

Which packet format PDM type 1 or PDM type 2 do you use between each pair =
of nodes, and how does the sending node know that?

Scale this solution to 100K hosts.
>
> ----------------------------------------------------------------------
> --


--
Regards,
RayH

_______________________________________________
v6ops mailing list
v6ops=40ietf.org
https://www.ietf.org/mailman/listinfo/v6ops


The information contained in this communication is highly confidential and =
is intended solely for the use of the individual(s) to whom this =
communication is directed. If you are not the intended recipient, you are =
hereby notified that any viewing, copying, disclosure or distribution of =
this information is prohibited. Please notify the sender, by electronic =
mail or telephone, of any unintended receipt and delete the original =
message without making any copies.
=20
 Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are =
nonprofit corporations and independent licensees of the Blue Cross and =
Blue Shield Association.

From fernando@gont.com.ar  Thu Oct 24 10:53:21 2013
Return-Path: <fernando@gont.com.ar>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5014011E81CF for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 10:53:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tzY1SqpH7Qyq for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 10:53:20 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id A678C21E8093 for <6man@ietf.org>; Thu, 24 Oct 2013 10:51:01 -0700 (PDT)
Received: from 17-153-16-190.fibertel.com.ar ([190.16.153.17] helo=[192.168.1.170]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fernando@gont.com.ar>) id 1VZP3K-0001SL-4E; Thu, 24 Oct 2013 19:50:44 +0200
Message-ID: <52695DDE.70909@gont.com.ar>
Date: Thu, 24 Oct 2013 14:50:22 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: "6man@ietf.org" <6man@ietf.org>
Subject: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification for draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>
In-Reply-To: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.5.2
X-Forwarded-Message-Id: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: draft-gont-6man-deprecate-eui64-based-addresses@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 24 Oct 2013 17:53:21 -0000

Folks,

We have posted a new I-D entitled "Deprecating EUI-64 Based IPv6
Addresses"
(http://www.ietf.org/internet-drafts/draft-gont-6man-deprecate-eui64-based-addresses-00.txt).

It's a spin-off of the work we've been doing on IPv6 addressing
secuity/privacy considerations
(draft-ietf-6man-ipv6-address-generation-privacy and
draft-ietf-6man-stable-privacy-addresses), and the idea had already been
discussed among several folks mstly off-list and at IETF meeting corridors.

Any comments will be appreciated.

Thanks!

Best regards,
Fernando




-------- Original Message --------
Subject: New Version Notification for
draft-gont-6man-deprecate-eui64-based-addresses-00.txt
Date: Mon, 21 Oct 2013 15:43:46 -0700
From: internet-drafts@ietf.org
To: Fernando Gont <fgont@si6networks.com>, Will Liu
<liushucheng@huawei.com>, Alissa Cooper <acooper@cdt.org>, Dave Thaler
<dthaler@microsoft.com>


A new version of I-D, draft-gont-6man-deprecate-eui64-based-addresses-00.txt
has been successfully submitted by Fernando Gont and posted to the
IETF repository.

Filename:	 draft-gont-6man-deprecate-eui64-based-addresses
Revision:	 00
Title:		 Deprecating EUI-64 Based IPv6 Addresses
Creation date:	 2013-10-22
Group:		 Individual Submission
Number of pages: 6
URL:
http://www.ietf.org/internet-drafts/draft-gont-6man-deprecate-eui64-based-addresses-00.txt
Status:
http://datatracker.ietf.org/doc/draft-gont-6man-deprecate-eui64-based-addresses
Htmlized:
http://tools.ietf.org/html/draft-gont-6man-deprecate-eui64-based-addresses-00


Abstract:
   Stateless Address Autoconfiguration (SLAAC) for IPv6 typically
   results in hosts configuring one or more stable addresses composed of
   a network prefix advertised by a local router, and an Interface
   Identifier that typically embeds a hardware address (e.g., an IEEE
   LAN MAC address).  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 scheme to mitigate these issues.
   This document deprecates the use of hardware addresses in IPv6
   Interface Identifiers, and recommends the use of an alternative
   scheme ([I-D.ietf-6man-stable-privacy-addresses]) for the generation
   of IPv6 stable addresses.





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





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




From v6ops@globis.net  Thu Oct 24 10:53:45 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE93211E8389; Thu, 24 Oct 2013 10:53:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lhAtgmm-MqFl; Thu, 24 Oct 2013 10:53:44 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 0758C21E809F; Thu, 24 Oct 2013 10:52:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 08B7F8700B3; Thu, 24 Oct 2013 19:51:56 +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 7ZEcBsCHet+2; Thu, 24 Oct 2013 19:51:55 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id CED81870056; Thu, 24 Oct 2013 19:51:55 +0200 (CEST)
Message-ID: <52695E3A.9090406@globis.net>
Date: Thu, 24 Oct 2013 19:51:54 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: "Ackermann, Michael" <MAckermann@bcbsm.com>
Subject: Re: [v6ops] Fw: New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-04.txt
References: <20131017032024.5051.20799.idtracker@ietfa.amsl.com> <1381980305.36254.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com> <5263C783.1080001@globis.net> <1382396300.22968.YahooMailNeo@web2801.biz.mail.ne1.yahoo.com> <526616C4.40304@globis.net> <4FC37E442D05A748896589E468752CAA0CA88734@PWN401EA160.ent.corp.bcbsm.com>
In-Reply-To: <4FC37E442D05A748896589E468752CAA0CA88734@PWN401EA160.ent.corp.bcbsm.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: v6ops WG <v6ops@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 24 Oct 2013 17:53:46 -0000

> Ackermann, Michael <mailto:MAckermann@bcbsm.com>
> 24 October 2013 18:50
> Hi Ray.
> And thanks again for all your insightful comments/questions. 
>
> I am a little late in responding, so let me just tack on a little to what Nalini and others have already said. 
>
> Your point 4 seems to indicate that all nodes in a desired time synchronization domain need to be synched to the same master clock. 
No. I think what I said was that the level of certainty in your
measurements is dependent on the level of synchronisation of the 2 clock
sources if you are calculating a delta of timestamp of clock 1 -
timestamp clock 2.

I think it might be instructive to go back and look at high school
physics books on making measurements, precision, accuracy, and error
estimations, especially when taking the difference of two measurements,
or making other calculations on top of raw observations.

For example, as far as I know, DFC-77 is not compensated for speed of
light travel time from Frankfurt: that is a manual offset. So even if
two nodes using DCF-77 that are geographically spread across Europe are
perfectly synchronised to the incoming radio signal, they might have a
constant offset compared to the "absolute" time in Frankfurt. That may
or may not have an effect on one way trip measurement times you measure,
depending on how you perform your calculations.

I think this link might be instructive.
http://www.hopf.com/en/dcf77-gps_en.html

Equally a stratum 0 clock can be free running if it loses it's radio signal.

I see time stamps in the picosecond range defined in the protocol, and
errors on DCF-77 of up to 150mS...... completely different orders of
magnitude of precision.


>   This has not been my experience.   As long as the required Stratum level is realized, for the level of accuracy required by the situation or application, the proper level of time synchronization is achieved.   Example would be that if one node in the NTP domain is referencing a GPS Stratum 0 and another node is referencing a separate Stratum 0 source, the two nodes should be Stratum 1 and within that level of accuracy.  
> This is something we have implemented across several disparate enterprises and it has worked well for us.  I am wondering if your experience has yielded different results?
Absolutely. Different NTP servers are not guaranteed to be synched to
each other. They're close. But not in the picosecond range.
> You also had two other points/questions, that I believe Nalini already responded to, but..............
>
> 1. The possibility that "Middleboxes" could utilize PDM, is very intriguing to me.  I believe this would be more difficult to add/implement, but worth the effort if the Middlebox vendors would perceive value and actually use PDM.  Not sure how to determine if this would be the case or not? 

Why would it be difficult? If you can define the encoder in your
protocol in terms of absolute local timestamps only, plus a provenance
of the clock used for the timestamp, it would be a simple matter of
inserting an additional destination header into every forwarded packet
when the middlebox forwards it.
> 2. It would be ideal to have only 1 PDM format that handles both time sycnronized and non synchronized situations.   I do not readily see how to achieve this.   Would love to talk to you some more if you have some ideas!  
Well for example, PDM 2 uses a local delta for the last packet
transmission time: DELTALS.

IMHO If you know absolute timestamp 1 of clock 1 @ last packet n sent
from node 1, and absolute timestamp 2 of clock 1 @ last packet n+1 sent
from node 1, I see it as a trivial matter to calculate the delta time
between sending packet n and sending packet n+1 remotely at a decoder at
a remote location (as observed at node 1), which will be identical to
DELTALS, rather than calculating this value locally in the transmitting
node 1 before sending the packet. [you can only encode this DELTALS
value in packet 2.. anyway]

I suspect the step that you are missing is coupling a timestamp to a
clock and a packet ID and an event, and specifying only two timestamps
in the packet, rather than both nodes timestamping the same events with
their respective local clocks.

You could also have timestamps for last received n from node 2 based on
clock 1 sent in replies to packet n by node 1, and last received n+1
from node 2 based on clock1 sent in replies to packet n+1 by node 1, so
that you can calculate DELTALR remotely too (as observed at the location
of the receiving node 1). That way you avoid the need to calculate delta
locally, or any need to track sessions in the transmitter (so that you
can calculate a delta in the transmitter). You do obviously have to
calculate a delta and track sessions in the decoder, but that is not
time critical, and also can be applied to a subset of all traffic.
>
> Again, thanks for your great input, thoughts and questions!!!  (and hopefully more to come).  
>
> Mike
>
It seems to me that what you are essentially doing with this protocol is
largely what NTP does anyway.

So examining the NTP RFC might give you tips on what timestamps you
need. And equally, since you are going to be sending high bandwidth
synch traffic between 2 nodes, you might want to consider feeding the
results back into NTP to see if you can improve the clock
synchronisation between measuring nodes.

-- 
Regards,
RayH


From joelja@bogus.com  Thu Oct 24 11:14:50 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85EE311E81C5; Thu, 24 Oct 2013 11:14:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.431
X-Spam-Level: 
X-Spam-Status: No, score=-102.431 tagged_above=-999 required=5 tests=[AWL=-0.432, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VBs8g+YIrVom; Thu, 24 Oct 2013 11:14:49 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 621D811E8200; Thu, 24 Oct 2013 11:14:47 -0700 (PDT)
Received: from 00698a-hsutim.corp.zynga.com ([199.48.105.4]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r9OIEeJu029937 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 24 Oct 2013 18:14:42 GMT (envelope-from joelja@bogus.com)
Content-Type: multipart/signed; boundary="Apple-Mail=_4C19CD7E-9716-48FB-A56B-DCFF30077490"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Subject: Re: [v6ops] New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-04.txt
From: joel jaeggli <joelja@bogus.com>
In-Reply-To: <4FC37E442D05A748896589E468752CAA0CA88734@PWN401EA160.ent.corp.bcbsm.com>
Date: Thu, 24 Oct 2013 11:14:35 -0700
Message-Id: <585D21EB-BD17-40C7-9C31-67F12EC6712F@bogus.com>
References: <20131017032024.5051.20799.idtracker@ietfa.amsl.com> <1381980305.36254.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com> <5263C783.1080001@globis.net> <1382396300.22968.YahooMailNeo@web2801.biz.mail.ne1.yahoo.com> <526616C4.40304@globis.net> <4FC37E442D05A748896589E468752CAA0CA88734@PWN401EA160.ent.corp.bcbsm.com>
To: "Ackermann, Michael" <MAckermann@bcbsm.com>
X-Mailer: Apple Mail (2.1816)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Thu, 24 Oct 2013 18:14:43 +0000 (UTC)
Cc: Ray Hunter <v6ops@globis.net>, v6ops WG <v6ops@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 24 Oct 2013 18:14:50 -0000

--Apple-Mail=_4C19CD7E-9716-48FB-A56B-DCFF30077490
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Oct 24, 2013, at 9:50 AM, Ackermann, Michael <MAckermann@bcbsm.com> =
wrote:

> Hi Ray.
> And thanks again for all your insightful comments/questions.=20
>=20
> I am a little late in responding, so let me just tack on a little to =
what Nalini and others have already said.=20
>=20
> Your point 4 seems to indicate that all nodes in a desired time =
synchronization domain need to be synched to the same master clock.   =
This has not been my experience.   As long as the required Stratum level =
is realized, for the level of accuracy required by the situation or =
application, the proper level of time synchronization is achieved.   =
Example would be that if one node in the NTP domain is referencing a GPS =
Stratum 0 and another node is referencing a separate Stratum 0 source, =
the two nodes should be Stratum 1 and within that level of accuracy. =20

stratum is not an indication of either precision or accuracy it=92s an =
inidication of a position within the NTP heirachary.

> This is something we have implemented across several disparate =
enterprises and it has worked well for us.  I am wondering if your =
experience has yielded different results?
>=20
> You also had two other points/questions, that I believe Nalini already =
responded to, but..............
>=20
> 1. The possibility that "Middleboxes" could utilize PDM, is very =
intriguing to me.  I believe this would be more difficult to =
add/implement, but worth the effort if the Middlebox vendors would =
perceive value and actually use PDM.  Not sure how to determine if this =
would be the case or not?=20
>=20
> 2. It would be ideal to have only 1 PDM format that handles both time =
sycnronized and non synchronized situations.   I do not readily see how =
to achieve this.   Would love to talk to you some more if you have some =
ideas! =20
>=20
> Again, thanks for your great input, thoughts and questions!!!  (and =
hopefully more to come). =20
>=20
> Mike
>=20
>=20
>=20
>=20
>=20
> -----Original Message-----
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf =
Of Ray Hunter
> Sent: Tuesday, October 22, 2013 2:10 AM
> To: Nalini Elkins
> Cc: v6ops WG; 6man WG; ippm@ietf.org
> Subject: Re: [v6ops] Fw: New Version Notification for =
draft-elkins-6man-ipv6-pdm-dest-option-04.txt
>=20
>> Nalini Elkins <mailto:nalini.elkins@insidethestack.com>
>> 22 October 2013 00:58
>>> 1) encoding has to be fast, but decoding does not
>>=20
>> True
>>=20
>>> 2) a node's clock could be either in our out of synch with some=20
>>> notional  master clock (e.g. via NTP)
>>> 3) two clocks could be in synch to a master source, but the master =20=

>>> sources may themselves not share a common source (one sourced from=20=

>>> GPS, one from DCF77)
>>> 4) the key to being able to perform the end to end calculations is=20=

>>> whether two communicating nodes are synchronised to the same master=20=

>>> clock (within some level of error/jitter)
>>> 5) the absolute time is not particularly important
>>=20
>>=20
>> This is true for PDM 1 only.  PDM 2 does not require time =
synchronization.
>>=20
>>> Q1. Why do you want to encode differences as deltas in the case of =
an unsynchronised/ free running clock?
>>> Isn't that slow, and difficult for hardware implementations to =
achieve (e.g. TCP offload)? Doesn't it also require maintaining large =
amounts of state in the sending node.
>>>=20
>>=20
>> 1. I think that it is going to be interesting to see how hardware is =
going to handle TCP offload with IPv6 extension headers.   I do not see =
why PDM 2 would be so much harder than PDM 1 for an OS.
>> Can you tell me which end host operating systems are doing TCP =
offload in hardware?  =20
> IMHO Not a relevant question. As a standards body we should be looking =
to the future. There are many operations that are delegated to =
microcode.
>=20
> If you specified the packet with one single way of encapsulating =
timestamps, then hardware or interface microcode could add the timestamp =
at the last possible moment before the packet reached the wire, without =
having to examine the original packet contents, or knowing the context =
of the communicating nodes. I think that's very desirable.
>> I know some OS's which process TCP segmentation in hardware.    But =
at this point, the packet is already crafted.  Also some do IP checksum =
offload in hardware but that does not apply to IPv6 as there is no IP =
header checksum.
>>=20
>>=20
>> 2.  End hosts already maintain quite a bit of state.  Every OS has =
control blocks to handle events such as TCP duplicate packets, round =
trip time, congestion window, etc.   We are NOT suggesting
>> that the PDM headers be used in middle boxes.  That is, we are NOT =
asking routers to maintain state.
> So what? Why add to the problem?
>=20
> Why does the timestamp require synchronisation with that other TCP =
state?
>=20
> Isn't it better to define a solution that is independent of the upper =
layer header transport protocol?
>=20
> <heresy>  Why not allow middleboxes (or node hardware) to insert the =
timestamp header on the fly?</heresy>
>>=20
>>> Why not just encode the timestamp as-is and perform the appropriate =
difference calculation during decoding?
>>=20
>> If clocks are out of synch, you could end up having it look like you =
received the packet before you sent it.
>=20
> No. I'm not suggesting you use the same decoding algorithm: only that =
you define a single common encoding algorithm that combines all the =
information required for PDM 1 and PDM 2 calculations. Having to chose =
which packet encoding to use in advance is problematic IMHO.
>=20
>=20
>=20
>>> Q2. Why do you need two separate packet formats at all?
>>=20
>>> Why not have a common format for all cases, containing a timestamp=20=

>>> based on the local clock, plus an optional field containing a flag=20=

>>> that states if the local timestamp is coordinated to some master=20
>>> clock, plus an identifier for the master clock.
>>=20
>>> You could then encode whether a node had a free-running clock (case=20=

>>> 2), a synchronised clock (case 1), and whether it was synched via =
NTP=20
>>> to some stratum 0 source e.g. GPS, and also some identification of=20=

>>> the stratum 1 source (IPv6 address).
>>=20
>>> Two communicating nodes could then use e.g. NTP trace to see if they=20=

>>> shared a common clock source or not, before performing their =
calculations.
>>=20
>> We are trying to craft a solution with PDM 2 for those situations =
where time synchronization is not practical, possible or desired.
>=20
> I understand the aim, but let me ask my question a different way.
>=20
> Imagine there are nodes A&B that with clocks synched to DCF77.
> Imagine there are nodes C&D that with clocks  synched to GPS.
> Node E has free running clock (possibly because the GPS receiver is =
down).
>=20
> Which packet format PDM type 1 or PDM type 2 do you use between each =
pair of nodes, and how does the sending node know that?
>=20
> Scale this solution to 100K hosts.
>>=20
>> =
----------------------------------------------------------------------
>> --
>=20
>=20
> --
> Regards,
> RayH
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>=20
>=20
> The information contained in this communication is highly confidential =
and is intended solely for the use of the individual(s) to whom this =
communication is directed. If you are not the intended recipient, you =
are hereby notified that any viewing, copying, disclosure or =
distribution of this information is prohibited. Please notify the =
sender, by electronic mail or telephone, of any unintended receipt and =
delete the original message without making any copies.
>=20
> Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan =
are nonprofit corporations and independent licensees of the Blue Cross =
and Blue Shield Association.
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20


--Apple-Mail=_4C19CD7E-9716-48FB-A56B-DCFF30077490
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 - http://gpgtools.org

iEYEARECAAYFAlJpY4sACgkQ8AA1q7Z/VrKo/wCcDK5BXwTKRrJAadowt4znf186
rTgAnR/PcdhLLw8rsgOOhnTmlYlYh58I
=5W5c
-----END PGP SIGNATURE-----

--Apple-Mail=_4C19CD7E-9716-48FB-A56B-DCFF30077490--

From ietf@rozanak.com  Thu Oct 24 11:23:02 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 785AB11E8194 for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 11:23:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vxx7xvdrGvKE for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 11:22:57 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id 1716A11E81E4 for <ipv6@ietf.org>; Thu, 24 Oct 2013 11:22:57 -0700 (PDT)
Received: from kopoli ([193.43.158.234]) by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis) id 0LfCG8-1W28f62FdQ-00omdY; Thu, 24 Oct 2013 14:22:24 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: "'Fernando Gont'" <fernando@gont.com.ar>, "Alissa Cooper" <acooper@cdt.org>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar>
In-Reply-To: <52695DDE.70909@gont.com.ar>
Subject: RE: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification	for draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
Date: Thu, 24 Oct 2013 20:22:16 +0200
Message-ID: <001101ced0e5$fc380120$f4a80360$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJdGpkKhBNwQmPgs6BLyJ03nfzI7QLvxViamNAWRbA=
Content-Language: en-us
X-Provags-ID: V02:K0:2OdzPr4pxm53+LgRKdd5n/cIAa+wkVGUGQlNFVMWtkP /f584HbaIZFyoPu6uvjiOPx2Vu2F+lsoLCj24QxMjgQaQCacB5 jchb7O3WIefobW6fim5xhhJmdPiQLARANxpo1sOJUDHcfW133i lSrWWcBhSAh/dlGVhkQrLs3Xwdlm6Ugw3uejHKfUu4SgNS1YFr NJ7O3tU3TRhRALQgqUhVsaVIaLUj1W/35Pim4MKdTVGHZxdoFb CL+mLGdlqc6XKMym1uQUVnaFQUkjSMa/WbOqFnrRT38jU/PBkb 2qSEnPZx7joFuNo9IUH8+UjXsXZbwdjAi5lxjq2yOjQsoHnSJu rShLa5raiyIW8tT6rpiY=
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 24 Oct 2013 18:23:02 -0000

Hi,

I guess you also included the section regarding ra-privacy draft in this
draft.  Are you going to merge my draft with yours? 

@Alissia: Did I missed something? I guess we discussed to keep this in my
draft (the email that Ole and others were also included)

I am not totally disagree with deprecating the use of EUI-64 but I would
like to clarify the status of my draft that was active for some months.
Thanks,

-----------smile----------
Hosnieh
. success is a journey, not a destination..
You cannot change your destination overnight, but you can change your
direction ... Focus on the journey


-----Original Message-----
From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
Fernando Gont
Sent: Thursday, October 24, 2013 7:50 PM
To: 6man@ietf.org
Cc: draft-gont-6man-deprecate-eui64-based-addresses@tools.ietf.org
Subject: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version
Notification for draft-gont-6man-deprecate-eui64-based-addresses-00.txt)

Folks,

We have posted a new I-D entitled "Deprecating EUI-64 Based IPv6 Addresses"
(http://www.ietf.org/internet-drafts/draft-gont-6man-deprecate-eui64-based-a
ddresses-00.txt).

It's a spin-off of the work we've been doing on IPv6 addressing
secuity/privacy considerations
(draft-ietf-6man-ipv6-address-generation-privacy and
draft-ietf-6man-stable-privacy-addresses), and the idea had already been
discussed among several folks mstly off-list and at IETF meeting corridors.

Any comments will be appreciated.

Thanks!

Best regards,
Fernando




-------- Original Message --------
Subject: New Version Notification for
draft-gont-6man-deprecate-eui64-based-addresses-00.txt
Date: Mon, 21 Oct 2013 15:43:46 -0700
From: internet-drafts@ietf.org
To: Fernando Gont <fgont@si6networks.com>, Will Liu
<liushucheng@huawei.com>, Alissa Cooper <acooper@cdt.org>, Dave Thaler
<dthaler@microsoft.com>


A new version of I-D, draft-gont-6man-deprecate-eui64-based-addresses-00.txt
has been successfully submitted by Fernando Gont and posted to the IETF
repository.

Filename:	 draft-gont-6man-deprecate-eui64-based-addresses
Revision:	 00
Title:		 Deprecating EUI-64 Based IPv6 Addresses
Creation date:	 2013-10-22
Group:		 Individual Submission
Number of pages: 6
URL:
http://www.ietf.org/internet-drafts/draft-gont-6man-deprecate-eui64-based-ad
dresses-00.txt
Status:
http://datatracker.ietf.org/doc/draft-gont-6man-deprecate-eui64-based-addres
ses
Htmlized:
http://tools.ietf.org/html/draft-gont-6man-deprecate-eui64-based-addresses-0
0


Abstract:
   Stateless Address Autoconfiguration (SLAAC) for IPv6 typically
   results in hosts configuring one or more stable addresses composed of
   a network prefix advertised by a local router, and an Interface
   Identifier that typically embeds a hardware address (e.g., an IEEE
   LAN MAC address).  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 scheme to mitigate these issues.
   This document deprecates the use of hardware addresses in IPv6
   Interface Identifiers, and recommends the use of an alternative
   scheme ([I-D.ietf-6man-stable-privacy-addresses]) for the generation
   of IPv6 stable addresses.





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





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



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


From brian.e.carpenter@gmail.com  Thu Oct 24 12:59:42 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DC5E11E838E for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 12:59:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.533
X-Spam-Level: 
X-Spam-Status: No, score=-102.533 tagged_above=-999 required=5 tests=[AWL=0.066, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NjIqOxsEuXCS for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 12:59:41 -0700 (PDT)
Received: from mail-pd0-x22b.google.com (mail-pd0-x22b.google.com [IPv6:2607:f8b0:400e:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 3811D11E82F8 for <ipv6@ietf.org>; Thu, 24 Oct 2013 12:59:39 -0700 (PDT)
Received: by mail-pd0-f171.google.com with SMTP id w10so1109010pde.2 for <ipv6@ietf.org>; Thu, 24 Oct 2013 12:59:39 -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=JL8C/0VxppvcAA35+F0UYxmJCxuJIuNM4c5+VM9PgZ8=; b=0EmnkW2wUwLHdDLjK8vlQj6YkmqhmKNS+44cZRUR0c6sK5JKOpIuLTq27HFkAOyXDS qWfxRHVOuuB/q8n7UNDN/ZXAYfizEwwASrdLYm/cSN7JMA7s6dSKUNvlNm/EdX1WfB+z dda0skDlBCXrYwTVcQxJ/DN5CAU+iQXXU15e8Pj4yxFRQKVjsHEjDGm9sySTZT/uoG7G D4artZd1eOGtkBo/aGD/bxr6ijlLdEoNdWVUmfqrT7kXbu1GrEKNDw0zoNWIcd8s5UUE ihoL47OxgExCNqFFmt3GSSUblQtKy+ue+ZCwVaUfexHvX8l5MrKdaYjueZMtPgRJD+/q XFaA==
X-Received: by 10.66.230.233 with SMTP id tb9mr5109250pac.38.1382644778906; Thu, 24 Oct 2013 12:59:38 -0700 (PDT)
Received: from [192.168.178.20] (181.196.69.111.dynamic.snap.net.nz. [111.69.196.181]) by mx.google.com with ESMTPSA id q4sm4506598pba.12.2013.10.24.12.59.37 for <ipv6@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 24 Oct 2013 12:59:38 -0700 (PDT)
Message-ID: <52697C33.7010904@gmail.com>
Date: Fri, 25 Oct 2013 08:59:47 +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-gont-6man-deprecate-eui64-based-addresses-00.txt
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com>
In-Reply-To: <20131021224345.32495.19727.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 24 Oct 2013 19:59:42 -0000

Unfortunately I feel that this is operationally unacceptable.

There are many (I suppose thousands) of sites that rely on MAC
addresses to manage their assets, and in many cases to trace
malicious users. It's certainly true that in theory, they can do
this by using ND or DHCPv6 logging, as today they use ARP cache
or DHCP logging to trace IPv4 users, and they may have to do this
anyway when some users implement some form of obscure IID generation.
But I just don't see site managers in general (and therefore vendors)
accepting this:

"Nodes MUST NOT employ IPv6 address generation schemes that embed the
 underlying hardware address in the Interface Identifier."

I would suggest that this might fly:

"Nodes SHOULD NOT employ IPv6 address generation schemes that embed the
 underlying hardware address in the Interface Identifier, and such schemes
 MUST NOT be enabled by default in any implementation."

Even that might prove unrealistic.

Incidentally, your case would be strengthened by referring to
draft-ietf-6man-ug, which makes it plain that the case for EUI64
is weaker than was originally thought.

   Brian

From brian.e.carpenter@gmail.com  Thu Oct 24 14:38:52 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E618411E81F8 for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 14:38:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.534
X-Spam-Level: 
X-Spam-Status: No, score=-102.534 tagged_above=-999 required=5 tests=[AWL=0.065, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G-udPu+cSqZz for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 14:38:50 -0700 (PDT)
Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 40E9111E823C for <ipv6@ietf.org>; Thu, 24 Oct 2013 14:38:48 -0700 (PDT)
Received: by mail-pa0-f45.google.com with SMTP id kp14so2796615pab.32 for <ipv6@ietf.org>; Thu, 24 Oct 2013 14:38:48 -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=tlHncdQTRKBLzSQQgwPGEGit8inaJp6ei3j00I1YVBM=; b=vuJ1fFTtLghJtxNARRvb9rDFfpfNpF7Ubejw/5wClbwk3lz+F274XX+MTy1OkHjTx6 G4uGM5qt8Ut22qWGjZoDlFIuVhYebSgyZky/6rkIwfMqDot1hDHJBsHPn+6U8WY37ONz TM6j1QHwVpeVt3BqdgtAht/JvrivWw0QuAYOpC4qXvFC3OO/XDgBM6dkDlDDqg1M6LHX Aa3R2qppyV1NgHMpkCHoQQqUPAsoigLdlO94VQw5pwTWZ0ioUS89gvbfC7Qf2oe4mUgA 2/07+ws9YQE1HchZ2LJaYfX3JLsdN3fB6ZtLJbiR9Dp/P6bOYyPBmGE5nVs8SnYiafJK o4dg==
X-Received: by 10.68.52.231 with SMTP id w7mr4944869pbo.19.1382650728062; Thu, 24 Oct 2013 14:38:48 -0700 (PDT)
Received: from [192.168.178.20] (181.196.69.111.dynamic.snap.net.nz. [111.69.196.181]) by mx.google.com with ESMTPSA id og5sm4820645pbb.10.2013.10.24.14.38.45 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 24 Oct 2013 14:38:47 -0700 (PDT)
Message-ID: <5269936F.7020705@gmail.com>
Date: Fri, 25 Oct 2013 10:38:55 +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: John Day <jeanjour@comcast.net>
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com> <52697C33.7010904@gmail.com> <a06240804ce8f365bd832@[10.0.1.3]>
In-Reply-To: <a06240804ce8f365bd832@[10.0.1.3]>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 24 Oct 2013 21:38:53 -0000

On 25/10/2013 09:58, John Day wrote:
> I couldn't agree with you more, Brian.   This is a really bad idea.
> 
>  "Government" should not be trying to protect us from ourselves! (Did I
> hear that on Fox News or was it Rush Limbaugh?)  This is not the proper
> kind of constraints for the IETF to be imposing. Information wants to be
> free!  If some operations manager wants to improve the ability of others
> to trace his traffic and spy on the people in his network, he should be
> allowed to do it.
> 
> As for tracing malicious users, that is a bit like the argument that if
> guns are outlawed only outlaws will have guns. Only in this case, if we
> don't outlaw it only the clueless will use MAC Addresses as endpoint
> ids, the "outlaws" aren't that dumb.  I really doubt they would use
> their own MAC addresses, or even to use the same one for very long.

In some contexts that doesn't matter. For example, at the university
where I currently work, a student can sit at any one of a few thousand
workstations - the security people need a way to track back malicious
traffic to a specific login session. The MAC address is definitely part
of the tracking process, even if the student is long gone.

    Brian

> Take care,
> John Day
> 
> At 8:59 AM +1300 10/25/13, Brian E Carpenter wrote:
>> Unfortunately I feel that this is operationally unacceptable.
>>
>> There are many (I suppose thousands) of sites that rely on MAC
>> addresses to manage their assets, and in many cases to trace
>> malicious users. It's certainly true that in theory, they can do
>> this by using ND or DHCPv6 logging, as today they use ARP cache
>> or DHCP logging to trace IPv4 users, and they may have to do this
>> anyway when some users implement some form of obscure IID generation.
>> But I just don't see site managers in general (and therefore vendors)
>> accepting this:
>>
>> "Nodes MUST NOT employ IPv6 address generation schemes that embed the
>>  underlying hardware address in the Interface Identifier."
>>
>> I would suggest that this might fly:
>>
>> "Nodes SHOULD NOT employ IPv6 address generation schemes that embed the
>>  underlying hardware address in the Interface Identifier, and such
>> schemes
>>  MUST NOT be enabled by default in any implementation."
>>
>> Even that might prove unrealistic.
>>
>> Incidentally, your case would be strengthened by referring to
>> draft-ietf-6man-ug, which makes it plain that the case for EUI64
>> is weaker than was originally thought.
>>
>>    Brian
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
> 
> 

From tjc@ecs.soton.ac.uk  Thu Oct 24 15:01:41 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFCB411E820E for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 15:01:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZX6IzN+3-YuH for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 15:01:40 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id DFD4411E824A for <ipv6@ietf.org>; Thu, 24 Oct 2013 15:01:39 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r9OM1Vo6028307; Thu, 24 Oct 2013 23:01:31 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r9OM1Vo6028307
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1382652091; bh=v83zI+mkkIq0I+xZQik/PbJzmbA=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=kMppw7VqPWIdtqQ0esxj5nUnRd8AoUeDynbNIZ5QDieeAK90s45LTuNP4OnqF86Tk /pKmQLrzr8Lhe8O8XNBk39zInsgz8MnW4ZuW003NOmbrRIA3Arm3dIZ6d2sKnjm7DC vWFVv4fiDQLsNX4YCZEn8U2171IpzZnXFLV7zyIc=
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 p9NN1V0959662971J2 ret-id none; Thu, 24 Oct 2013 23:01:31 +0100
Received: from [192.168.1.108] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r9OM0hGA025664 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 24 Oct 2013 23:01:28 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <5269936F.7020705@gmail.com>
Date: Thu, 24 Oct 2013 23:01:28 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|caa096f62332b0b87f0053a710e89364p9NN1V03tjc|ecs.soton.ac.uk|E9BB1094-64E9-4219-B801-7205D2B0A1E4@ecs.soton.ac.uk>
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com> <52697C33.7010904@gmail.com> <a06240804ce8f365bd832@[10.0.1.3]> <5269936F.7020705@gmail.com> <E9BB1094-64E9-4219-B801-7205D2B0A1E4@ecs.soton.ac.uk>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1510)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p9NN1V095966297100; tid=p9NN1V0959662971J2; 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: r9OM1Vo6028307
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: 6man <ipv6@ietf.org>, John Day <jeanjour@comcast.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 24 Oct 2013 22:01:42 -0000

On 24 Oct 2013, at 22:38, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

> On 25/10/2013 09:58, John Day wrote:
>> I couldn't agree with you more, Brian.   This is a really bad idea.
>>=20
>> "Government" should not be trying to protect us from ourselves! (Did =
I
>> hear that on Fox News or was it Rush Limbaugh?)  This is not the =
proper
>> kind of constraints for the IETF to be imposing. Information wants to =
be
>> free!  If some operations manager wants to improve the ability of =
others
>> to trace his traffic and spy on the people in his network, he should =
be
>> allowed to do it.
>>=20
>> As for tracing malicious users, that is a bit like the argument that =
if
>> guns are outlawed only outlaws will have guns. Only in this case, if =
we
>> don't outlaw it only the clueless will use MAC Addresses as endpoint
>> ids, the "outlaws" aren't that dumb.  I really doubt they would use
>> their own MAC addresses, or even to use the same one for very long.
>=20
> In some contexts that doesn't matter. For example, at the university
> where I currently work, a student can sit at any one of a few thousand
> workstations - the security people need a way to track back malicious
> traffic to a specific login session. The MAC address is definitely =
part
> of the tracking process, even if the student is long gone.

But it's part of the tracking at the Ethernet layer, not the IP layer. =
There is no need at all to include the MAC address in the IP address for =
accountability purposes.=20

Tim


From mackermann@bcbsm.com  Thu Oct 24 16:45:15 2013
Return-Path: <mackermann@bcbsm.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CE5411E8269 for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 16:45:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.048
X-Spam-Level: 
X-Spam-Status: No, score=-6.048 tagged_above=-999 required=5 tests=[AWL=-0.049, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EzBEm0dHfL2G for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 16:45:09 -0700 (PDT)
Received: from mx.z120.zixworks.com (mx.z120.zixworks.com [199.30.235.120]) by ietfa.amsl.com (Postfix) with ESMTP id B17C611E825F for <ipv6@ietf.org>; Thu, 24 Oct 2013 16:45:08 -0700 (PDT)
Received: from vmvpm01.z120.zixworks.com (ZixVPM [127.0.0.1]) by Outbound.z120.zixworks.com (Proprietary) with ESMTP id 2386A9AD9F8 for <ipv6@ietf.org>; Thu, 24 Oct 2013 18:45:08 -0500 (CDT)
Received: from imsva1.bcbsm.com (unknown [12.107.172.80]) by mx.z120.zixworks.com (Proprietary) with SMTP id EC5BF9AD9E9; Thu, 24 Oct 2013 18:45:06 -0500 (CDT)
Received: from imsva1.bcbsm.com (unknown [127.0.0.1]) by IMSVA80 (Postfix) with ESMTP id DEE554F804D; Thu, 24 Oct 2013 19:34:51 -0400 (EDT)
Received: from pwn401ea100.ent.corp.bcbsm.com (unknown [10.64.80.217]) by imsva1.bcbsm.com (Postfix) with ESMTP id D10194F8049; Thu, 24 Oct 2013 19:34:51 -0400 (EDT)
Received: from PWN401EA160.ent.corp.bcbsm.com ([fe80::fdcb:603d:469e:b1db]) by PWN401EA100.ent.corp.bcbsm.com ([fe80::8db:9ce7:e2cf:8565%13]) with mapi id 14.01.0438.000; Thu, 24 Oct 2013 19:44:52 -0400
From: "Ackermann, Michael" <MAckermann@bcbsm.com>
To: Ray Hunter <v6ops@globis.net>
Subject: RE: [v6ops] Fw: New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-04.txt
Thread-Topic: [v6ops] Fw: New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-04.txt
Thread-Index: AQHO0OGzc1wNgnhly0SIwwwBJHHHZZoEfl4g
Date: Thu, 24 Oct 2013 23:44:51 +0000
Message-ID: <4FC37E442D05A748896589E468752CAA0CA8A36F@PWN401EA160.ent.corp.bcbsm.com>
References: <20131017032024.5051.20799.idtracker@ietfa.amsl.com> <1381980305.36254.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com> <5263C783.1080001@globis.net> <1382396300.22968.YahooMailNeo@web2801.biz.mail.ne1.yahoo.com> <526616C4.40304@globis.net> <4FC37E442D05A748896589E468752CAA0CA88734@PWN401EA160.ent.corp.bcbsm.com> <52695E3A.9090406@globis.net>
In-Reply-To: <52695E3A.9090406@globis.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.64.10.35]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: v6ops WG <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>, "bill.jouris@insidethestack.com" <bill.jouris@insidethestack.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 24 Oct 2013 23:45:15 -0000

Ray

Your Comment:=20
No. I think what I said was that the level of certainty in your =
measurements is dependent on the level of synchronisation of the 2 clock =
sources if you are calculating a delta of timestamp of clock 1 - timestamp =
clock 2.
My Response:
Then it sounds like we are in agreement.   Given the appropriate stratum =
level at both nodes, the desired level of time synchronization is =
achieved.=20


Your Comment:=20
I think it might be instructive to go back and look at high school physics =
books on making measurements, precision, accuracy, and error estimations, =
especially when taking the difference of two measurements, or making other =
calculations on top of raw observations
My Response:  Not sure exactly what this means but I can say that this =
sounds like theoretical doubt that time synchronization will not work =
properly in geographically dispersed environments?    I can tell you that =
it does in our experiences and that the surrounding =
protocols/implementations are crafted to account for such vicissitudes. =20
I will say that I have no field experience with DCF-77 sources, only GPS =
and Cesium. =20


Your Comment:
Equally a stratum 0 clock can be free running if it loses it's radio signal.
My Response:=20
This comment sort of confused me as well, but suffice to say, if any =
component is broken, results will be impaired.   Obviously this is not =
limited to the time synch subject. =20


Finally, your comment about =22Middleboxes=22.    I hope it can be as =
simple to accommodate as you describe.   My concern is that if there are =
numerous middleboxes, the fields may get repetitively overlaid, or there =
will need to be so many separate fields, we could incur excessive =
complexity or overhead.    Given that we can accomplish this with a =
workable solution, I am certainly all for it.  =20
The more information I can have to manage networks and solve problems, the =
better=21

Thanks again for your thoughts, inputs and questions=21

Mike









=20





-----Original Message-----
From: Ray Hunter =5Bmailto:v6ops=40globis.net=5D=20
Sent: Thursday, October 24, 2013 1:52 PM
To: Ackermann, Michael
Cc: Nalini Elkins; v6ops WG; 6man WG; ippm=40ietf.org
Subject: Re: =5Bv6ops=5D Fw: New Version Notification for =
draft-elkins-6man-ipv6-pdm-dest-option-04.txt

> Ackermann, Michael <mailto:MAckermann=40bcbsm.com>
> 24 October 2013 18:50
> Hi Ray.
> And thanks again for all your insightful comments/questions.=20
>
> I am a little late in responding, so let me just tack on a little to =
what Nalini and others have already said.=20
>
> Your point 4 seems to indicate that all nodes in a desired time =
synchronization domain need to be synched to the same master clock.=20
No. I think what I said was that the level of certainty in your =
measurements is dependent on the level of synchronisation of the 2 clock =
sources if you are calculating a delta of timestamp of clock 1 - timestamp =
clock 2.

I think it might be instructive to go back and look at high school physics =
books on making measurements, precision, accuracy, and error estimations, =
especially when taking the difference of two measurements, or making other =
calculations on top of raw observations.

For example, as far as I know, DFC-77 is not compensated for speed of =
light travel time from Frankfurt: that is a manual offset. So even if two =
nodes using DCF-77 that are geographically spread across Europe are =
perfectly synchronised to the incoming radio signal, they might have a =
constant offset compared to the =22absolute=22 time in Frankfurt. That may =
or may not have an effect on one way trip measurement times you measure, =
depending on how you perform your calculations.

I think this link might be instructive.
http://www.hopf.com/en/dcf77-gps_en.html

Equally a stratum 0 clock can be free running if it loses it's radio signal.

I see time stamps in the picosecond range defined in the protocol, and =
errors on DCF-77 of up to 150mS...... completely different orders of =
magnitude of precision.


>   This has not been my experience.   As long as the required Stratum =
level is realized, for the level of accuracy required by the situation or =
application, the proper level of time synchronization is achieved.   =
Example would be that if one node in the NTP domain is referencing a GPS =
Stratum 0 and another node is referencing a separate Stratum 0 source, the =
two nodes should be Stratum 1 and within that level of accuracy. =20
> This is something we have implemented across several disparate =
enterprises and it has worked well for us.  I am wondering if your =
experience has yielded different results?
Absolutely. Different NTP servers are not guaranteed to be synched to each =
other. They're close. But not in the picosecond range.
> You also had two other points/questions, that I believe Nalini already =
responded to, but..............
>
> 1. The possibility that =22Middleboxes=22 could utilize PDM, is very =
intriguing to me.  I believe this would be more difficult to =
add/implement, but worth the effort if the Middlebox vendors would =
perceive value and actually use PDM.  Not sure how to determine if this =
would be the case or not?=20

Why would it be difficult? If you can define the encoder in your protocol =
in terms of absolute local timestamps only, plus a provenance of the clock =
used for the timestamp, it would be a simple matter of inserting an =
additional destination header into every forwarded packet when the =
middlebox forwards it.
> 2. It would be ideal to have only 1 PDM format that handles both time =
sycnronized and non synchronized situations.   I do not readily see how to =
achieve this.   Would love to talk to you some more if you have some =
ideas=21 =20
Well for example, PDM 2 uses a local delta for the last packet =
transmission time: DELTALS.

IMHO If you know absolute timestamp 1 of clock 1 =40 last packet n sent =
from node 1, and absolute timestamp 2 of clock 1 =40 last packet n+1 sent =
from node 1, I see it as a trivial matter to calculate the delta time =
between sending packet n and sending packet n+1 remotely at a decoder at a =
remote location (as observed at node 1), which will be identical to =
DELTALS, rather than calculating this value locally in the transmitting =
node 1 before sending the packet. =5Byou can only encode this DELTALS =
value in packet 2.. anyway=5D

I suspect the step that you are missing is coupling a timestamp to a clock =
and a packet ID and an event, and specifying only two timestamps in the =
packet, rather than both nodes timestamping the same events with their =
respective local clocks.

You could also have timestamps for last received n from node 2 based on =
clock 1 sent in replies to packet n by node 1, and last received n+1 from =
node 2 based on clock1 sent in replies to packet n+1 by node 1, so that =
you can calculate DELTALR remotely too (as observed at the location of the =
receiving node 1). That way you avoid the need to calculate delta locally, =
or any need to track sessions in the transmitter (so that you can =
calculate a delta in the transmitter). You do obviously have to calculate =
a delta and track sessions in the decoder, but that is not time critical, =
and also can be applied to a subset of all traffic.
>
> Again, thanks for your great input, thoughts and questions=21=21=21  =
(and hopefully more to come). =20
>
> Mike
>
It seems to me that what you are essentially doing with this protocol is =
largely what NTP does anyway.

So examining the NTP RFC might give you tips on what timestamps you need. =
And equally, since you are going to be sending high bandwidth synch =
traffic between 2 nodes, you might want to consider feeding the results =
back into NTP to see if you can improve the clock synchronisation between =
measuring nodes.

--
Regards,
RayH



The information contained in this communication is highly confidential and =
is intended solely for the use of the individual(s) to whom this =
communication is directed. If you are not the intended recipient, you are =
hereby notified that any viewing, copying, disclosure or distribution of =
this information is prohibited. Please notify the sender, by electronic =
mail or telephone, of any unintended receipt and delete the original =
message without making any copies.
=20
 Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are =
nonprofit corporations and independent licensees of the Blue Cross and =
Blue Shield Association.

From bob.hinden@gmail.com  Thu Oct 24 16:55:41 2013
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5772411E8249 for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 16:55:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i+uJxXL80MYr for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 16:55:40 -0700 (PDT)
Received: from mail-qe0-x231.google.com (mail-qe0-x231.google.com [IPv6:2607:f8b0:400d:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id D1AF311E827F for <ipv6@ietf.org>; Thu, 24 Oct 2013 16:55:27 -0700 (PDT)
Received: by mail-qe0-f49.google.com with SMTP id a11so1901518qen.8 for <ipv6@ietf.org>; Thu, 24 Oct 2013 16:55:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version; bh=nwTjd9YjcLG9UJpdMj/JeTIyd9SnWhqwTiR2pQJsaTU=; b=voGPqbgiwXb1QHV4SZ0XA2pnMjSQWlGV09aCdyqrFhGJtdxBIDEl+/UQGY4s0VoGic 7HGNn2vZmTZswHpJWGi6wXMLQDEW6CXkrpKytzzd8wokdN8DivDqNnEwvwrL5fJhJJ/6 vXKNOlNOCz1CDDHUrU8gPwFCy0fIOGp+vyDvPfghdKRolTPD0UPDC1FS9qnIgqNMhTkY S6ZcagBAVeJsR3qLqRcHvgLA48RJA/pOEk84eyH8JJ+KDYHODrkv59ZG+7MICfXRI2aM 7Ba4vAj9pRgwTwqP+aZWO6g+NgLxO0tz0X83q8Q7/1NzmX0embCaAOL4ZOKmq6XQnrbP DzQg==
X-Received: by 10.49.94.172 with SMTP id dd12mr7309638qeb.4.1382658926955; Thu, 24 Oct 2013 16:55:26 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by mx.google.com with ESMTPSA id ge5sm7848413qeb.5.2013.10.24.16.55.25 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 24 Oct 2013 16:55:26 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: IETF88 6MAN Agenda
Date: Thu, 24 Oct 2013 16:55:25 -0700
Message-Id: <DD9D29B2-CFE4-49A0-9330-70B05CA994AA@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)
Cc: Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 24 Oct 2013 23:55:41 -0000

The agenda for 6man has been posted at

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

We were able to accommodate most requests, but for some new drafts that =
have not had enough discussion, we are starting something new.

For the last 20 minutes of the session we will have four "Speed Talks".  =
These will be limited to five minutes and three slides each.  The =
prupose is to allow the authors to present a quick summary of their =
proposal to generate discussion on the mailing list.

There were a few requests we did not give agenda time to.  There were =
topics that had been presented at earlier 6man session and the chairs =
did not feel that the working group had expressed enough interested to =
allocate another speaking slot.  The authors should see if they can =
develop interest on the mailing list.  We will be contacting each person =
directly.

Speakers should send a pdf of their slides to the chairs no later than =
Saturday November 2.  The session is at 9am on Monday, so we need to =
have everything uploaded well before the session starts.

Thanks,
Bob & Ole


From brian.e.carpenter@gmail.com  Thu Oct 24 16:57:40 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A228811E827B for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 16:57:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.535
X-Spam-Level: 
X-Spam-Status: No, score=-102.535 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id okR2Di4UubKy for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 16:57:40 -0700 (PDT)
Received: from mail-pb0-x230.google.com (mail-pb0-x230.google.com [IPv6:2607:f8b0:400e:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 1DA7211E8277 for <ipv6@ietf.org>; Thu, 24 Oct 2013 16:57:40 -0700 (PDT)
Received: by mail-pb0-f48.google.com with SMTP id mc8so378916pbc.21 for <ipv6@ietf.org>; Thu, 24 Oct 2013 16:57:39 -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=9dmWlJHEkbLXwAo+jWipjKTI/5DJrjZL42wOrFTu2sU=; b=QqXWFwAVG4ko5fHvm+KHQ4tpN63+OmfcIJH1Bjpq8c0q+x4gvBdOevj78vF8GIDpEW jU75RvNqFyJiY+xsww5Hnp8rGJ6XfW6KtImc0Ys7DPPCddwnzQx4c1LBXVXfJQtiFg9O LyGXOiZ4Bhzc8r+EatVWpLlF9oN64XIuvbF/aiav9H3dTmK2FGVGDrdBVUhjHcsa1N8Q JavvNTOZ5DKDxYuWohrX84gsVfdDaNNOnV1RmwNz4QdJBccQfdVSqLss0/xuIsKQa9Qi +ius/WN2qDxge7W5kDyn2Baaq7oFvhz+aWc7mvk4RjLlm43rTQoqHnQ77RRk/gVlKrNA LHyw==
X-Received: by 10.66.118.71 with SMTP id kk7mr6233136pab.14.1382659059688; Thu, 24 Oct 2013 16:57:39 -0700 (PDT)
Received: from [192.168.178.20] (181.196.69.111.dynamic.snap.net.nz. [111.69.196.181]) by mx.google.com with ESMTPSA id wr10sm5243827pbc.17.2013.10.24.16.57.37 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 24 Oct 2013 16:57:39 -0700 (PDT)
Message-ID: <5269B3FB.8080007@gmail.com>
Date: Fri, 25 Oct 2013 12:57:47 +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: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com> <52697C33.7010904@gmail.com> <a06240804ce8f365bd832@[10.0.1.3]> <5269936F.7020705@gmail.com> <E9BB1094-64E9-4219-B801-7205D2B0A1E4@ecs.soton.ac.uk> <EMEW3|caa096f62332b0b87f0053a710e89364p9NN1V03tjc|ecs.soton.ac.uk|E9BB1094-64E9-4219-B801-7205D2B0A1E4@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|caa096f62332b0b87f0053a710e89364p9NN1V03tjc|ecs.soton.ac.uk|E9BB1094-64E9-4219-B801-7205D2B0A1E4@ecs.soton.ac.uk>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 6man <ipv6@ietf.org>, John Day <jeanjour@comcast.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 24 Oct 2013 23:57:40 -0000

On 25/10/2013 11:01, Tim Chown wrote:
> On 24 Oct 2013, at 22:38, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
>> On 25/10/2013 09:58, John Day wrote:
>>> I couldn't agree with you more, Brian.   This is a really bad idea.
>>>
>>> "Government" should not be trying to protect us from ourselves! (Did I
>>> hear that on Fox News or was it Rush Limbaugh?)  This is not the proper
>>> kind of constraints for the IETF to be imposing. Information wants to be
>>> free!  If some operations manager wants to improve the ability of others
>>> to trace his traffic and spy on the people in his network, he should be
>>> allowed to do it.
>>>
>>> As for tracing malicious users, that is a bit like the argument that if
>>> guns are outlawed only outlaws will have guns. Only in this case, if we
>>> don't outlaw it only the clueless will use MAC Addresses as endpoint
>>> ids, the "outlaws" aren't that dumb.  I really doubt they would use
>>> their own MAC addresses, or even to use the same one for very long.
>> In some contexts that doesn't matter. For example, at the university
>> where I currently work, a student can sit at any one of a few thousand
>> workstations - the security people need a way to track back malicious
>> traffic to a specific login session. The MAC address is definitely part
>> of the tracking process, even if the student is long gone.
> 
> But it's part of the tracking at the Ethernet layer, not the IP layer. There is no need at all to include the MAC address in the IP address for accountability purposes. 

I agree that there will always be a way to do it without; IPv4
is the proof. But that isn't really my main concern; it's that
the suggested MUST NOT is just not realistic, so the resulting RFC
wouldn't be taken seriously outside the IETF.

    Brian

From tjc@ecs.soton.ac.uk  Thu Oct 24 17:02:18 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECEC711E827B for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 17:02:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id frl+JiuWkrg5 for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 17:02:18 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 935C911E824C for <ipv6@ietf.org>; Thu, 24 Oct 2013 17:02:14 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r9P01ttm018622; Fri, 25 Oct 2013 01:01:55 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r9P01ttm018622
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1382659315; bh=YmLiSFnlUCHUpoOKOzFM5rTz59I=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=iFnd3SsmlWmT7CSX2+HaXeWyZI8C3IGu65okmV6ySeGObnlcLFGPHcfu1nbTwX6Kz zpbKw7htj8ztcxfJWH4J86AtpcdCj7MT+dBzk7h3ig2SwjbqfiOTaIb4UTV0hjJwlI Fa088zKG9oEseva2Xdy+N/yPaZDUw81bwI/8XWuo=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p9O11y09596635290O ret-id none; Fri, 25 Oct 2013 01:01:55 +0100
Received: from [192.168.1.108] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r9P01mSH019470 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 25 Oct 2013 01:01:48 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <5269B3FB.8080007@gmail.com>
Date: Fri, 25 Oct 2013 01:01:49 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|abf1cccb479ec105214e7466c7c3a9e6p9O11y03tjc|ecs.soton.ac.uk|76A6422A-EEE4-4C87-9505-ABDC04063621@ecs.soton.ac.uk>
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com> <52697C33.7010904@gmail.com> <a06240804ce8f365bd832@[10.0.1.3]> <5269936F.7020705@gmail.com> <E9BB1094-64E9-4219-B801-7205D2B0A1E4@ecs.soton.ac.uk> <EMEW3|caa096f62332b0b87f0053a710e89364p9NN1V03tjc|ecs.soton.ac.uk|E9BB1094-64E9-4219-B801-7205D2B0A1E4@ecs.soton.ac.uk> <5269B3FB.8080007@gmail.com> <76A6422A-EEE4-4C87-9505-ABDC04063621@ecs.soton.ac.uk>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1510)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p9O11y095966352900; tid=p9O11y09596635290O; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r9P01ttm018622
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: 6man <ipv6@ietf.org>, John Day <jeanjour@comcast.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 00:02:19 -0000

On 25 Oct 2013, at 00:57, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

> On 25/10/2013 11:01, Tim Chown wrote:
>> On 24 Oct 2013, at 22:38, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>>=20
>>> On 25/10/2013 09:58, John Day wrote:
>>>> I couldn't agree with you more, Brian.   This is a really bad idea.
>>>>=20
>>>> "Government" should not be trying to protect us from ourselves! =
(Did I
>>>> hear that on Fox News or was it Rush Limbaugh?)  This is not the =
proper
>>>> kind of constraints for the IETF to be imposing. Information wants =
to be
>>>> free!  If some operations manager wants to improve the ability of =
others
>>>> to trace his traffic and spy on the people in his network, he =
should be
>>>> allowed to do it.
>>>>=20
>>>> As for tracing malicious users, that is a bit like the argument =
that if
>>>> guns are outlawed only outlaws will have guns. Only in this case, =
if we
>>>> don't outlaw it only the clueless will use MAC Addresses as =
endpoint
>>>> ids, the "outlaws" aren't that dumb.  I really doubt they would use
>>>> their own MAC addresses, or even to use the same one for very long.
>>> In some contexts that doesn't matter. For example, at the university
>>> where I currently work, a student can sit at any one of a few =
thousand
>>> workstations - the security people need a way to track back =
malicious
>>> traffic to a specific login session. The MAC address is definitely =
part
>>> of the tracking process, even if the student is long gone.
>>=20
>> But it's part of the tracking at the Ethernet layer, not the IP =
layer. There is no need at all to include the MAC address in the IP =
address for accountability purposes.=20
>=20
> I agree that there will always be a way to do it without; IPv4
> is the proof. But that isn't really my main concern; it's that
> the suggested MUST NOT is just not realistic, so the resulting RFC
> wouldn't be taken seriously outside the IETF.

With the MUST NOT, I agree.  Fernando's alternative should be attractive =
enough for vendors to move to over time, without this draft. Microsoft =
already do something similar, for similar reasons.  I think the carrot =
is tasty enough to avoid the need for a stick.

Tim=

From fgont@si6networks.com  Thu Oct 24 17:16:42 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2C4B21F99B0 for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 17:16:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.142
X-Spam-Level: 
X-Spam-Status: No, score=-1.142 tagged_above=-999 required=5 tests=[AWL=-0.843, BAYES_00=-2.599, MANGLED_FROM=2.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LgB+mzhEKHWh for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 17:16:34 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id F3A6011E8269 for <ipv6@ietf.org>; Thu, 24 Oct 2013 17:16:31 -0700 (PDT)
Received: from 86-135-17-190.fibertel.com.ar ([190.17.135.86] helo=[192.168.1.118]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1VZV4n-0003F0-Nc; Fri, 25 Oct 2013 02:16:30 +0200
Message-ID: <5269B633.8010802@si6networks.com>
Date: Thu, 24 Oct 2013 21:07:15 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, 6man <ipv6@ietf.org>
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com> <52697C33.7010904@gmail.com>
In-Reply-To: <52697C33.7010904@gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 00:16:42 -0000

On 10/24/2013 04:59 PM, Brian E Carpenter wrote:
> Unfortunately I feel that this is operationally unacceptable.
> 
> There are many (I suppose thousands) of sites that rely on MAC
> addresses to manage their assets, and in many cases to trace
> malicious users. 

Question:

Do you argue that they rely on
1) the MAC address being present in the IID, or,
2) the IPv6 address (and hence the IPv6 -> link layer address mapping)
   being stable?

If "1)", I wonder:
a) why (in the first place :-) )
b) how they manage Windows nodes (which do not employ IEEE-based IIDs)


If you meant "2)" above, please note that we're recommending
stable-privacy, which does produces "stable per network" addresses. For
instance, this scheme was acceptebable to Ron Broersma, that did a
number f presentation on why they needed to disable RFC4941 for
accountability etc.



> It's certainly true that in theory, they can do
> this by using ND or DHCPv6 logging, as today they use ARP cache
> or DHCP logging to trace IPv4 users, and they may have to do this
> anyway when some users implement some form of obscure IID generation.

You don't need to do this with stable-privacy. For instance, this is
exactly the reason for shich stable-privacy uses a hash rather than
random() at bootstrapping time.


> But I just don't see site managers in general (and therefore vendors)
> accepting this:
> 
> "Nodes MUST NOT employ IPv6 address generation schemes that embed the
>  underlying hardware address in the Interface Identifier."
> 
> I would suggest that this might fly:
> 
> "Nodes SHOULD NOT employ IPv6 address generation schemes that embed the
>  underlying hardware address in the Interface Identifier, and such schemes
>  MUST NOT be enabled by default in any implementation."
> 
> Even that might prove unrealistic.

Please see above. Besides, note that Microsoft has moved away froom
IEEE-based IDs for *years* now.


> Incidentally, your case would be strengthened by referring to
> draft-ietf-6man-ug, which makes it plain that the case for EUI64
> is weaker than was originally thought.

Are you referring to MAC address duplication, or something else?

Thanks!

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





From fernando@gont.com.ar  Thu Oct 24 17:21:42 2013
Return-Path: <fernando@gont.com.ar>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4452011E81DB for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 17:21:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.288
X-Spam-Level: 
X-Spam-Status: No, score=-2.288 tagged_above=-999 required=5 tests=[AWL=0.311,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zlTD1WFDe4Dy for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 17:21:39 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id A924411E8231 for <ipv6@ietf.org>; Thu, 24 Oct 2013 17:21:38 -0700 (PDT)
Received: from 86-135-17-190.fibertel.com.ar ([190.17.135.86] helo=[192.168.1.118]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fernando@gont.com.ar>) id 1VZV9h-0003Lz-G0; Fri, 25 Oct 2013 02:21:36 +0200
Message-ID: <5269B943.6080709@gont.com.ar>
Date: Thu, 24 Oct 2013 21:20:19 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>,  Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com>	<52697C33.7010904@gmail.com> <a06240804ce8f365bd832@[10.0.1.3]>	<5269936F.7020705@gmail.com>	<E9BB1094-64E9-4219-B801-7205D2B0A1E4@ecs.soton.ac.uk>	<EMEW3|caa096f62332b0b87f0053a710e89364p9NN1V03tjc|ecs.soton.ac.uk|E9BB1094-64E9-4219-B801-7205D2B0A1E4@ecs.soton.ac.uk> <5269B3FB.8080007@gmail.com>
In-Reply-To: <5269B3FB.8080007@gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 6man <ipv6@ietf.org>, John Day <jeanjour@comcast.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 00:21:42 -0000

On 10/24/2013 08:57 PM, Brian E Carpenter wrote:
>> 
>> But it's part of the tracking at the Ethernet layer, not the IP
>> layer. There is no need at all to include the MAC address in the IP
>> address for accountability purposes.
> 
> I agree that there will always be a way to do it without; IPv4 is the
> proof. 

Please see my other port on the topic: do you really need/expect the MAC
address in the IID, or is it just that you expect the address to be stable?


> But that isn't really my main concern; it's that the suggested
> MUST NOT is just not realistic, so the resulting RFC wouldn't be
> taken seriously outside the IETF.

FWIW, I can certainly live with "SHOULD NOT". Your proposed change "...
SHOULD NOT...and MUST NOT enable it by default" sounds perfectly
reasonable to me.

What do other folks think?

Thanks!

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





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




From jiangsheng@huawei.com  Thu Oct 24 18:07:12 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 212CD11E8261 for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 18:07:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.56
X-Spam-Level: 
X-Spam-Status: No, score=-6.56 tagged_above=-999 required=5 tests=[AWL=0.039,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KogpyxTXn4oS for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 18:07:08 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id A9BFE11E8239 for <ipv6@ietf.org>; Thu, 24 Oct 2013 18:07:05 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AXE09344; Fri, 25 Oct 2013 01:07:04 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 25 Oct 2013 02:06:53 +0100
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 25 Oct 2013 02:06:59 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.191]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.03.0146.000; Fri, 25 Oct 2013 09:06:55 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
Thread-Topic: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
Thread-Index: AQHO0QFw5IfmHRNWEECrB55ezpjxBpoD4Q4AgAAggICAAAEggIAAlW4A
Date: Fri, 25 Oct 2013 01:06:54 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AD4D6E5@nkgeml512-mbx.china.huawei.com>
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com> <52697C33.7010904@gmail.com> <a06240804ce8f365bd832@[10.0.1.3]> <5269936F.7020705@gmail.com> <E9BB1094-64E9-4219-B801-7205D2B0A1E4@ecs.soton.ac.uk> <EMEW3|caa096f62332b0b87f0053a710e89364p9NN1V03tjc|ecs.soton.ac.uk|E9BB1094-64E9-4219-B801-7205D2B0A1E4@ecs.soton.ac.uk> <5269B3FB.8080007@gmail.com> <76A6422A-EEE4-4C87-9505-ABDC04063621@ecs.soton.ac.uk> <EMEW3|abf1cccb479ec105214e7466c7c3a9e6p9O11y03tjc|ecs.soton.ac.uk|76A6422A-EEE4-4C87-9505-ABDC04063621@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|abf1cccb479ec105214e7466c7c3a9e6p9O11y03tjc|ecs.soton.ac.uk|76A6422A-EEE4-4C87-9505-ABDC04063621@ecs.soton.ac.uk>
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
Cc: 6man <ipv6@ietf.org>, John Day <jeanjour@comcast.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 01:07:12 -0000

QWdyZWUgd2l0aCBUaW0gYW5kIEJyaWFuLiBUaGUgcmVhbGl0eSBpcyB0aGlzIGhhcyBiZWVuIHdp
ZGVseSB1c2VkIGluIHNvIG1hbnkgaW1wbGVtZW50YXRpb25zLiBXZSBhbGwga25vdyBob3cgZGlm
ZmljdWx0IGZvciB0aGVzZSBpbXBsZW1lbnRhdGlvbnMgdG8gYmUgY2hhbmdlZC4gV2UgaGF2ZSBz
aW1pbGFyIGV4cGVyaWVuY2Ugd2l0aCBJUHY2IHRyYW5zaXRpb24gLSB0byBhZGQgSVB2NiBzdGFj
ayBpbnRvIGFueSBvbmUgaW1wbGVtZW50YXRpb25zIGlzIG5vdCBkaWZmaWN1bHQuIEJ1dCBjaGFu
Z2luZyBhbGwgb3IgbW9zdCBvZiB0aGVzZSBpbXBsZW1lbnRhdGlvbnMgdGFrZXMgeWVhcnMuDQoN
Ck9uIGFub3RoZXIgc2lkZSwgSSBkbyBzZWUgRmVybmFuZG8ncyBwb2ludCBldWk2NC1iYXNlZCBh
ZGRyZXNzZXMgc2hvdWxkIGJlIHVzZWQgbGVzcyBhbmQgbGVzcy4gTXkgc3VnZ2VzdGlvbiBpczog
aW5zdGVhZCBvZiAiZGVwcmVjYXRlIiBhbmQgIk1VU1QgTk9UIiwgdXNlIHRoZXNlIHNvZnRlciB3
b3JkICJEaXNjb3VyYWdlIiBhbmQgIlNIT1VMRCBOT1QiLiBBbHRob3VnaCB0aGVzZSB0b3VnaCB3
b3JkIG1heSBnaXZlIG91dCBzdHJvbmdlciBtZXNzYWdlLCBwZW9wbGUgd291bGQgY2hvb3NlIHRv
IGlnbm9yZSB0aGUgbWVzc2FnZSB3aGVuIHRoZXkgZmVlbCBpdCBpcyBub3Qgb3BlcmFibGUuDQoN
ClNoZW5nDQoNCj4tLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPkZyb206IGlwdjYtYm91bmNl
c0BpZXRmLm9yZyBbbWFpbHRvOmlwdjYtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mDQo+
VGltIENob3duDQo+U2VudDogRnJpZGF5LCBPY3RvYmVyIDI1LCAyMDEzIDg6MDIgQU0NCj5Ubzog
QnJpYW4gRSBDYXJwZW50ZXINCj5DYzogNm1hbjsgSm9obiBEYXkNCj5TdWJqZWN0OiBSZTogSS1E
IEFjdGlvbjoNCj5kcmFmdC1nb250LTZtYW4tZGVwcmVjYXRlLWV1aTY0LWJhc2VkLWFkZHJlc3Nl
cy0wMC50eHQNCj4NCj4NCj5PbiAyNSBPY3QgMjAxMywgYXQgMDA6NTcsIEJyaWFuIEUgQ2FycGVu
dGVyIDxicmlhbi5lLmNhcnBlbnRlckBnbWFpbC5jb20+DQo+d3JvdGU6DQo+DQo+PiBPbiAyNS8x
MC8yMDEzIDExOjAxLCBUaW0gQ2hvd24gd3JvdGU6DQo+Pj4gT24gMjQgT2N0IDIwMTMsIGF0IDIy
OjM4LCBCcmlhbiBFIENhcnBlbnRlcg0KPjxicmlhbi5lLmNhcnBlbnRlckBnbWFpbC5jb20+IHdy
b3RlOg0KPj4+DQo+Pj4+IE9uIDI1LzEwLzIwMTMgMDk6NTgsIEpvaG4gRGF5IHdyb3RlOg0KPj4+
Pj4gSSBjb3VsZG4ndCBhZ3JlZSB3aXRoIHlvdSBtb3JlLCBCcmlhbi4gICBUaGlzIGlzIGEgcmVh
bGx5IGJhZCBpZGVhLg0KPj4+Pj4NCj4+Pj4+ICJHb3Zlcm5tZW50IiBzaG91bGQgbm90IGJlIHRy
eWluZyB0byBwcm90ZWN0IHVzIGZyb20gb3Vyc2VsdmVzISAoRGlkIEkNCj4+Pj4+IGhlYXIgdGhh
dCBvbiBGb3ggTmV3cyBvciB3YXMgaXQgUnVzaCBMaW1iYXVnaD8pICBUaGlzIGlzIG5vdCB0aGUN
Cj5wcm9wZXINCj4+Pj4+IGtpbmQgb2YgY29uc3RyYWludHMgZm9yIHRoZSBJRVRGIHRvIGJlIGlt
cG9zaW5nLiBJbmZvcm1hdGlvbiB3YW50cyB0byBiZQ0KPj4+Pj4gZnJlZSEgIElmIHNvbWUgb3Bl
cmF0aW9ucyBtYW5hZ2VyIHdhbnRzIHRvIGltcHJvdmUgdGhlIGFiaWxpdHkgb2YNCj5vdGhlcnMN
Cj4+Pj4+IHRvIHRyYWNlIGhpcyB0cmFmZmljIGFuZCBzcHkgb24gdGhlIHBlb3BsZSBpbiBoaXMg
bmV0d29yaywgaGUgc2hvdWxkIGJlDQo+Pj4+PiBhbGxvd2VkIHRvIGRvIGl0Lg0KPj4+Pj4NCj4+
Pj4+IEFzIGZvciB0cmFjaW5nIG1hbGljaW91cyB1c2VycywgdGhhdCBpcyBhIGJpdCBsaWtlIHRo
ZSBhcmd1bWVudCB0aGF0IGlmDQo+Pj4+PiBndW5zIGFyZSBvdXRsYXdlZCBvbmx5IG91dGxhd3Mg
d2lsbCBoYXZlIGd1bnMuIE9ubHkgaW4gdGhpcyBjYXNlLCBpZiB3ZQ0KPj4+Pj4gZG9uJ3Qgb3V0
bGF3IGl0IG9ubHkgdGhlIGNsdWVsZXNzIHdpbGwgdXNlIE1BQyBBZGRyZXNzZXMgYXMgZW5kcG9p
bnQNCj4+Pj4+IGlkcywgdGhlICJvdXRsYXdzIiBhcmVuJ3QgdGhhdCBkdW1iLiAgSSByZWFsbHkg
ZG91YnQgdGhleSB3b3VsZCB1c2UNCj4+Pj4+IHRoZWlyIG93biBNQUMgYWRkcmVzc2VzLCBvciBl
dmVuIHRvIHVzZSB0aGUgc2FtZSBvbmUgZm9yIHZlcnkgbG9uZy4NCj4+Pj4gSW4gc29tZSBjb250
ZXh0cyB0aGF0IGRvZXNuJ3QgbWF0dGVyLiBGb3IgZXhhbXBsZSwgYXQgdGhlIHVuaXZlcnNpdHkN
Cj4+Pj4gd2hlcmUgSSBjdXJyZW50bHkgd29yaywgYSBzdHVkZW50IGNhbiBzaXQgYXQgYW55IG9u
ZSBvZiBhIGZldyB0aG91c2FuZA0KPj4+PiB3b3Jrc3RhdGlvbnMgLSB0aGUgc2VjdXJpdHkgcGVv
cGxlIG5lZWQgYSB3YXkgdG8gdHJhY2sgYmFjayBtYWxpY2lvdXMNCj4+Pj4gdHJhZmZpYyB0byBh
IHNwZWNpZmljIGxvZ2luIHNlc3Npb24uIFRoZSBNQUMgYWRkcmVzcyBpcyBkZWZpbml0ZWx5IHBh
cnQNCj4+Pj4gb2YgdGhlIHRyYWNraW5nIHByb2Nlc3MsIGV2ZW4gaWYgdGhlIHN0dWRlbnQgaXMg
bG9uZyBnb25lLg0KPj4+DQo+Pj4gQnV0IGl0J3MgcGFydCBvZiB0aGUgdHJhY2tpbmcgYXQgdGhl
IEV0aGVybmV0IGxheWVyLCBub3QgdGhlIElQIGxheWVyLiBUaGVyZSBpcw0KPm5vIG5lZWQgYXQg
YWxsIHRvIGluY2x1ZGUgdGhlIE1BQyBhZGRyZXNzIGluIHRoZSBJUCBhZGRyZXNzIGZvciBhY2Nv
dW50YWJpbGl0eQ0KPnB1cnBvc2VzLg0KPj4NCj4+IEkgYWdyZWUgdGhhdCB0aGVyZSB3aWxsIGFs
d2F5cyBiZSBhIHdheSB0byBkbyBpdCB3aXRob3V0OyBJUHY0DQo+PiBpcyB0aGUgcHJvb2YuIEJ1
dCB0aGF0IGlzbid0IHJlYWxseSBteSBtYWluIGNvbmNlcm47IGl0J3MgdGhhdA0KPj4gdGhlIHN1
Z2dlc3RlZCBNVVNUIE5PVCBpcyBqdXN0IG5vdCByZWFsaXN0aWMsIHNvIHRoZSByZXN1bHRpbmcg
UkZDDQo+PiB3b3VsZG4ndCBiZSB0YWtlbiBzZXJpb3VzbHkgb3V0c2lkZSB0aGUgSUVURi4NCj4N
Cj5XaXRoIHRoZSBNVVNUIE5PVCwgSSBhZ3JlZS4gIEZlcm5hbmRvJ3MgYWx0ZXJuYXRpdmUgc2hv
dWxkIGJlIGF0dHJhY3RpdmUNCj5lbm91Z2ggZm9yIHZlbmRvcnMgdG8gbW92ZSB0byBvdmVyIHRp
bWUsIHdpdGhvdXQgdGhpcyBkcmFmdC4gTWljcm9zb2Z0DQo+YWxyZWFkeSBkbyBzb21ldGhpbmcg
c2ltaWxhciwgZm9yIHNpbWlsYXIgcmVhc29ucy4gIEkgdGhpbmsgdGhlIGNhcnJvdCBpcyB0YXN0
eQ0KPmVub3VnaCB0byBhdm9pZCB0aGUgbmVlZCBmb3IgYSBzdGljay4NCj4NCj5UaW0NCj4tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLQ0KPklFVEYgSVB2NiB3b3JraW5nIGdyb3VwIG1haWxpbmcgbGlzdA0KPmlwdjZAaWV0
Zi5vcmcNCj5BZG1pbmlzdHJhdGl2ZSBSZXF1ZXN0czogaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby9pcHY2DQo+LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCg==

From brian.e.carpenter@gmail.com  Thu Oct 24 18:58:13 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EA7E11E81A7 for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 18:58:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.386
X-Spam-Level: 
X-Spam-Status: No, score=-101.386 tagged_above=-999 required=5 tests=[AWL=-1.087, BAYES_00=-2.599, MANGLED_FROM=2.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xos7b2Zm84jb for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 18:58:12 -0700 (PDT)
Received: from mail-pd0-x22b.google.com (mail-pd0-x22b.google.com [IPv6:2607:f8b0:400e:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 8E9FE11E828C for <ipv6@ietf.org>; Thu, 24 Oct 2013 18:58:11 -0700 (PDT)
Received: by mail-pd0-f171.google.com with SMTP id w10so1450914pde.30 for <ipv6@ietf.org>; Thu, 24 Oct 2013 18:58:11 -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=YMB0RpG/06BBjWk/MqkWL1J1QKpZnjKcQ+gIpfelG98=; b=OUGDVXIb79Zsnk4d3Gcis4UY3jix7h+ubmtd3fj8rvNpXdgTf20NIkfyTXueTV4B5+ gcUDUKuJmEG+fMDWBPxJ5E+nIO0EJblbuuEXJcCYwNu/IgxCIl28spsl3B8ZVDmMRVTk QDCat1fIQ4F8h1vSW29Jd8zEoQFEvJZwCFoSA02/lWKfcK/X8qBL7jcTpmrVN6JQNXqN XKe6Fhjl1qdHZxZBpEXLFDCJcEwmN2/K6MUSC/1fsixqyhIes1Dvmq8EyU8LAZMoLEtr qTgHxj2bAtIPyxb/8ECzGhnntsPaHQ2tF+jFNclromB4pJYrMrBd1HRU0wKaxLrhfhIj wpgA==
X-Received: by 10.66.196.110 with SMTP id il14mr7017849pac.130.1382666291116;  Thu, 24 Oct 2013 18:58:11 -0700 (PDT)
Received: from [192.168.178.20] (181.196.69.111.dynamic.snap.net.nz. [111.69.196.181]) by mx.google.com with ESMTPSA id at4sm5640672pbc.30.2013.10.24.18.58.08 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 24 Oct 2013 18:58:10 -0700 (PDT)
Message-ID: <5269D03A.8030809@gmail.com>
Date: Fri, 25 Oct 2013 14:58:18 +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-gont-6man-deprecate-eui64-based-addresses-00.txt
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com> <52697C33.7010904@gmail.com> <5269B633.8010802@si6networks.com>
In-Reply-To: <5269B633.8010802@si6networks.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 01:58:13 -0000

On 25/10/2013 13:07, Fernando Gont wrote:
> On 10/24/2013 04:59 PM, Brian E Carpenter wrote:
>> Unfortunately I feel that this is operationally unacceptable.
>>
>> There are many (I suppose thousands) of sites that rely on MAC
>> addresses to manage their assets, and in many cases to trace
>> malicious users. 
> 
> Question:
> 
> Do you argue that they rely on
> 1) the MAC address being present in the IID, or,
> 2) the IPv6 address (and hence the IPv6 -> link layer address mapping)
>    being stable?

I actually think that today, not too many sites have decided how
to handle this for IPv6, but the decisions whether to use SLAAC
or DHCPv6, and whether to allow RFC4941 addresses or insist
on Modified EUI-64, have to be taken as each site rolls out
IPv6. My guess is that large campus-style sites will not
allow RFC4941 because they don't have the logging to allow
a traceback to the user. So they'll either go for stateful
DHCPv6 if they can find working products for all platforms,
or stick to SLAAC/EUI-64. The reason is indeed the stable
mapping, not the fact that it's bit-for-bit mapping of
the MAC address.

The ability to deploy stable-privacy-addresses is years
in the future, but when it comes, it will probably be the best
solution for campus deployments and at that point, Modified EUI-64
could go away.

   Brian

> 
> If "1)", I wonder:
> a) why (in the first place :-) )
> b) how they manage Windows nodes (which do not employ IEEE-based IIDs)
> 
> 
> If you meant "2)" above, please note that we're recommending
> stable-privacy, which does produces "stable per network" addresses. For
> instance, this scheme was acceptebable to Ron Broersma, that did a
> number f presentation on why they needed to disable RFC4941 for
> accountability etc.
> 
> 
> 
>> It's certainly true that in theory, they can do
>> this by using ND or DHCPv6 logging, as today they use ARP cache
>> or DHCP logging to trace IPv4 users, and they may have to do this
>> anyway when some users implement some form of obscure IID generation.
> 
> You don't need to do this with stable-privacy. For instance, this is
> exactly the reason for shich stable-privacy uses a hash rather than
> random() at bootstrapping time.
> 
> 
>> But I just don't see site managers in general (and therefore vendors)
>> accepting this:
>>
>> "Nodes MUST NOT employ IPv6 address generation schemes that embed the
>>  underlying hardware address in the Interface Identifier."
>>
>> I would suggest that this might fly:
>>
>> "Nodes SHOULD NOT employ IPv6 address generation schemes that embed the
>>  underlying hardware address in the Interface Identifier, and such schemes
>>  MUST NOT be enabled by default in any implementation."
>>
>> Even that might prove unrealistic.
> 
> Please see above. Besides, note that Microsoft has moved away froom
> IEEE-based IDs for *years* now.
> 
> 
>> Incidentally, your case would be strengthened by referring to
>> draft-ietf-6man-ug, which makes it plain that the case for EUI64
>> is weaker than was originally thought.
> 
> Are you referring to MAC address duplication, or something else?
> 
> Thanks!
> 
> Cheers,

From fgont@si6networks.com  Thu Oct 24 19:07:20 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E55121F9E3A for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 19:07:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.081
X-Spam-Level: 
X-Spam-Status: No, score=-2.081 tagged_above=-999 required=5 tests=[AWL=0.518,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W0g3i8itsH6q for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 19:07:15 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 5932C11E826C for <ipv6@ietf.org>; Thu, 24 Oct 2013 19:07:10 -0700 (PDT)
Received: from 86-135-17-190.fibertel.com.ar ([190.17.135.86] helo=[192.168.1.118]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1VZWng-0006f8-QV; Fri, 25 Oct 2013 04:06:57 +0200
Message-ID: <5269CB80.3050103@si6networks.com>
Date: Thu, 24 Oct 2013 22:38:08 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Sheng Jiang <jiangsheng@huawei.com>, Tim Chown <tjc@ecs.soton.ac.uk>,  Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com>	<52697C33.7010904@gmail.com> <a06240804ce8f365bd832@[10.0.1.3]>	<5269936F.7020705@gmail.com>	<E9BB1094-64E9-4219-B801-7205D2B0A1E4@ecs.soton.ac.uk>	<EMEW3|caa096f62332b0b87f0053a710e89364p9NN1V03tjc|ecs.soton.ac.uk|E9BB1094-64E9-4219-B801-7205D2B0A1E4@ecs.soton.ac.uk>	<5269B3FB.8080007@gmail.com>	<76A6422A-EEE4-4C87-9505-ABDC04063621@ecs.soton.ac.uk>	<EMEW3|abf1cccb479ec105214e7466c7c3a9e6p9O11y03tjc|ecs.soton.ac.uk|76A6422A-EEE4-4C87-9505-ABDC04063621@ecs.soton.ac.uk> <5D36713D8A4E7348A7E10DF7437A4B923AD4D6E5@nkgeml512-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AD4D6E5@nkgeml512-mbx.china.huawei.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 6man <ipv6@ietf.org>, John Day <jeanjour@comcast.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 02:07:20 -0000

Sheng,

On 10/24/2013 10:06 PM, Sheng Jiang wrote:
> Agree with Tim and Brian. The reality is this has been widely used in
> so many implementations. 

Isn't that the case with essentially any spec you update?

What we're trying to do here is what should happen when looking
forward... what devices should be shipping in the future.


> We all know how difficult for these
> implementations to be changed. We have similar experience with IPv6
> transition - to add IPv6 stack into any one implementations is not
> difficult. But changing all or most of these implementations takes
> years.

I don't see that as a problem. Better to get this sort of thing in at
this point in time, than later.

Besides, if there's anything to gain from the whole Snowden "thing", I
guess it is to gain the necessary momentum to apply changes that improve
security/privacy. Clearly, having a device-identifier such as an IEEE
address in the IPv6 IID does not help security/privacy.


> On another side, I do see Fernando's point eui64-based addresses
> should be used less and less. My suggestion is: instead of
> "deprecate" and "MUST NOT", use these softer word "Discourage" and
> "SHOULD NOT". Although these tough word may give out stronger
> message, people would choose to ignore the message when they feel it
> is not operable.

What I'm sensing both on-list and off-list is that folks are fine with
"SHOULD NOT". So it all looks like we'll be updating the I-D accordingly.

Regarding "discourage" vs. "deprecate": Me, I'd have no issues with such
a change although:
1) I'd still like to hear what other folks think about this
2) I guess IETF circles are familiar with what "deprecate" means(*), but
folks would wonder what "discourage" means (i.e., whether it has any
semantics other than the "colloquial" meaning).

(*) based on recent discussions, it seems that people tend to have
different views on the details of what "deprecation" means.

Thanks! (and please keep the feedback coming!)
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From jiangsheng@huawei.com  Thu Oct 24 19:21:28 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A854B11E8209 for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 19:21:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.562
X-Spam-Level: 
X-Spam-Status: No, score=-6.562 tagged_above=-999 required=5 tests=[AWL=0.037,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lrB2eMfyv8J9 for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 19:21:23 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id CC15B11E81E3 for <ipv6@ietf.org>; Thu, 24 Oct 2013 19:21:19 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AZL17478; Fri, 25 Oct 2013 02:21:18 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 25 Oct 2013 03:21:12 +0100
Received: from NKGEML408-HUB.china.huawei.com (10.98.56.39) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 25 Oct 2013 03:21:17 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.191]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.03.0146.000; Fri, 25 Oct 2013 10:21:09 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Fernando Gont <fgont@si6networks.com>, Tim Chown <tjc@ecs.soton.ac.uk>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
Thread-Topic: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
Thread-Index: AQHO0QFw5IfmHRNWEECrB55ezpjxBpoD4Q4AgAAggICAAAEggIAAlW4A//+FewCAAI9xQA==
Date: Fri, 25 Oct 2013 02:21:08 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AD4D760@nkgeml512-mbx.china.huawei.com>
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com> <52697C33.7010904@gmail.com> <a06240804ce8f365bd832@[10.0.1.3]> <5269936F.7020705@gmail.com> <E9BB1094-64E9-4219-B801-7205D2B0A1E4@ecs.soton.ac.uk> <EMEW3|caa096f62332b0b87f0053a710e89364p9NN1V03tjc|ecs.soton.ac.uk|E9BB1094-64E9-4219-B801-7205D2B0A1E4@ecs.soton.ac.uk> <5269B3FB.8080007@gmail.com> <76A6422A-EEE4-4C87-9505-ABDC04063621@ecs.soton.ac.uk> <EMEW3|abf1cccb479ec105214e7466c7c3a9e6p9O11y03tjc|ecs.soton.ac.uk|76A6422A-EEE4-4C87-9505-ABDC04063621@ecs.soton.ac.uk> <5D36713D8A4E7348A7E10DF7437A4B923AD4D6E5@nkgeml512-mbx.china.huawei.com> <5269CB80.3050103@si6networks.com>
In-Reply-To: <5269CB80.3050103@si6networks.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
Cc: 6man <ipv6@ietf.org>, John Day <jeanjour@comcast.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 02:21:28 -0000

PlNoZW5nLA0KPg0KPk9uIDEwLzI0LzIwMTMgMTA6MDYgUE0sIFNoZW5nIEppYW5nIHdyb3RlOg0K
Pj4gQWdyZWUgd2l0aCBUaW0gYW5kIEJyaWFuLiBUaGUgcmVhbGl0eSBpcyB0aGlzIGhhcyBiZWVu
IHdpZGVseSB1c2VkIGluDQo+PiBzbyBtYW55IGltcGxlbWVudGF0aW9ucy4NCj4NCj5Jc24ndCB0
aGF0IHRoZSBjYXNlIHdpdGggZXNzZW50aWFsbHkgYW55IHNwZWMgeW91IHVwZGF0ZT8NCj4NCj5X
aGF0IHdlJ3JlIHRyeWluZyB0byBkbyBoZXJlIGlzIHdoYXQgc2hvdWxkIGhhcHBlbiB3aGVuIGxv
b2tpbmcNCj5mb3J3YXJkLi4uIHdoYXQgZGV2aWNlcyBzaG91bGQgYmUgc2hpcHBpbmcgaW4gdGhl
IGZ1dHVyZS4NCg0KTXkgdW5kZXJzdGFuZGluZyBpcyB0aGF0IHB1Ymxpc2hlZCBSRkMgd291bGQg
dGFrZSBpbmZsdWVuY2Ugb24gYWxsIGN1cnJlbnQgaW1wbGVtZW50YXRpb25zLCBub3Qgb25seSBm
dXR1cmUgZGV2aWNlcy4gSWYgSUVURiBwdWJsaXNoZWQgYSBSRkMgZGVwcmVjYXRlIGV1aTY0LWJh
c2VkIElQdjYgYWRkcmVzc2VzLCBpdCBtZWFucyBhbGwgY3VycmVudCBpbXBsZW1lbnRhdGlvbnMg
bmVlZCB0byBiZSBtb2RpZmllZCB0b28uDQoNCldlIGNvdWxkIGNvbXBhcmUgdG8gb2lsLWJhc2Vk
IGNhcnMuIFdlIHNob3VsZCBlbmNvdXJhZ2UgdXNlIG9mIGVsZWN0cm9uaWMgY2FycyBmb3IgZW52
aXJvbm1lbnQgcHJvdGVjdGlvbi4gQnV0IHdlIGNhbm5vdCBlbmZvcmNlIHBlb3BsZSB0byBjaGFu
Z2UgdGhlaXIgY3VycmVudCBvaWwtYmFzZWQgY2FyLiBUaGUgcmlnaHQgbWVzc2FnZSBpcyBvbmUg
U0hPVUxEIGJ1eSBlbGVjdHJvbmljIGNhciB3aGVuIGhlIGNoYW5nZSBhIG5ldyBjYXIuIEV2ZW4g
c28sIGl0IHNob3VsZCBub3QgYmUgIk1VU1QiLg0KDQpTaGVuZw0KDQo+PiBXZSBhbGwga25vdyBo
b3cgZGlmZmljdWx0IGZvciB0aGVzZQ0KPj4gaW1wbGVtZW50YXRpb25zIHRvIGJlIGNoYW5nZWQu
IFdlIGhhdmUgc2ltaWxhciBleHBlcmllbmNlIHdpdGggSVB2Ng0KPj4gdHJhbnNpdGlvbiAtIHRv
IGFkZCBJUHY2IHN0YWNrIGludG8gYW55IG9uZSBpbXBsZW1lbnRhdGlvbnMgaXMgbm90DQo+PiBk
aWZmaWN1bHQuIEJ1dCBjaGFuZ2luZyBhbGwgb3IgbW9zdCBvZiB0aGVzZSBpbXBsZW1lbnRhdGlv
bnMgdGFrZXMNCj4+IHllYXJzLg0KPg0KPkkgZG9uJ3Qgc2VlIHRoYXQgYXMgYSBwcm9ibGVtLiBC
ZXR0ZXIgdG8gZ2V0IHRoaXMgc29ydCBvZiB0aGluZyBpbiBhdA0KPnRoaXMgcG9pbnQgaW4gdGlt
ZSwgdGhhbiBsYXRlci4NCj4NCj5CZXNpZGVzLCBpZiB0aGVyZSdzIGFueXRoaW5nIHRvIGdhaW4g
ZnJvbSB0aGUgd2hvbGUgU25vd2RlbiAidGhpbmciLCBJDQo+Z3Vlc3MgaXQgaXMgdG8gZ2FpbiB0
aGUgbmVjZXNzYXJ5IG1vbWVudHVtIHRvIGFwcGx5IGNoYW5nZXMgdGhhdCBpbXByb3ZlDQo+c2Vj
dXJpdHkvcHJpdmFjeS4gQ2xlYXJseSwgaGF2aW5nIGEgZGV2aWNlLWlkZW50aWZpZXIgc3VjaCBh
cyBhbiBJRUVFDQo+YWRkcmVzcyBpbiB0aGUgSVB2NiBJSUQgZG9lcyBub3QgaGVscCBzZWN1cml0
eS9wcml2YWN5Lg0KPg0KPg0KPj4gT24gYW5vdGhlciBzaWRlLCBJIGRvIHNlZSBGZXJuYW5kbydz
IHBvaW50IGV1aTY0LWJhc2VkIGFkZHJlc3Nlcw0KPj4gc2hvdWxkIGJlIHVzZWQgbGVzcyBhbmQg
bGVzcy4gTXkgc3VnZ2VzdGlvbiBpczogaW5zdGVhZCBvZg0KPj4gImRlcHJlY2F0ZSIgYW5kICJN
VVNUIE5PVCIsIHVzZSB0aGVzZSBzb2Z0ZXIgd29yZCAiRGlzY291cmFnZSIgYW5kDQo+PiAiU0hP
VUxEIE5PVCIuIEFsdGhvdWdoIHRoZXNlIHRvdWdoIHdvcmQgbWF5IGdpdmUgb3V0IHN0cm9uZ2Vy
DQo+PiBtZXNzYWdlLCBwZW9wbGUgd291bGQgY2hvb3NlIHRvIGlnbm9yZSB0aGUgbWVzc2FnZSB3
aGVuIHRoZXkgZmVlbCBpdA0KPj4gaXMgbm90IG9wZXJhYmxlLg0KPg0KPldoYXQgSSdtIHNlbnNp
bmcgYm90aCBvbi1saXN0IGFuZCBvZmYtbGlzdCBpcyB0aGF0IGZvbGtzIGFyZSBmaW5lIHdpdGgN
Cj4iU0hPVUxEIE5PVCIuIFNvIGl0IGFsbCBsb29rcyBsaWtlIHdlJ2xsIGJlIHVwZGF0aW5nIHRo
ZSBJLUQgYWNjb3JkaW5nbHkuDQo+DQo+UmVnYXJkaW5nICJkaXNjb3VyYWdlIiB2cy4gImRlcHJl
Y2F0ZSI6IE1lLCBJJ2QgaGF2ZSBubyBpc3N1ZXMgd2l0aCBzdWNoDQo+YSBjaGFuZ2UgYWx0aG91
Z2g6DQo+MSkgSSdkIHN0aWxsIGxpa2UgdG8gaGVhciB3aGF0IG90aGVyIGZvbGtzIHRoaW5rIGFi
b3V0IHRoaXMNCj4yKSBJIGd1ZXNzIElFVEYgY2lyY2xlcyBhcmUgZmFtaWxpYXIgd2l0aCB3aGF0
ICJkZXByZWNhdGUiIG1lYW5zKCopLCBidXQNCj5mb2xrcyB3b3VsZCB3b25kZXIgd2hhdCAiZGlz
Y291cmFnZSIgbWVhbnMgKGkuZS4sIHdoZXRoZXIgaXQgaGFzIGFueQ0KPnNlbWFudGljcyBvdGhl
ciB0aGFuIHRoZSAiY29sbG9xdWlhbCIgbWVhbmluZykuDQo+DQo+KCopIGJhc2VkIG9uIHJlY2Vu
dCBkaXNjdXNzaW9ucywgaXQgc2VlbXMgdGhhdCBwZW9wbGUgdGVuZCB0byBoYXZlDQo+ZGlmZmVy
ZW50IHZpZXdzIG9uIHRoZSBkZXRhaWxzIG9mIHdoYXQgImRlcHJlY2F0aW9uIiBtZWFucy4NCj4N
Cj5UaGFua3MhIChhbmQgcGxlYXNlIGtlZXAgdGhlIGZlZWRiYWNrIGNvbWluZyEpDQo+LS0NCj5G
ZXJuYW5kbyBHb250DQo+U0k2IE5ldHdvcmtzDQo+ZS1tYWlsOiBmZ29udEBzaTZuZXR3b3Jrcy5j
b20NCj5QR1AgRmluZ2VycHJpbnQ6IDY2NjYgMzFDNiBENDg0IDYzQjIgOEZCMSBFM0M0IEFFMjUg
MEQ1NSAxRDRFIDc0OTINCj4NCj4NCj4NCg0K

From fgont@si6networks.com  Thu Oct 24 19:49:01 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33EA211E80EA for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 19:49:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.185
X-Spam-Level: 
X-Spam-Status: No, score=-2.185 tagged_above=-999 required=5 tests=[AWL=0.414,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R5HB-tIGmoCJ for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 19:49:00 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id B6CDC11E828D for <ipv6@ietf.org>; Thu, 24 Oct 2013 19:48:56 -0700 (PDT)
Received: from 86-135-17-190.fibertel.com.ar ([190.17.135.86] helo=[192.168.1.118]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1VZXS8-0007c4-8y; Fri, 25 Oct 2013 04:48:44 +0200
Message-ID: <5269DAD1.6060909@si6networks.com>
Date: Thu, 24 Oct 2013 23:43:29 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Sheng Jiang <jiangsheng@huawei.com>, Tim Chown <tjc@ecs.soton.ac.uk>,  Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com>	<52697C33.7010904@gmail.com> <a06240804ce8f365bd832@[10.0.1.3]>	<5269936F.7020705@gmail.com>	<E9BB1094-64E9-4219-B801-7205D2B0A1E4@ecs.soton.ac.uk>	<EMEW3|caa096f62332b0b87f0053a710e89364p9NN1V03tjc|ecs.soton.ac.uk|E9BB1094-64E9-4219-B801-7205D2B0A1E4@ecs.soton.ac.uk>	<5269B3FB.8080007@gmail.com>	<76A6422A-EEE4-4C87-9505-ABDC04063621@ecs.soton.ac.uk>	<EMEW3|abf1cccb479ec105214e7466c7c3a9e6p9O11y03tjc|ecs.soton.ac.uk|76A6422A-EEE4-4C87-9505-ABDC04063621@ecs.soton.ac.uk>	<5D36713D8A4E7348A7E10DF7437A4B923AD4D6E5@nkgeml512-mbx.china.huawei.com>	<5269CB80.3050103@si6networks.com> <5D36713D8A4E7348A7E10DF7437A4B923AD4D760@nkgeml512-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AD4D760@nkgeml512-mbx.china.huawei.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 6man <ipv6@ietf.org>, John Day <jeanjour@comcast.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 02:49:01 -0000

On 10/24/2013 11:21 PM, Sheng Jiang wrote:
>> 
>> On 10/24/2013 10:06 PM, Sheng Jiang wrote:
>>> Agree with Tim and Brian. The reality is this has been widely
>>> used in so many implementations.
>> 
>> Isn't that the case with essentially any spec you update?
>> 
>> What we're trying to do here is what should happen when looking 
>> forward... what devices should be shipping in the future.
> 
> My understanding is that published RFC would take influence on all
> current implementations, not only future devices.

Current and future. For obvious reasons, there will always be a delay
between a spec is published and the spec is implemented.


> If IETF published a
> RFC deprecate eui64-based IPv6 addresses, it means all current
> implementations need to be modified too.

It means that if your implementation is meant to comply with the latest
standards, it needs to be updated.

But if your implementation predates the standard... it just predates the
standard.

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





From fgont@si6networks.com  Thu Oct 24 19:51:06 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DF9311E8229 for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 19:51:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.254
X-Spam-Level: 
X-Spam-Status: No, score=-2.254 tagged_above=-999 required=5 tests=[AWL=0.345,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tnr4rWBTDGTb for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 19:51:06 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 0275911E8299 for <ipv6@ietf.org>; Thu, 24 Oct 2013 19:51:05 -0700 (PDT)
Received: from 86-135-17-190.fibertel.com.ar ([190.17.135.86] helo=[192.168.1.118]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1VZXUN-0007cB-7m; Fri, 25 Oct 2013 04:51:03 +0200
Message-ID: <5269DBBA.8020606@si6networks.com>
Date: Thu, 24 Oct 2013 23:47:22 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com> <52697C33.7010904@gmail.com> <5269B633.8010802@si6networks.com> <5269D03A.8030809@gmail.com>
In-Reply-To: <5269D03A.8030809@gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 02:51:06 -0000

Brian,

On 10/24/2013 10:58 PM, Brian E Carpenter wrote:
[...]
> IPv6. My guess is that large campus-style sites will not
> allow RFC4941 because they don't have the logging to allow
> a traceback to the user. So they'll either go for stateful
> DHCPv6 if they can find working products for all platforms,
> or stick to SLAAC/EUI-64. The reason is indeed the stable
> mapping, not the fact that it's bit-for-bit mapping of
> the MAC address.

That's the point: we're not deprecating the stable mappings. Just
improving them.



> The ability to deploy stable-privacy-addresses is years
> in the future, but when it comes, it will probably be the best
> solution for campus deployments and at that point, Modified EUI-64
> could go away.

I guess that varies from product to product. e.g., for some client OSes
this might not take that long.

FWIW, as long as MS Windows is concerned, Modified EUI 64 have been gone
for a while now -- they have mitigated at least address scannin attacks
at least since Vista.

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





From lorenzo@google.com  Thu Oct 24 22:13:50 2013
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3797111E8120 for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 22:13:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.639
X-Spam-Level: 
X-Spam-Status: No, score=-1.639 tagged_above=-999 required=5 tests=[AWL=-0.262, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_22=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SUjkIHAE3Tq9 for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 22:13:49 -0700 (PDT)
Received: from mail-ie0-x22f.google.com (mail-ie0-x22f.google.com [IPv6:2607:f8b0:4001:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 9AD8311E82A0 for <ipv6@ietf.org>; Thu, 24 Oct 2013 22:13:47 -0700 (PDT)
Received: by mail-ie0-f175.google.com with SMTP id aq17so5427299iec.6 for <ipv6@ietf.org>; Thu, 24 Oct 2013 22:13:47 -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=PMydVkPEUT5aWEMbQYTYmtjYU/cRIGVdNma9gnVb8Pk=; b=VRyk+cD1lfHgTSLlutDx/VQcGeppxa7HBn0KhGUj3/QrFPk9qU83crSL0PhDvkTKzf jp7T1udRPmVJ4Hb0nBGms9StXVAc9aY6ab6R90dorKMwEIA9Ty2umX2gDp9lc4tWuplJ EnFmr9ysAwUp4/TZG29xefm3HUWM8V6w/jpUCS7kRwpelMtY/HY5Wwk2Cvm7IdRIogKc vi+d9AdTn3PfiW6qdJe/Ds7U3AK/lpRpzN6vjBYBV6bNgxJd0oSDHAqM9fgVJVMt23cX a1sMOeiMeGPU9LC5r+H1F4HRPVlOeHZukA3RJez7BfknScngLrDCLSh+pwL4UOD6jE3I eTRQ==
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=PMydVkPEUT5aWEMbQYTYmtjYU/cRIGVdNma9gnVb8Pk=; b=eTDf7mrnCYKFBgSIFDE6x5lqAjj7cY3yppxTMDo1+MrYFtxn8+vC7e2a2IyH8TtzLG KSNyoMUTIBJ/8u7eex0nQtX/Ni1uuAUe8NJF5ECvZ8hYr+KYdDzRFhSpFBnUGCle7j2I 1FfK+v3TB69Uq3f/lmrsMtgqvUq3qJ6rK9BbBjLvamDy9GyKsuBe+V3H0NjKF7q6hoDf XlYwleCA9XzBrbELGCD9FKViXtwGtp8q7VWcs3ePmcCHIatrQQLEEzWw8BH9qALNp/xR 4/w5uUMfRlo2hURjFtdlqmLa1cO7FMmaHgk7d+ktLhfcqCWPlne30s75uye+LeTrWZno sayg==
X-Gm-Message-State: ALoCoQnNHTgi9UcU4ZH0uvu6KiYF3OXBCvK32wnudRGyunbRy87zyrNsxgPFuN1v3i+88q1UltFTMTckQJji9MGEVzujGaXQPqpmB+XoRxo8Y/C297e91pXnsC5b7UpL2dkvBkh7E5s7p18fudYOp0dvZx6OMbFExmKu2imvAIhvNGBZiKX7BhMlOunqxOZ+XQrey1xzcxI6
X-Received: by 10.42.208.211 with SMTP id gd19mr3942117icb.15.1382678027007; Thu, 24 Oct 2013 22:13:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.86.106 with HTTP; Thu, 24 Oct 2013 22:13:26 -0700 (PDT)
In-Reply-To: <52697C33.7010904@gmail.com>
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com> <52697C33.7010904@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 25 Oct 2013 14:13:26 +0900
Message-ID: <CAKD1Yr1nNa8nBMYeyUVcmpLb6buwHFCD4LGq9xbVpde83a0QTw@mail.gmail.com>
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=20cf303ea90aa3a53804e989d033
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 05:13:50 -0000

--20cf303ea90aa3a53804e989d033
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Oct 25, 2013 at 4:59 AM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> Unfortunately I feel that this is operationally unacceptable.
>

It's also a major implementation burden. Take Linux as an example, Linux
has an in-kernel implementation of autoconf.
draft-ietf-6man-stable-privacy-addresses cannot, realistically, be
implemented in kernel space because it requires stable storage. Thus, if we
disallow EUI-64 addresses, we:

1. Add an extra barrier to IPv6 adoption because someone has to write a
userspace implementation (or more than one, due to licensing issues), and
OS distributors must include that implementation (which is always a harder
sell than something that's built in).
2. Increase the footprint of embedded devices that use Linux, because now
they need both the kernel implementation (which is extremely unlikely to be
removed due to backward compatibility concerns, no matter what the IETF
says), and the userspace implementation.

In case you think that Linux doesn't matter, bear in mind that a
substantial percentage of mobile devices (and probably the majority of
smartphones/tablets) are Linux-based.

What's the security threat here? Network activity correlation and location
tracking aren't an issue if the host implements RFC4941 temporary
addresses. As for scanning and exploitation, can those be avoided simply by
blocking incoming connections to ff:fe addresses?

Finally: some environments (e.g., enterprises) which already block incoming
scans might appreciate having predictable IPv6 addresses assigned to their
hosts, especially if they already have a database of all the MAC addresses
assigned to their devices. In that case, they can simply generate AAAA
records deterministically without having to run DHCP or dynamic DNS or
anything.

So I don't think this is a worthwhile tradeoff.

--20cf303ea90aa3a53804e989d033
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Fri, Oct 25, 2013 at 4:59 AM, Brian E Carpenter <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_bl=
ank">brian.e.carpenter@gmail.com</a>&gt;</span> wrote:<br><div class=3D"gma=
il_extra">

<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204=
);border-left-style:solid;padding-left:1ex">Unfortunately I feel that this =
is operationally unacceptable.<br>

</blockquote><div><br></div><div>It&#39;s also a major implementation burde=
n. Take Linux as an example, Linux has an in-kernel implementation of autoc=
onf. draft-ietf-6man-stable-privacy-addresses cannot, realistically, be imp=
lemented in kernel space because it requires stable storage. Thus, if we di=
sallow EUI-64 addresses, we:</div>

<div><br></div><div>1. Add an extra barrier to IPv6 adoption because someon=
e has to write a userspace implementation (or more than one, due to licensi=
ng issues), and OS distributors must include that implementation (which is =
always a harder sell than something that&#39;s built in).</div>

<div>2. Increase the footprint of embedded devices that use Linux, because =
now they need both the kernel implementation (which is extremely unlikely t=
o be removed due to backward compatibility concerns, no matter what the IET=
F says), and the userspace implementation.</div>

<div><br></div><div>In case you think that Linux doesn&#39;t matter, bear i=
n mind that a substantial percentage of mobile devices (and probably the ma=
jority of smartphones/tablets) are Linux-based.</div><div><br></div><div>

What&#39;s the security threat here? Network activity correlation and locat=
ion tracking aren&#39;t an issue if the host implements RFC4941 temporary a=
ddresses. As for scanning and exploitation, can those be avoided simply by =
blocking incoming connections to ff:fe addresses?<br>

</div><div><br></div><div>Finally: some environments (e.g., enterprises) wh=
ich already block incoming scans might appreciate having predictable IPv6 a=
ddresses assigned to their hosts, especially if they already have a databas=
e of all the MAC addresses assigned to their devices. In that case, they ca=
n simply generate AAAA records deterministically without having to run DHCP=
 or dynamic DNS or anything.</div>

<div><br></div><div>So I don&#39;t think this is a worthwhile tradeoff.</di=
v></div></div></div>

--20cf303ea90aa3a53804e989d033--

From fred@cisco.com  Thu Oct 24 22:17:06 2013
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CA2011E82A5 for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 22:17:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.293
X-Spam-Level: 
X-Spam-Status: No, score=-110.293 tagged_above=-999 required=5 tests=[AWL=0.306, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PY-ZyPSBs2pX for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 22:17:01 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 010F511E8120 for <6man@ietf.org>; Thu, 24 Oct 2013 22:16:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5207; q=dns/txt; s=iport; t=1382678220; x=1383887820; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=W9jPqJRtGWa67wXByDtKOp/23o0glqD5vhfXze64wmk=; b=cuV4L7A8uhhiS44+i4cCJcSDcJWQzP6OMmkcOUDy4g6y2AuCJ/mMRkCY SASyPPS+P9mpfczf3yvkL4apmWcx7O6B3yAFDAMSCgxqsKPL1yvKKXQSg iBYjW0cbxAiAGHbKiHYyd8UwA3VG1MKct2w5fF3u/nMtt/Cm5kQJ0z+Pf w=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AicFANr9aVKtJV2a/2dsb2JhbABZgwc4VL4/gSQWdIIlAQEBAwEBAQFrCQIFBwQCAQgRAwECCxkLJwsdCAIEDgUIAQWHcwYNuXCOFIEIIBEHBgODFoENA5AtgTCHXJBYgWaBPoFxOQ
X-IronPort-AV: E=Sophos;i="4.93,568,1378857600";  d="asc'?scan'208";a="276479733"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-3.cisco.com with ESMTP; 25 Oct 2013 05:16:59 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r9P5GxVu020348 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 25 Oct 2013 05:16:59 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.23]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.02.0318.004; Fri, 25 Oct 2013 00:16:58 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Fernando Gont <fernando@gont.com.ar>
Subject: Re: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification	for draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
Thread-Topic: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification	for draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
Thread-Index: AQHO0OH8lQkejqwy7UmdsuSYFgWyOpoFNNcA
Date: Fri, 25 Oct 2013 05:16:58 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553BA7A268@xmb-rcd-x09.cisco.com>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar>
In-Reply-To: <52695DDE.70909@gont.com.ar>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.61.201.55]
Content-Type: multipart/signed; boundary="Apple-Mail=_F1206046-DFA0-4275-BCF9-1E29BD711C11"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "6man@ietf.org" <6man@ietf.org>, "<draft-gont-6man-deprecate-eui64-based-addresses@tools.ietf.org>" <draft-gont-6man-deprecate-eui64-based-addresses@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 05:17:06 -0000

--Apple-Mail=_F1206046-DFA0-4275-BCF9-1E29BD711C11
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

IMHO, we don't need to deprecate the address type. It's OK to have it. =
Deprecating it is a little more difficult than saying "oops", it means =
rethinking the link-local address, which even on non-Ethernet links =
stupidly presumes the presence of a MAC address and has no alternative. =
At most, we need to say that the use of EUI-64 addresses is optional.

Speaking for myself, I personally don't see the value of forcing a 64 =
bit IID on a LAN type that uses 48 bit MAC addresses anyway. RFC 1884 =
used the 48 bit MAC address, and I don't see a problem with saying that =
on LANs that use a MAC address of a certain length, SLAAC can presume =
that the IID (which might be optionally derived from the MAC address as =
a seed or value) would be the same length, and in general recommending =
that DHCP-assigned addresses do similarly as link-local addresses and =
legacy equipment are likely to use or be derived from the MAC address. =
Recall that the change to EUI-64 was in response to the IEEE's =
observation that MAC addresses would be moving to 64 bit on new =
technologies, and note that the IEEE is now (I'm told) discussing 128 =
bit MAC Addresses.=20

On Oct 24, 2013, at 7:50 PM, Fernando Gont <fernando@gont.com.ar> wrote:

> Folks,
>=20
> We have posted a new I-D entitled "Deprecating EUI-64 Based IPv6
> Addresses"
> =
(http://www.ietf.org/internet-drafts/draft-gont-6man-deprecate-eui64-based=
-addresses-00.txt).
>=20
> It's a spin-off of the work we've been doing on IPv6 addressing
> secuity/privacy considerations
> (draft-ietf-6man-ipv6-address-generation-privacy and
> draft-ietf-6man-stable-privacy-addresses), and the idea had already =
been
> discussed among several folks mstly off-list and at IETF meeting =
corridors.
>=20
> Any comments will be appreciated.
>=20
> Thanks!
>=20
> Best regards,
> Fernando
>=20
>=20
>=20
>=20
> -------- Original Message --------
> Subject: New Version Notification for
> draft-gont-6man-deprecate-eui64-based-addresses-00.txt
> Date: Mon, 21 Oct 2013 15:43:46 -0700
> From: internet-drafts@ietf.org
> To: Fernando Gont <fgont@si6networks.com>, Will Liu
> <liushucheng@huawei.com>, Alissa Cooper <acooper@cdt.org>, Dave Thaler
> <dthaler@microsoft.com>
>=20
>=20
> A new version of I-D, =
draft-gont-6man-deprecate-eui64-based-addresses-00.txt
> has been successfully submitted by Fernando Gont and posted to the
> IETF repository.
>=20
> Filename:	 draft-gont-6man-deprecate-eui64-based-addresses
> Revision:	 00
> Title:		 Deprecating EUI-64 Based IPv6 Addresses
> Creation date:	 2013-10-22
> Group:		 Individual Submission
> Number of pages: 6
> URL:
> =
http://www.ietf.org/internet-drafts/draft-gont-6man-deprecate-eui64-based-=
addresses-00.txt
> Status:
> =
http://datatracker.ietf.org/doc/draft-gont-6man-deprecate-eui64-based-addr=
esses
> Htmlized:
> =
http://tools.ietf.org/html/draft-gont-6man-deprecate-eui64-based-addresses=
-00
>=20
>=20
> Abstract:
>   Stateless Address Autoconfiguration (SLAAC) for IPv6 typically
>   results in hosts configuring one or more stable addresses composed =
of
>   a network prefix advertised by a local router, and an Interface
>   Identifier that typically embeds a hardware address (e.g., an IEEE
>   LAN MAC address).  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 scheme to mitigate these issues.
>   This document deprecates the use of hardware addresses in IPv6
>   Interface Identifiers, and recommends the use of an alternative
>   scheme ([I-D.ietf-6man-stable-privacy-addresses]) for the generation
>   of IPv6 stable addresses.
>=20
>=20
>=20
>=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
> The IETF Secretariat
>=20
>=20
>=20
>=20
>=20
> --=20
> Fernando Gont
> e-mail: fernando@gont.com.ar || fgont@si6networks.com
> PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
>=20
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


--Apple-Mail=_F1206046-DFA0-4275-BCF9-1E29BD711C11
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 - http://gpgtools.org

iD8DBQFSaf68bjEdbHIsm0MRAuhwAKD5FlN43TZffQcELXkAofI71J3+mwCfeJtA
AybQGce5OoDSB4KmnnNuvtg=
=GabF
-----END PGP SIGNATURE-----

--Apple-Mail=_F1206046-DFA0-4275-BCF9-1E29BD711C11--

From ayourtch@gmail.com  Thu Oct 24 13:00:44 2013
Return-Path: <ayourtch@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9E8011E839D for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 13:00:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3Dg5jBBP9AGN for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 13:00:44 -0700 (PDT)
Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id ACCBA11E83A9 for <ipv6@ietf.org>; Thu, 24 Oct 2013 13:00:16 -0700 (PDT)
Received: by mail-qc0-f182.google.com with SMTP id n7so1701699qcx.27 for <ipv6@ietf.org>; Thu, 24 Oct 2013 13:00:16 -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 :cc:content-type; bh=5CFsypSBorKig9MEYsyTCsBop41Qo9wpJfIhYACbYZE=; b=EnAE6rZ59rZqq+a7mDa6/18vlzrLxAa3aXW7jWHFfZvSaooJ81iSEA5iLYIxO4aMpP cGlKlkfSTwAd3T8a750FeyzIF0iIhMC54Zev+MHJ91zddztYky7nGEUnxa31BIIHt9Ms seD+oFn0nuVRsxSXnH+i1RHNCa8Xxuu7xDfCFuJL2iEBv7zNlpDWhoClMqVG4saoQjfH +UswGeCsKm/qNGWDteiK1HrPps3iZrQnDoBjA+KEWtVFxi8sTk3TpW4/20D+sQpXu+Oq OqvmaEzus0Ofz6iBQDZuzZaK5u8RkJ+xOrRMe8WD+LPm+IHRo0877B0MNsileoscdsf0 m+mQ==
MIME-Version: 1.0
X-Received: by 10.224.130.72 with SMTP id r8mr6627536qas.32.1382644816057; Thu, 24 Oct 2013 13:00:16 -0700 (PDT)
Received: by 10.96.12.199 with HTTP; Thu, 24 Oct 2013 13:00:16 -0700 (PDT)
In-Reply-To: <014301cece8a$2b780e20$82682a60$@rozanak.com>
References: <014301cece8a$2b780e20$82682a60$@rozanak.com>
Date: Thu, 24 Oct 2013 22:00:16 +0200
Message-ID: <CAPi140PStSx+HDM9rpgVjPed3OFD=gpsXkOdH2HiC7mf350f+Q@mail.gmail.com>
Subject: Re: ra privacy: an improvement to privacy extension plus source code
From: Andrew Yourtchenko <ayourtch@gmail.com>
To: Hosnieh Rafiee <ietf@rozanak.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Thu, 24 Oct 2013 23:54:19 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 24 Oct 2013 20:00:45 -0000

Hi Hosnieh,

I'll reply on-list so it gets into archives - so as to record my
feedback, which is mostly a retransmit of what I wrote in our offline
communication.

I will go over the "problems" that are now distinctly listed in the
introduction, thanks!

"- RFC 4941 specifies the use of EUI-64 to generate the public address
   of node
"

I would not agree with this. 4941 refers to 4862 for generating the
public address, which in turn suggests to use "interface identifier"
when creating a global address, and does not mandate EUI-64 as the
only mechanism (as evidenced in some implementations, namely,
Windows). The 4291, on the other hand, does talk about EUI-64 *format*
but it also specifically mentions the MAC addresses are not necessary
to be used. So, IMHO this is not a problem.

Anyway if the nodes want to use the stable public addresses that are
scan-resistant, there is a draft by Fernando Gont which solves this
problem. I'd rather see you contribute to that one if that solution is
not good enough you think, rather than having yet another fork.

"
   - If the node is changing the physical link, it may keep the IID
   already used on the link it is leaving, to form an IPv6 address on
   the new link using SLAAC.
"

This is a problem I agree is a problem, which has been fixed in some
implementations; and arguably in the other implementations a bug
should be filed "If the prefix changes, the node MUST NOT reuse the
already used temporary IID". But, maybe to fix this bug, an update to
4941 could be useful.

Fernando's draft also specifies that IID of the "stable addresses"
needs to be different on different prefixes, so this problem only
applies to temporary addresses.

"
   - This document is also plan to clarify the interpretation of some
   words used in RFC 4941. One example is a node might nterpret a need
   for the use of a large, stable storage area in which to store each
   newly generated IID. This needs to be done to prevent the generation
   of another currently "in use" value.
"

I read the 4941 and I think it is flexible enough allow oneself to
both shoot oneself in the foot and to make a sane implementation. So I
am not sure this is a valid problem to solve.

Making things fool-proof applies a Darwinian pressure to breed better fools...

"
   - This document also clarifies the use of other algorithm and compare
   it with CGA and DHCPv6 when there is no stable storage available. So
   that the node may be able to make use of a greatly randomized IID
   because, according to section 3.2.2 of RFC 4941, there is nothing to
   force the use of RFC 4086.
"

We had tons of the discussions about the algorithm. I maintain that it
boils down to:

"On each link change, take 64 bits of random data and put it into IID.
Ensure the random data is good quality".

There is a significant body of work on generating good random numbers
and I do not see this draft contributing anything new to it, in this
regard.

So, as I support only 1 portion of the draft out of 4, in general I am
still opposed to it.

--a

On 10/21/13, Hosnieh Rafiee <ietf@rozanak.com> wrote:
> First I would like to thank Andrew for his constructive comments off list.
> I
> tried to address his concerns.
>
>
>
> I wrote a small c++ program that compares ra-privacy with privacy
> extension.
> Before, I submitted a version that only ran on windows OS
> (www.hpi.uni-potsdam.de/fileadmin/hpi/FG_ITS/research/Ipv6/md5_Test.zip ).
> This version works on Linux. I haven't tried it on another OS (FreeBSD ,
> etc). I guess you should try to compile it for other OSs.
>
> You only need to run compare.cpp. It will call the other functions.
>
> http://sourceforge.net/u/hrafiee/raprivacy/ci/master/tree/
>
>
>
> Finally I had a chance to update ra-privacy draft as well. The purpose of
> this draft, if you can still remember :-), is to improve privacy
> deficiencies that exist in Privacy Extension RFC  (RFC 4941) and update it.
> Please share your comments and support the document. I would like to ask
> the
> chair of 6man to assign a timeslot at the upcoming IETF meeting  to discuss
> it further.
>
> http://tools.ietf.org/html/draft-rafiee-6man-ra-privacy
>
>
>
> Thank you,
>
>
>
>
>
> -----------smile----------
>
> Hosnieh
>
> . success is a journey, not a destination..
>
>
>
>

From jeanjour@comcast.net  Thu Oct 24 14:06:41 2013
Return-Path: <jeanjour@comcast.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E526811E822D for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 14:06:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.147
X-Spam-Level: 
X-Spam-Status: No, score=-0.147 tagged_above=-999 required=5 tests=[AWL=0.290,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bBJ1v3K-H0b0 for <ipv6@ietfa.amsl.com>; Thu, 24 Oct 2013 14:06:15 -0700 (PDT)
Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:212]) by ietfa.amsl.com (Postfix) with ESMTP id 0B68811E8237 for <ipv6@ietf.org>; Thu, 24 Oct 2013 14:05:59 -0700 (PDT)
Received: from omta13.westchester.pa.mail.comcast.net ([76.96.62.52]) by qmta14.westchester.pa.mail.comcast.net with comcast id gzeo1m00517dt5G5E95yrl; Thu, 24 Oct 2013 21:05:58 +0000
Received: from [10.0.1.3] ([98.229.211.49]) by omta13.westchester.pa.mail.comcast.net with comcast id h95x1m00814WE023Z95xzv; Thu, 24 Oct 2013 21:05:58 +0000
Mime-Version: 1.0
Message-Id: <a06240804ce8f365bd832@[10.0.1.3]>
In-Reply-To: <52697C33.7010904@gmail.com>
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com> <52697C33.7010904@gmail.com>
Date: Thu, 24 Oct 2013 16:58:37 -0400
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, 6man <ipv6@ietf.org>
From: John Day <jeanjour@comcast.net>
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1382648758; bh=teO6UjN4SOWvOWE428dr7KCqfPVSwuICg3y8uPQbRvo=; h=Received:Received:Mime-Version:Message-Id:Date:To:From:Subject: Content-Type; b=TG2or3zLlRhkr4+o3L6md59Z+DKXFXPswZKv718x/FWxUaPedBDOi89bs4SusPqOh NdwSK3CsAzSt2xjfW9KJwlNCoNHW4rzyaa9SbqQEDWMeNX5IgTwd2CoPPuwK+uYlO2 LFitL/Jfuz6rB4lcaFh4SR81HuTL9rM737H/qldgzQOHXa3/kDP+wMBinzG1ZSd74O 5KHVSygtDy0FM64TcFRJf0nLU9L721dDqOZBzzAuh9oWH1warhcm/0WYyT4XASbCD1 QTnKBh4ijpwQt79Z7YYERuGzLk5BRBUhZVcBOv83rs1oMzZRLbL6PTpDdurKWoI6JK 6Piinn2YoLOdA==
X-Mailman-Approved-At: Thu, 24 Oct 2013 23:54:19 -0700
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 24 Oct 2013 21:06:46 -0000

I couldn't agree with you more, Brian.   This is a really bad idea.

  "Government" should not be trying to protect us from ourselves! 
(Did I hear that on Fox News or was it Rush Limbaugh?)  This is not 
the proper kind of constraints for the IETF to be imposing. 
Information wants to be free!  If some operations manager wants to 
improve the ability of others to trace his traffic and spy on the 
people in his network, he should be allowed to do it.

As for tracing malicious users, that is a bit like the argument that 
if guns are outlawed only outlaws will have guns. Only in this case, 
if we don't outlaw it only the clueless will use MAC Addresses as 
endpoint ids, the "outlaws" aren't that dumb.  I really doubt they 
would use their own MAC addresses, or even to use the same one for 
very long.

Take care,
John Day

At 8:59 AM +1300 10/25/13, Brian E Carpenter wrote:
>Unfortunately I feel that this is operationally unacceptable.
>
>There are many (I suppose thousands) of sites that rely on MAC
>addresses to manage their assets, and in many cases to trace
>malicious users. It's certainly true that in theory, they can do
>this by using ND or DHCPv6 logging, as today they use ARP cache
>or DHCP logging to trace IPv4 users, and they may have to do this
>anyway when some users implement some form of obscure IID generation.
>But I just don't see site managers in general (and therefore vendors)
>accepting this:
>
>"Nodes MUST NOT employ IPv6 address generation schemes that embed the
>  underlying hardware address in the Interface Identifier."
>
>I would suggest that this might fly:
>
>"Nodes SHOULD NOT employ IPv6 address generation schemes that embed the
>  underlying hardware address in the Interface Identifier, and such schemes
>  MUST NOT be enabled by default in any implementation."
>
>Even that might prove unrealistic.
>
>Incidentally, your case would be strengthened by referring to
>draft-ietf-6man-ug, which makes it plain that the case for EUI64
>is weaker than was originally thought.
>
>    Brian
>--------------------------------------------------------------------
>IETF IPv6 working group mailing list
>ipv6@ietf.org
>Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>--------------------------------------------------------------------


From fernando@gont.com.ar  Fri Oct 25 00:40:13 2013
Return-Path: <fernando@gont.com.ar>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52ABE11E825E for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 00:40:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.444
X-Spam-Level: 
X-Spam-Status: No, score=-2.444 tagged_above=-999 required=5 tests=[AWL=0.156,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IPOThRgvSC6n for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 00:40:11 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id A3B7811E81FE for <6man@ietf.org>; Fri, 25 Oct 2013 00:40:11 -0700 (PDT)
Received: from 86-135-17-190.fibertel.com.ar ([190.17.135.86] helo=[192.168.1.118]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fernando@gont.com.ar>) id 1VZc05-00068m-86; Fri, 25 Oct 2013 09:40:05 +0200
Message-ID: <526A204D.8080209@gont.com.ar>
Date: Fri, 25 Oct 2013 04:39:57 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification for draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <8C48B86A895913448548E6D15DA7553BA7A268@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553BA7A268@xmb-rcd-x09.cisco.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "6man@ietf.org" <6man@ietf.org>, "<draft-gont-6man-deprecate-eui64-based-addresses@tools.ietf.org>" <draft-gont-6man-deprecate-eui64-based-addresses@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 07:40:13 -0000

Hi, Fred,

On 10/25/2013 02:16 AM, Fred Baker (fred) wrote:
> IMHO, we don't need to deprecate the address type. It's OK to have 
> it. Deprecating it is a little more difficult than saying "oops",
> it means rethinking the link-local address, which even on
> non-Ethernet links stupidly presumes the presence of a MAC address
> and has no alternative.

draft-ietf-6man-stable-privacy-addresses can be used for those... and
is albeit a more general scheme that can be still be employed if the
underlying interface doesn't have a MAC address.


> At most, we need to say that the use of EUI-64 addresses is
> optional.

You mean the advice should be "SHOULD do
draft-ietf-6man-stable-privacy-addresses but MAY do Modified EUI-64"?
or something else?

Me, I'd say that the propoer advice would seem to be "SHOULD NOT do
EUI-64", thus meaning that you can do it if you have a very good
reason to.

I don't personally bother if Modified EUI-64 is an option, as long as
it's not the default option (and as long as the consequences are
understood when overriding a more sane default).


> Speaking for myself, I personally don't see the value of forcing a
> 64 bit IID on a LAN type that uses 48 bit MAC addresses anyway.

Given that MAC address duplication is a fact, and that the
implications of embedding MAC addresses in the IID are well-known, I'm
not sure why the length of the underlying addresses should affect the
IPv6 subnet size. It results in less flexibility with no obvious gain
(but yes, subnet size is unrelated to this ID, and I understand it's a
controversial topic for some).

Thanks!

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




From fgont@si6networks.com  Fri Oct 25 00:40:18 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A82DD21E808A for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 00:40:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.003
X-Spam-Level: 
X-Spam-Status: No, score=-2.003 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, J_CHICKENPOX_22=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZWeaHx49wbmX for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 00:40:18 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id D6C1311E8115 for <ipv6@ietf.org>; Fri, 25 Oct 2013 00:40:17 -0700 (PDT)
Received: from 86-135-17-190.fibertel.com.ar ([190.17.135.86] helo=[192.168.1.118]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1VZc0G-0006FK-3l; Fri, 25 Oct 2013 09:40:16 +0200
Message-ID: <526A1D22.2090407@si6networks.com>
Date: Fri, 25 Oct 2013 04:26:26 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>,  Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com>	<52697C33.7010904@gmail.com> <CAKD1Yr1nNa8nBMYeyUVcmpLb6buwHFCD4LGq9xbVpde83a0QTw@mail.gmail.com>
In-Reply-To: <CAKD1Yr1nNa8nBMYeyUVcmpLb6buwHFCD4LGq9xbVpde83a0QTw@mail.gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 6man <ipv6@ietf.org>, draft-gont-6man-deprecate-eui64-based-addresses@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 07:40:18 -0000

On 10/25/2013 02:13 AM, Lorenzo Colitti wrote:
> It's also a major implementation burden. Take Linux as an example, Linux
> has an in-kernel implementation of autoconf.
> draft-ietf-6man-stable-privacy-addresses cannot, realistically, be
> implemented in kernel space because it requires stable storage.

I assume that you're referring to stable storage for storing the secret key?


> Thus, if
> we disallow EUI-64 addresses, we:

There's a Linux implementation underway.


> 1. Add an extra barrier to IPv6 adoption because someone has to write a
> userspace implementation (or more than one, due to licensing issues),
> and OS distributors must include that implementation (which is always a
> harder sell than something that's built in).

I don't follow. This document is not even being published *now* as an
RFC. It could easily take it one-two years before it is published as an RFC.

ANy update that you do to a protocol will take time to be implement.
What's the problem?


> 2. Increase the footprint of embedded devices that use Linux, because
> now they need both the kernel implementation (which is extremely
> unlikely to be removed due to backward compatibility concerns, no matter
> what the IETF says), and the userspace implementation.

If anything, in that case you could say that you have a valid reason to
not follow the advice in this document. (assuming we change the "MUST
NOT" to "SHOULD NOT" as suggested by other folks).

That said, I wonder what you have in mind when you say "embedded Linux",
since for many of such devices this would be a no-brainer. For example,
a CPE or TV contans and runs stuff that is orders of magnitude more
complex, bigger, etc., than this.



> In case you think that Linux doesn't matter, bear in mind that a
> substantial percentage of mobile devices (and probably the majority of
> smartphones/tablets) are Linux-based.

Linux does matter. As noted above, a Linux implementation is in the
works (and thiis is no coincidence).



> What's the security threat here?  Network activity correlation and
> location tracking aren't an issue if the host implements RFC4941
> temporary addresses. 

That's incorrect. Please check the I-D we wrote with Alissa and Dave.
(Short answer: even if you do RFC4941, IEEE-based addresses are there.
Hence you can still probe them).


> As for scanning and exploitation, can those be
> avoided simply by blocking incoming connections to ff:fe addresses?

Again, check the I-D we wrote with Alissa and Dave: you can still be
discovered even if you employ a local firewall. e.g., the local router
will respond to "ICMPv6 address unreachable" vs no response).



> Finally: some environments (e.g., enterprises) which already block
> incoming scans might appreciate having predictable IPv6 addresses
> assigned to their hosts, especially if they already have a database of
> all the MAC addresses assigned to their devices. In that case, they can
> simply generate AAAA records deterministically without having to run
> DHCP or dynamic DNS or anything.

And this scheme breaks if you replace a NIC, or if you use Windows, etc.
-- do you consider *this* to be operationally acceptable?



> So I don't think this is a worthwhile tradeoff.

There's really no tradeoff here, because there's no much to gain from
having the MAC address in the IID. The property that you care about is
address stability, rather than using a universaly unique identifier in
the IID.

The security and privacy implications of this have been understood for a
while (that's why Microsoft did sometihng else), and are discussed in
detail in draft-ietf-6man-ipv6-address-generation-privacy.

I'm kind of puzzled that in the light of the whole NSA/Snowden drama
we're still discussing why we should be concerned about having a
globally-unique identifier in the IID.

Such IIDs allow location tracking by any soul (;-) ) that can record an
IPv6 address. (besides the other implications discussed in Alissa's ID)

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





From simon.perreault@viagenie.ca  Fri Oct 25 00:52:06 2013
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1544B11E8115 for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 00:52:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z7IDMO8MwkUn for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 00:52:05 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 9D4BE11E82BB for <ipv6@ietf.org>; Fri, 25 Oct 2013 00:52:05 -0700 (PDT)
Received: from [IPv6:::1] (unknown [IPv6:2001:660:3001:4012:50b3:5fc6:1c4d:60c0]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 00D744021C for <ipv6@ietf.org>; Fri, 25 Oct 2013 03:52:03 -0400 (EDT)
Message-ID: <526A2323.5060604@viagenie.ca>
Date: Fri, 25 Oct 2013 09:52:03 +0200
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com>	<52697C33.7010904@gmail.com>	<a06240804ce8f365bd832@[10.0.1.3]>	<5269936F.7020705@gmail.com>	<E9BB1094-64E9-4219-B801-7205D2B0A1E4@ecs.soton.ac.uk>	<EMEW3|caa096f62332b0b87f0053a710e89364p9NN1V03tjc|ecs.soton.ac.uk|E9BB1094-64E9-4219-B801-7205D2B0A1E4@ecs.soton.ac.uk>	<5269B3FB.8080007@gmail.com>	<76A6422A-EEE4-4C87-9505-ABDC04063621@ecs.soton.ac.uk>	<EMEW3|abf1cccb479ec105214e7466c7c3a9e6p9O11y03tjc|ecs.soton.ac.uk|76A6422A-EEE4-4C87-9505-ABDC04063621@ecs.soton.ac.uk>	<5D36713D8A4E7348A7E10DF7437A4B923AD4D6E5@nkgeml512-mbx.china.huawei.com> <5269CB80.3050103@si6networks.com>
In-Reply-To: <5269CB80.3050103@si6networks.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 07:52:06 -0000

Le 2013-10-25 03:38, Fernando Gont a écrit :
> What I'm sensing both on-list and off-list is that folks are fine with
> "SHOULD NOT". So it all looks like we'll be updating the I-D accordingly.

What would make most sense to me is a recommendation saying that a host
should not generate EUI-64 based addresses *by default*. IMHO it's fine
for e.g. a sysadmin to turn it on on the machines it administers, but
there really is no reason for my mother's PC to have an EUI-64 based
address.

Simon

From simon.perreault@viagenie.ca  Fri Oct 25 00:54:03 2013
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12A8E11E82BE for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 00:54:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JqVivrTyYju2 for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 00:54:02 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id A66DB11E8115 for <ipv6@ietf.org>; Fri, 25 Oct 2013 00:54:02 -0700 (PDT)
Received: from [IPv6:::1] (unknown [IPv6:2001:660:3001:4012:50b3:5fc6:1c4d:60c0]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 17CAA4021C for <ipv6@ietf.org>; Fri, 25 Oct 2013 03:54:01 -0400 (EDT)
Message-ID: <526A2399.3020109@viagenie.ca>
Date: Fri, 25 Oct 2013 09:54:01 +0200
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com>	<52697C33.7010904@gmail.com> <a06240804ce8f365bd832@[10.0.1.3]>	<5269936F.7020705@gmail.com>	<E9BB1094-64E9-4219-B801-7205D2B0A1E4@ecs.soton.ac.uk>	<EMEW3|caa096f62332b0b87f0053a710e89364p9NN1V03tjc|ecs.soton.ac.uk|E9BB1094-64E9-4219-B801-7205D2B0A1E4@ecs.soton.ac.uk>	<5269B3FB.8080007@gmail.com>	<76A6422A-EEE4-4C87-9505-ABDC04063621@ecs.soton.ac.uk>	<EMEW3|abf1cccb479ec105214e7466c7c3a9e6p9O11y03tjc|ecs.soton.ac.uk|76A6422A-EEE4-4C87-9505-ABDC04063621@ecs.soton.ac.uk>	<5D36713D8A4E7348A7E10DF7437A4B923AD4D6E5@nkgeml512-mbx.china.huawei.com>	<5269CB80.3050103@si6networks.com> <5D36713D8A4E7348A7E10DF7437A4B923AD4D760@nkgeml512-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AD4D760@nkgeml512-mbx.china.huawei.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 07:54:03 -0000

Le 2013-10-25 04:21, Sheng Jiang a écrit :
> My understanding is that published RFC would take influence on all
> current implementations, not only future devices. If IETF published a
> RFC deprecate eui64-based IPv6 addresses, it means all current
> implementations need to be modified too.

On all IPv6 OS stacks I know it would be a trivial change. Not an
issue IMHO.

Simon

From lorenzo@google.com  Fri Oct 25 01:27:05 2013
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1976811E82C9 for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 01:27:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.619
X-Spam-Level: 
X-Spam-Status: No, score=-1.619 tagged_above=-999 required=5 tests=[AWL=-0.242, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_22=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oWW2XbV0vP9T for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 01:27:04 -0700 (PDT)
Received: from mail-ie0-x22f.google.com (mail-ie0-x22f.google.com [IPv6:2607:f8b0:4001:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id C236E11E82D9 for <ipv6@ietf.org>; Fri, 25 Oct 2013 01:26:37 -0700 (PDT)
Received: by mail-ie0-f175.google.com with SMTP id aq17so5729420iec.20 for <ipv6@ietf.org>; Fri, 25 Oct 2013 01:26: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=kAdIc3yIKFeoyTEbHJflnGTHMRYL/V7V94IXPCAOYeo=; b=M20JL7ZCK7wLDsFQ0/7QmotWec4nc1fssMS35/D2Rz59S5DmqEuMa0CCD1uussQJ+d Zq4Vf0HixM9yiUalmKQzbj/79+x7Rjii3t6jGGsY9wB4amiYDQn48nB4IgVsOZFFjGir aNTrX5na69ICGDQoxIJoR174SFwcmJ/wSyWPJ3EQ782sCFoweR/lWdtxpqa4mWypvIqo L9IbVLwy9pBHKBYCEOyX/Jo73BlgR6p5mEFqWqT0YrH3ytiAFViEkxbA4et3HIElR6ep qpQpRjLV3Adj1PhZ21oNoa4qaLv33HkPy9gDd+8ewLx2n8+wS/KtRSoxmfuU6JCklkyO 004g==
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=kAdIc3yIKFeoyTEbHJflnGTHMRYL/V7V94IXPCAOYeo=; b=Fut7xr4k/UIbUah9noLoL6TxWln2V4t61/DLaqgX5u/3tYn0/LRQzw3tHFJ7WXXXLi ic6h5d4XETmL0st7XFeFQP9DOWDIrKUm1slTL1vNudCkf5RmTpT99h6gnhd/GIriVtSZ qOzhXNTvi5nnr41yA928CTf8bQVnfaVufI8HxABDcGo3VwLAyOtgLHSKqcxMwcImAhfq IoeJbepe/9TpfA0olRud3P0cNEZsf+2GhaqkEOYwNe8NiKE26rzY2QKlUoUssO5aVDQB kXVwQ4oY3sV3Nwr4mzh4hZRzqSa5qCvuC0KoEkF7SredvEgQdWkvnmIDAdfjiqi8ASvm dSdg==
X-Gm-Message-State: ALoCoQkrbccAF43m/bSwA3BlPlmRVUn8fngYDdTz1a0a/I2l2up4MNSd5p3gJSvFMT9l+etd1Z/e8YFvqX5rgsXimShbpezMy1WhJ3YbL/+r7I9CmN0UnWPlF6G+ZX3vL8fQVe4QVbLduLG8gg16BoI1PuKwvcO3v/rAvHLhPR+dtIpk5TiaFQ1j2+wPRXGMRSAlJ2xP9dok
X-Received: by 10.50.114.168 with SMTP id jh8mr1239874igb.6.1382689597163; Fri, 25 Oct 2013 01:26:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.86.106 with HTTP; Fri, 25 Oct 2013 01:26:16 -0700 (PDT)
In-Reply-To: <526A1D22.2090407@si6networks.com>
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com> <52697C33.7010904@gmail.com> <CAKD1Yr1nNa8nBMYeyUVcmpLb6buwHFCD4LGq9xbVpde83a0QTw@mail.gmail.com> <526A1D22.2090407@si6networks.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 25 Oct 2013 17:26:16 +0900
Message-ID: <CAKD1Yr1w=U3fKijOawDhM6mEVDYaoK7QL1aaGzRZO_SdShmCKw@mail.gmail.com>
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=089e01229f86462dd904e98c8230
Cc: 6man <ipv6@ietf.org>, draft-gont-6man-deprecate-eui64-based-addresses@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 08:27:05 -0000

--089e01229f86462dd904e98c8230
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Oct 25, 2013 at 4:26 PM, Fernando Gont <fgont@si6networks.com>wrote:

> > Thus, if we disallow EUI-64 addresses, we:
>

> There's a Linux implementation underway.
>

Userspace or kernel space? What's the license? How many implementations
will be written, and will the kernel implementation be deleted?


> ANy update that you do to a protocol will take time to be implement.
> What's the problem?
>

That you just added an extra hoop to jump through to implement IPv6 in a
host OS. Potential implementers already often say that IPv6 is too complex.


> That said, I wonder what you have in mind when you say "embedded Linux", since
> for many of such devices this would be a no-brainer. For example, a CPE
> or TV contans and runs stuff that is orders of magnitude more complex,
> bigger, etc., than this.
>

And all those CPEs and TVs implement IPv6? If not, why not? Perhaps because
it's code they need to verify and turn on (and possibly write) that they
don't see a need for?


> > As for scanning and exploitation, can those be
>
> avoided simply by blocking incoming connections to ff:fe addresses?
>
> Again, check the I-D we wrote with Alissa and Dave: you can still be
> discovered even if you employ a local firewall. e.g., the local router
> will respond to "ICMPv6 address unreachable" vs no response).
>

Sure, but you can do this in the network. If you drop the packets before
they reach the local router, or on the local router itself, no unreachables
will be generated, and all the off-network attacks go away (assuming the
hosts use RFC4941 addresses).


> > Finally: some environments (e.g., enterprises) which already block
> > incoming scans might appreciate having predictable IPv6 addresses
> > assigned to their hosts, especially if they already have a database of
> > all the MAC addresses assigned to their devices. In that case, they can
> > simply generate AAAA records deterministically without having to run
> > DHCP or dynamic DNS or anything.
>
> And this scheme breaks if you replace a NIC, or if you use Windows, etc.
> -- do you consider *this* to be operationally acceptable?
>

Believe it or not, not all enterprises use Windows. :-)

As for this breaking when you replace a NIC: it's not hard to keep the
database up to date. If you rely on said database of all MAC addresses for
something operationally relevant, then it will be kept up to date.


> There's really no tradeoff here, because there's no much to gain from
> having the MAC address in the IID. The property that you care about is
> address stability, rather than using a universaly unique identifier in
> the IID.
>

There's always a tradeoff between implementation complexity and benefit.


> I'm kind of puzzled that in the light of the whole NSA/Snowden drama
> we're still discussing why we should be concerned about having a
> globally-unique identifier in the IID.
>

I find a statement that users can protect themselves against national
security agencies by obscuring their IPv6 addresses a bit amusing.

--089e01229f86462dd904e98c8230
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Fri, Oct 25, 2013 at 4:26 PM, Fernando Gont <span dir=
=3D"ltr">&lt;<a href=3D"mailto:fgont@si6networks.com" target=3D"_blank">fgo=
nt@si6networks.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div=
 class=3D"gmail_quote">

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">&gt; Thus, if=A0we disallo=
w EUI-64 addresses, we:<br></div></blockquote><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">

<div class=3D"im">
<br>
</div>There&#39;s a Linux implementation underway.<br></blockquote><div><br=
></div><div>Userspace or kernel space? What&#39;s the license? How many imp=
lementations will be written, and will the kernel implementation be deleted=
?</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
<div class=3D"im"><span style=3D"color:rgb(34,34,34)">ANy update that you d=
o to a protocol will take time to be implement.</span><br></div>
What&#39;s the problem?<br></blockquote><div><br></div><div>That you just a=
dded an extra hoop to jump through to implement IPv6 in a host OS. Potentia=
l implementers already often say that IPv6 is too complex.</div><div>=A0</d=
iv>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div class=3D"im"><span style=3D"color:rgb(34,34,34)">That said, I wonder w=
hat you have in mind when you say &quot;embedded Linux&quot;,=A0</span><spa=
n style=3D"color:rgb(34,34,34)">since for many of such devices this would b=
e a no-brainer. For example,=A0</span><span style=3D"color:rgb(34,34,34)">a=
 CPE or TV contans and runs stuff that is orders of magnitude more=A0</span=
><span style=3D"color:rgb(34,34,34)">complex, bigger, etc., than this.</spa=
n></div>

</blockquote><div><br></div><div>And all those CPEs and TVs implement IPv6?=
 If not, why not? Perhaps because it&#39;s code they need to verify and tur=
n on (and possibly write) that they don&#39;t see a need for?</div><div>

=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">
<div class=3D"im">&gt; As for scanning and exploitation, can those be<br></=
div></blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"im">
&gt; avoided simply by blocking incoming connections to ff:fe addresses?<br=
>
<br>
</div>Again, check the I-D we wrote with Alissa and Dave: you can still be<=
br>
discovered even if you employ a local firewall. e.g., the local router<br>
will respond to &quot;ICMPv6 address unreachable&quot; vs no response).<br>=
</blockquote><div><br></div><div>Sure, but you can do this in the network. =
If you drop the packets before they reach the local router, or on the local=
 router itself, no unreachables will be generated, and all the off-network =
attacks go away (assuming the hosts use RFC4941 addresses).</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
<div class=3D"im">&gt; Finally: some environments (e.g., enterprises) which=
 already block<br>
&gt; incoming scans might appreciate having predictable IPv6 addresses<br>
&gt; assigned to their hosts, especially if they already have a database of=
<br>
&gt; all the MAC addresses assigned to their devices. In that case, they ca=
n<br>
&gt; simply generate AAAA records deterministically without having to run<b=
r>
&gt; DHCP or dynamic DNS or anything.<br>
<br>
</div>And this scheme breaks if you replace a NIC, or if you use Windows, e=
tc.<br>
-- do you consider *this* to be operationally acceptable?<br></blockquote><=
div><br></div><div>Believe it or not, not all enterprises use Windows. :-)<=
/div><div><br></div><div>As for this breaking when you replace a NIC: it&#3=
9;s not hard to keep the database up to date. If you rely on said database =
of all MAC addresses for something operationally relevant, then it will be =
kept up to date.</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
<div class=3D"im"><span style=3D"color:rgb(34,34,34)">There&#39;s really no=
 tradeoff here, because there&#39;s no much to gain from</span><br></div>
having the MAC address in the IID. The property that you care about is<br>
address stability, rather than using a universaly unique identifier in<br>
the IID.<br></blockquote><div><br></div><div>There&#39;s always a tradeoff =
between implementation complexity and benefit.</div><div>=A0</div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex">

I&#39;m kind of puzzled that in the light of the whole NSA/Snowden drama<br=
>
we&#39;re still discussing why we should be concerned about having a<br>
globally-unique identifier in the IID.<br></blockquote><div><br></div><div>=
I find a statement that users can protect themselves against national secur=
ity agencies by obscuring their IPv6 addresses a bit amusing.</div></div>

</div></div>

--089e01229f86462dd904e98c8230--

From hannes@stressinduktion.org  Fri Oct 25 01:42:48 2013
Return-Path: <hannes@stressinduktion.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9510E11E82F2 for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 01:42:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sDL3XqDKoU4p for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 01:42:40 -0700 (PDT)
Received: from order.stressinduktion.org (order.stressinduktion.org [87.106.68.36]) by ietfa.amsl.com (Postfix) with ESMTP id 7E4CC11E815A for <ipv6@ietf.org>; Fri, 25 Oct 2013 01:42:40 -0700 (PDT)
Received: by order.stressinduktion.org (Postfix, from userid 500) id 2B68A1A0C2A6; Fri, 25 Oct 2013 10:42:36 +0200 (CEST)
Date: Fri, 25 Oct 2013 10:42:36 +0200
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
Message-ID: <20131025084236.GD23937@order.stressinduktion.org>
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com> <52697C33.7010904@gmail.com> <CAKD1Yr1nNa8nBMYeyUVcmpLb6buwHFCD4LGq9xbVpde83a0QTw@mail.gmail.com> <526A1D22.2090407@si6networks.com> <CAKD1Yr1w=U3fKijOawDhM6mEVDYaoK7QL1aaGzRZO_SdShmCKw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CAKD1Yr1w=U3fKijOawDhM6mEVDYaoK7QL1aaGzRZO_SdShmCKw@mail.gmail.com>
Cc: Fernando Gont <fgont@si6networks.com>, 6man <ipv6@ietf.org>, draft-gont-6man-deprecate-eui64-based-addresses@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 08:42:48 -0000

Hi!

On Fri, Oct 25, 2013 at 05:26:16PM +0900, Lorenzo Colitti wrote:
> On Fri, Oct 25, 2013 at 4:26 PM, Fernando Gont <fgont@si6networks.com>wrote:
> 
> > > Thus, if we disallow EUI-64 addresses, we:
> >
> 
> > There's a Linux implementation underway.
> >
> 
> Userspace or kernel space? What's the license? How many implementations
> will be written, and will the kernel implementation be deleted?

I started the implementation and strive to get it accepted into the
upstream kernel. I started with a kernel implementation and currently
am hanging on the exact issue on how to handle the installtion generated
secret. For testing I just used the kernel command line but this is not
acceptable as a general solution.

Maybe a compile time switch would be acceptable for the transition to
this new scheme, I don't know and have to consult the NetworkManager
people how to proceed on this and to get them installed as soon as
possible. Unfortunately I had no time to do so, yet.

Greetings,

  Hannes


From fgont@si6networks.com  Fri Oct 25 01:55:46 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 367EB11E82FC for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 01:55:46 -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=-2.599, J_CHICKENPOX_22=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m-qaTS10ouWN for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 01:55:45 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 32B3A11E8353 for <ipv6@ietf.org>; Fri, 25 Oct 2013 01:55:43 -0700 (PDT)
Received: from 200-081-044-137.wireless.movistar.net.ar ([200.81.44.137] helo=[192.168.43.189]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1VZdBC-00083T-7u; Fri, 25 Oct 2013 10:55:40 +0200
Message-ID: <526A31FA.8080205@si6networks.com>
Date: Fri, 25 Oct 2013 05:55:22 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com> <52697C33.7010904@gmail.com> <CAKD1Yr1nNa8nBMYeyUVcmpLb6buwHFCD4LGq9xbVpde83a0QTw@mail.gmail.com> <526A1D22.2090407@si6networks.com> <CAKD1Yr1w=U3fKijOawDhM6mEVDYaoK7QL1aaGzRZO_SdShmCKw@mail.gmail.com>
In-Reply-To: <CAKD1Yr1w=U3fKijOawDhM6mEVDYaoK7QL1aaGzRZO_SdShmCKw@mail.gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Theo de Raadt <deraadt@cvs.openbsd.org>, 6man <ipv6@ietf.org>, draft-gont-6man-deprecate-eui64-based-addresses@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 08:55:46 -0000

On 10/25/2013 05:26 AM, Lorenzo Colitti wrote:
> On Fri, Oct 25, 2013 at 4:26 PM, Fernando Gont <fgont@si6networks.com
> <mailto:fgont@si6networks.com>> wrote:
> 
>     > Thus, if we disallow EUI-64 addresses, we:
> 
> 
>     There's a Linux implementation underway.
> 
> 
> Userspace or kernel space?

Kernel space


> What's the license? 

Same as the kernel, I'd guess.


> How many implementations
> will be written, and will the kernel implementation be deleted?

what kernel implementation are you asking whether it'll be deleted?



>     ANy update that you do to a protocol will take time to be implement.
>     What's the problem?
> 
> That you just added an extra hoop to jump through to implement IPv6 in a
> host OS. Potential implementers already often say that IPv6 is too complex.

C'mon, Lorenzo. :-) ND itself is way harder to implement than this.
And those who don't want to implement v6 will always find a reason to.

You don't help the current situation if you "buy" their excuses.

Put enough money on the table, and you'll see how v6 turns out to be
easy to implement. :-)



>     That said, I wonder what you have in mind when you say "embedded
>     Linux", since for many of such devices this would be a no-brainer.
>     For example, a CPE or TV contans and runs stuff that is orders of
>     magnitude more complex, bigger, etc., than this.
> 
> And all those CPEs and TVs implement IPv6? If not, why not? Perhaps
> because it's code they need to verify and turn on (and possibly write)
> that they don't see a need for?

Then it's not a footprint problem. Have them implement stable-privacy
rather than the old "embed the mac address", and that's it.

I don't expect the vendor to "see a need", because it's not their
security/privacy that is at stake, and because most folks that buy such
devices don't even know what an IP address is (so implementing this will
not buy them any more customers per-se).



>     > As for scanning and exploitation, can those be
> 
>     > avoided simply by blocking incoming connections to ff:fe addresses?
> 
>     Again, check the I-D we wrote with Alissa and Dave: you can still be
>     discovered even if you employ a local firewall. e.g., the local router
>     will respond to "ICMPv6 address unreachable" vs no response). 
> 
> Sure, but you can do this in the network. If you drop the packets before
> they reach the local router, or on the local router itself, no
> unreachables will be generated, and all the off-network attacks go away
> (assuming the hosts use RFC4941 addresses).

So.. this assumes:

1) all hosts implement RFC4941, and eneable it by default
2) the resulting addresses cannot include the fffe word
3) you have control of the border router, *and* that you can filter
based on a portion of the IPv6 address
4) you won't need incomming connections to your stable addresses

Do you really consider this a realistic assessment?



>     > Finally: some environments (e.g., enterprises) which already block
>     > incoming scans might appreciate having predictable IPv6 addresses
>     > assigned to their hosts, especially if they already have a database of
>     > all the MAC addresses assigned to their devices. In that case,
>     they can
>     > simply generate AAAA records deterministically without having to run
>     > DHCP or dynamic DNS or anything.
> 
>     And this scheme breaks if you replace a NIC, or if you use Windows, etc.
>     -- do you consider *this* to be operationally acceptable?
> 
> Believe it or not, not all enterprises use Windows. :-)
> 
> As for this breaking when you replace a NIC: it's not hard to keep the
> database up to date. If you rely on said database of all MAC addresses
> for something operationally relevant, then it will be kept up to date.

You can do whatever you want, obviously. The question is. should you?



>     I'm kind of puzzled that in the light of the whole NSA/Snowden drama
>     we're still discussing why we should be concerned about having a
>     globally-unique identifier in the IID.
> 
> I find a statement that users can protect themselves against national
> security agencies by obscuring their IPv6 addresses a bit amusing.

That's not what my statement says. It rather says "why one should be
concerned about the NSA allegdly subverting a standardization process
when, being presented with something that has well-known security and
privacy implications, we prefer to ignore the problem".

You don't need the NSA to track you when you advertise yourself in the
very address that you're using.

The problem with the current scheme is that any idiot could leverage it
to track your location by just looking at your address.

PoC: scan6 tool from <http://www.si6networks.com/tools/ipv6toolkit>
("man scan6" for examples).

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





From roland.bless@kit.edu  Fri Oct 25 03:35:45 2013
Return-Path: <roland.bless@kit.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A832011E8177 for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 03:35:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.327
X-Spam-Level: 
X-Spam-Status: No, score=-6.327 tagged_above=-999 required=5 tests=[AWL=-0.078, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o5aMZBBDR9ru for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 03:35:34 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) by ietfa.amsl.com (Postfix) with ESMTP id E1DB311E8135 for <ipv6@ietf.org>; Fri, 25 Oct 2013 03:35:28 -0700 (PDT)
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=vorta.tm.kit.edu) by iramx2.ira.uni-karlsruhe.de with esmtp port 25  id 1VZejf-00057R-4o; Fri, 25 Oct 2013 12:35:20 +0200
Received: from [IPv6:::1] (ip6-localhost [IPv6:::1]) by vorta.tm.kit.edu (Postfix) with ESMTPS id E5A40A80A1E; Fri, 25 Oct 2013 12:35:24 +0200 (CEST)
Message-ID: <526A496C.3080400@kit.edu>
Date: Fri, 25 Oct 2013 12:35:24 +0200
From: "Bless, Roland (TM)" <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>,  Fernando Gont <fgont@si6networks.com>
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com>	<52697C33.7010904@gmail.com> <5269B633.8010802@si6networks.com> <5269D03A.8030809@gmail.com>
In-Reply-To: <5269D03A.8030809@gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1382697320.
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 10:35:45 -0000

Hi Brian,

On 25.10.2013 03:58, Brian E Carpenter wrote:
> I actually think that today, not too many sites have decided how
> to handle this for IPv6, but the decisions whether to use SLAAC
> or DHCPv6, and whether to allow RFC4941 addresses or insist
> on Modified EUI-64, have to be taken as each site rolls out
> IPv6. My guess is that large campus-style sites will not
> allow RFC4941 because they don't have the logging to allow
> a traceback to the user. So they'll either go for stateful

Counter-example:
Here at KIT we have a larger campus site with several thousand
users and more than 500 wireless access points. IPv6 w/ SLAAC is on
in the 802.1x protected network and AFAIK they do some logging
to being able to match IPv6 and MAC address in case of abuse etc.
If interested I could try to get the detailed numbers..

BR,
 Roland


From lorenzo@google.com  Fri Oct 25 03:44:20 2013
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 281CC11E8131 for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 03:44:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[AWL=0.076,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sFtIg+RKi9aJ for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 03:44:19 -0700 (PDT)
Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id CC5C711E82F2 for <ipv6@ietf.org>; Fri, 25 Oct 2013 03:44:15 -0700 (PDT)
Received: by mail-ie0-f178.google.com with SMTP id x13so6242039ief.9 for <ipv6@ietf.org>; Fri, 25 Oct 2013 03:44:15 -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=yC3Di724htCcnZ0zdk/WNwy6rGyq7PiJpHukDnxtJV0=; b=KnPQZC0kV8VQh392gka/rN4g9Pf+qn9xX1CjuTB5gGUnXOmLixSav5GWzwgaZuY2Qd ENmNU3fFW+6YEUMHpvC33z7BqdFXwbcZuTEtMVvnZa4QBuuZ54TJPqltSpLKod/CGw7W V7ffB80qCPivBkxPpK94K5zgX8ANfK8hOm5BYDhY6OOMYHxlZZX3jGMNtj+6ax39RJ1Z HWMESW3l7PdtlzNiHQ18qgW3zym2Mm3CSPuAD4chRC3E4Y0zNfPSV40b0nsKTrFObztt g9D4giPTjL1bdqwBOCf9lRDfK9GT0IX8NF2/WhwUMZNceyEb9m3N6lZy0eew8kcS8SvF 2pDA==
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=yC3Di724htCcnZ0zdk/WNwy6rGyq7PiJpHukDnxtJV0=; b=hJ9fHrJcUyG8+TBJ1QpwocRH/lfFATPiXbE8sekiaOEgm3YeB25OxBp0N6/pxZTOJ6 Uq+oH2nj07qiPzXgx0dFdt8XtcXBfRfjPFiMhvvcGwsye2bap+MUdzAIcw0Cr2saW0Bq RgNc6TP/y6bRboF5+3hwKnGLcisedn2pLY1wuvzA8Zm2uN40rnWSsTiXHojNBZuhGuzp 2EA9z52k29X1JS2/auy2zmxN09k/7Wk8ZNRSd0lS+dmrKLoLLoz3DGu6AAliZbPzuBii r6s8pS5pbGlGM7f4t9pz70xIyBOZfDlSQoI1IwC84QDUnRJ87GBPxkb8FFdBvN7iHuBA /tgQ==
X-Gm-Message-State: ALoCoQm5BLTQKRFXETbKfj1uWCrqYo3ELCIN03Ez1ORRrPQOPbcd7xVB0+BDfGMktsU7VkiwlH+x9BHE0OiIqK2Aw43JK1yOC6n6cjySTk5uHzFyWnT/7LcWtN7UqCgwBQ82VdFncNtdt/jjXZQB+ox2+E/KWGVV3/3BgLQloWDnLjUzNhu/QZFG6CbjMSTjoP5+7rRZEYJp
X-Received: by 10.50.66.163 with SMTP id g3mr1673234igt.20.1382697855024; Fri, 25 Oct 2013 03:44:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.86.106 with HTTP; Fri, 25 Oct 2013 03:43:54 -0700 (PDT)
In-Reply-To: <20131025084236.GD23937@order.stressinduktion.org>
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com> <52697C33.7010904@gmail.com> <CAKD1Yr1nNa8nBMYeyUVcmpLb6buwHFCD4LGq9xbVpde83a0QTw@mail.gmail.com> <526A1D22.2090407@si6networks.com> <CAKD1Yr1w=U3fKijOawDhM6mEVDYaoK7QL1aaGzRZO_SdShmCKw@mail.gmail.com> <20131025084236.GD23937@order.stressinduktion.org>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 25 Oct 2013 19:43:54 +0900
Message-ID: <CAKD1Yr0SMb-pAy2TYA3FVx1CzngwG=nr8w=Rg+g+qh++isHEmg@mail.gmail.com>
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
To: Hannes Frederic Sowa <hannes@stressinduktion.org>
Content-Type: multipart/alternative; boundary=047d7bdca31c7b232004e98e6e6c
Cc: Fernando Gont <fgont@si6networks.com>, 6man <ipv6@ietf.org>, draft-gont-6man-deprecate-eui64-based-addresses@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 10:44:20 -0000

--047d7bdca31c7b232004e98e6e6c
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Oct 25, 2013 at 5:42 PM, Hannes Frederic Sowa <
hannes@stressinduktion.org> wrote:

> I started the implementation and strive to get it accepted into the
> upstream kernel. I started with a kernel implementation and currently
> am hanging on the exact issue on how to handle the installtion generated
> secret. For testing I just used the kernel command line but this is not
> acceptable as a general solution.
>

Would a sysctl / file in /proc/net/ipv6/conf/... work?


> Maybe a compile time switch would be acceptable for the transition to
> this new scheme, I don't know and have to consult the NetworkManager
> people how to proceed on this and to get them installed as soon as
> possible. Unfortunately I had no time to do so, yet.
>

NetworkManager is not used on most Linux hosts though, right? It's used on
distros but not on embedded devices.

--047d7bdca31c7b232004e98e6e6c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Fri, Oct 25, 2013 at 5:42 PM, Hannes Frederic Sowa <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:hannes@stressinduktion.org" target=3D"_=
blank">hannes@stressinduktion.org</a>&gt;</span> wrote:<br><div class=3D"gm=
ail_extra">

<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I started the imp=
lementation and strive to get it accepted into the<br>
upstream kernel. I started with a kernel implementation and currently<br>
am hanging on the exact issue on how to handle the installtion generated<br=
>
secret. For testing I just used the kernel command line but this is not<br>
acceptable as a general solution.<br></blockquote><div><br></div><div>Would=
 a sysctl / file in /proc/net/ipv6/conf/... work?</div><div>=A0</div><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex">


Maybe a compile time switch would be acceptable for the transition to<br>
this new scheme, I don&#39;t know and have to consult the NetworkManager<br=
>
people how to proceed on this and to get them installed as soon as<br>
possible. Unfortunately I had no time to do so, yet.<br></blockquote><div><=
br></div><div>NetworkManager is not used on most Linux hosts though, right?=
 It&#39;s used on distros but not on embedded devices.=A0</div></div></div>

</div>

--047d7bdca31c7b232004e98e6e6c--

From george+ipng@m5p.com  Fri Oct 25 04:09:26 2013
Return-Path: <george+ipng@m5p.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70DC711E8135 for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 04:09:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BVQK43uL5dfz for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 04:09:25 -0700 (PDT)
Received: from mailhost.m5p.com (ip-2-1-0-2.r03.asbnva02.us.ce.gin.ntt.net [IPv6:2001:418:0:5000::16]) by ietfa.amsl.com (Postfix) with ESMTP id 689D711E817A for <ipv6@ietf.org>; Fri, 25 Oct 2013 04:09:20 -0700 (PDT)
Received: from wonderland.m5p.com (localhost [IPv6:::1]) by mailhost.m5p.com (8.14.5/8.14.5) with ESMTP id r9PB8f1r057300 for <ipv6@ietf.org>; Fri, 25 Oct 2013 07:08:46 -0400 (EDT) (envelope-from george+ipng@m5p.com)
Message-ID: <526A5139.5050207@m5p.com>
Date: Fri, 25 Oct 2013 07:08:41 -0400
From: George Mitchell <george+ipng@m5p.com>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com>	<52697C33.7010904@gmail.com>	<a06240804ce8f365bd832@[10.0.1.3]>	<5269936F.7020705@gmail.com>	<E9BB1094-64E9-4219-B801-7205D2B0A1E4@ecs.soton.ac.uk>	<EMEW3|caa096f62332b0b87f0053a710e89364p9NN1V03tjc|ecs.soton.ac.uk|E9BB1094-64E9-4219-B801-7205D2B0A1E4@ecs.soton.ac.uk>	<5269B3FB.8080007@gmail.com>	<76A6422A-EEE4-4C87-9505-ABDC04063621@ecs.soton.ac.uk>	<EMEW3|abf1cccb479ec105214e7466c7c3a9e6p9O11y03tjc|ecs.soton.ac.uk|76A6422A-EEE4-4C87-9505-ABDC04063621@ecs.soton.ac.uk>	<5D36713D8A4E7348A7E10DF7437A4B923AD4D6E5@nkgeml512-mbx.china.huawei.com> <5269CB80.3050103@si6networks.com>
In-Reply-To: <5269CB80.3050103@si6networks.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.73 on 10.100.0.3
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (mailhost.m5p.com [IPv6:::1]); Fri, 25 Oct 2013 07:08:47 -0400 (EDT)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 11:09:26 -0000

On 10/24/13 21:38, Fernando Gont wrote:
> Sheng,
>
> On 10/24/2013 10:06 PM, Sheng Jiang wrote:
>> Agree with Tim and Brian. The reality is this has been widely used in
>> so many implementations.
>
> Isn't that the case with essentially any spec you update?
>
> What we're trying to do here is what should happen when looking
> forward... what devices should be shipping in the future.
>
>
>> We all know how difficult for these
>> implementations to be changed. We have similar experience with IPv6
>> transition - to add IPv6 stack into any one implementations is not
>> difficult. But changing all or most of these implementations takes
>> years.
>
> I don't see that as a problem. Better to get this sort of thing in at
> this point in time, than later.
>
> Besides, if there's anything to gain from the whole Snowden "thing", I
> guess it is to gain the necessary momentum to apply changes that improve
> security/privacy. Clearly, having a device-identifier such as an IEEE
> address in the IPv6 IID does not help security/privacy.
>
>
>> On another side, I do see Fernando's point eui64-based addresses
>> should be used less and less. My suggestion is: instead of
>> "deprecate" and "MUST NOT", use these softer word "Discourage" and
>> "SHOULD NOT". Although these tough word may give out stronger
>> message, people would choose to ignore the message when they feel it
>> is not operable.
>
> What I'm sensing both on-list and off-list is that folks are fine with
> "SHOULD NOT". So it all looks like we'll be updating the I-D accordingly.
>
> Regarding "discourage" vs. "deprecate": Me, I'd have no issues with such
> a change although:
> 1) I'd still like to hear what other folks think about this
> 2) I guess IETF circles are familiar with what "deprecate" means(*), but
> folks would wonder what "discourage" means (i.e., whether it has any
> semantics other than the "colloquial" meaning).
>
> (*) based on recent discussions, it seems that people tend to have
> different views on the details of what "deprecation" means.
>
> Thanks! (and please keep the feedback coming!)
>
I've been using IPv6 on my home network since the KAME patches for
FreeBSD came out (mumble) years ago.  It assigned link-local addresses
for the interfaces that were based on the MAC address, but I never found
them to be of any use.  The addresses I put in my local DNS were static
and arbitrary (prefix::1, prefix::2, prefix::3, etc.), as my network was
too small to need automatic configuration.  Obviously I wasn't the user
being targeted by the specification that required the MAC address/EUI to
be part of the address.  Even so, it seemed silly to make the use of the
hardware identifier mandatory.  And my network has functioned with no
difficulty for many years even though I disobeyed the "requirement."
-- George

From hannes@stressinduktion.org  Fri Oct 25 04:19:13 2013
Return-Path: <hannes@stressinduktion.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23AFB11E8110 for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 04:19:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S4Vh0xXSKCKX for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 04:19:08 -0700 (PDT)
Received: from order.stressinduktion.org (order.stressinduktion.org [87.106.68.36]) by ietfa.amsl.com (Postfix) with ESMTP id 81A7D11E83A6 for <ipv6@ietf.org>; Fri, 25 Oct 2013 04:19:07 -0700 (PDT)
Received: by order.stressinduktion.org (Postfix, from userid 500) id 8BFC61A0C27B; Fri, 25 Oct 2013 13:19:05 +0200 (CEST)
Date: Fri, 25 Oct 2013 13:19:05 +0200
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
Message-ID: <20131025111905.GL23937@order.stressinduktion.org>
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com> <52697C33.7010904@gmail.com> <CAKD1Yr1nNa8nBMYeyUVcmpLb6buwHFCD4LGq9xbVpde83a0QTw@mail.gmail.com> <526A1D22.2090407@si6networks.com> <CAKD1Yr1w=U3fKijOawDhM6mEVDYaoK7QL1aaGzRZO_SdShmCKw@mail.gmail.com> <20131025084236.GD23937@order.stressinduktion.org> <CAKD1Yr0SMb-pAy2TYA3FVx1CzngwG=nr8w=Rg+g+qh++isHEmg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CAKD1Yr0SMb-pAy2TYA3FVx1CzngwG=nr8w=Rg+g+qh++isHEmg@mail.gmail.com>
Cc: Fernando Gont <fgont@si6networks.com>, 6man <ipv6@ietf.org>, draft-gont-6man-deprecate-eui64-based-addresses@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 11:19:13 -0000

On Fri, Oct 25, 2013 at 07:43:54PM +0900, Lorenzo Colitti wrote:
> On Fri, Oct 25, 2013 at 5:42 PM, Hannes Frederic Sowa <
> hannes@stressinduktion.org> wrote:
> 
> > I started the implementation and strive to get it accepted into the
> > upstream kernel. I started with a kernel implementation and currently
> > am hanging on the exact issue on how to handle the installtion generated
> > secret. For testing I just used the kernel command line but this is not
> > acceptable as a general solution.
> >
> 
> Would a sysctl / file in /proc/net/ipv6/conf/... work?

Yes, I guess so. I thought about a netlink api which should give a bit more
flexibility to protect users from accidentally rewriting their secrets and
thus installing new generated addresses.

Some simple user interface for this api could be implemented in iproute2
and NetworkManager could be just another user of this.

> > Maybe a compile time switch would be acceptable for the transition to
> > this new scheme, I don't know and have to consult the NetworkManager
> > people how to proceed on this and to get them installed as soon as
> > possible. Unfortunately I had no time to do so, yet.
> >
> 
> NetworkManager is not used on most Linux hosts though, right? It's used on
> distros but not on embedded devices.

That's correct.

We must also have those addresses up before NetworkManager starts so
that services can bind() to those IPs while boot-up when receiving
RA information. I already thought about seeding this secret from
the initramfs (or we handle the file with the secret as a firmware and
request it from the kernel in-time).

A kernel parameter could then be used to switch off the "old style"
addresses.

Greetings,

  Hannes


From lorenzo@google.com  Fri Oct 25 04:39:40 2013
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CB4611E8321 for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 04:39:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level: 
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[AWL=0.071,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id axoyn3aRoVDh for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 04:39:39 -0700 (PDT)
Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com [IPv6:2607:f8b0:4001:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id 6BC4021F8D62 for <ipv6@ietf.org>; Fri, 25 Oct 2013 04:39:38 -0700 (PDT)
Received: by mail-ie0-f176.google.com with SMTP id u16so6266092iet.35 for <ipv6@ietf.org>; Fri, 25 Oct 2013 04:39:33 -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=zBeXMwdAomb+yVFfRNzP2gUno4NPr4vNDsnKoQlqOA0=; b=TZ0h5JMgR53lXJ7d5vktdj8MsT1t3vGbjlo9wCVXOk3Y9bxBineHHdMhYdL2YcTO+6 YTwCephowiuenZcUwq90qHSX/VP9sCLNjql1EKUj9BLJwwsQYys4snO8rIvJmzMbWqTK dEcIK6uwh9j3OGwysVwRy9aPhoUCltKU689lOI8tH+PqO+mLLmFEeR6WatF2e3w5zIqU bVyP87QQIU52F0ZHCAJGoU45gxjnWivjJEYjxsDfC9Nb1oVbHm1umQ1IWBpSjl64+NXX pHXkvJIO6DlAI0ftZYyiC39YkX0yW4Lj6E0doImvkYdkv6AsB9c4wO12fmOdwWsFpVkA vYgw==
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=zBeXMwdAomb+yVFfRNzP2gUno4NPr4vNDsnKoQlqOA0=; b=fdpBivKzM4x96xujHns/GqNbzNOFht8wg2fSdAjUOBlayryzxD4po9R1zzwTtP9Sry iohDEah+ypdCLlf/6zk1YbGjN7Z+a6UNvEyjTOe3iSNBzE7ZQCuuieMb6SgisAhouIgK 0YwVW1I4wX+Jt3LdJ/8Ifzv1ZR2C1+S/z1R2KJ1qW9QEpLzQLUrPnzeDK9uChFHUMTLl 5O3QLsWZxkK4xXnxTCJnQE4dPeYFmiIzyFsNA1IT1cNLCr8GyXMD4H1eNUcvgk+SopYi xFjPYqTEZ/pTv0VsJvTXzpRkbaHD5f+B39opJAEtmXElJjkACwXpgjy8NNAzog6vgK12 VmnQ==
X-Gm-Message-State: ALoCoQkPVYuP9xXLKtWqVfp0B5tgbcRiYb105Psv0OjauW5B/6CUHhOwXmUk4JnHX6MeLqri2PjUqLCR1pwjRjjsq/8I4/SsW9az4wg+FAUDhiHR96ftvVxuZy2cwHWu7ciDtkJ1/rIVsbgXWBHxoIOlNwo03Bq+8cQAo1hUIUFtb4bW0EZLkRRPjGHI0oqbGTfUgMHfuCd2
X-Received: by 10.50.153.50 with SMTP id vd18mr1828196igb.6.1382701173829; Fri, 25 Oct 2013 04:39:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.86.106 with HTTP; Fri, 25 Oct 2013 04:39:13 -0700 (PDT)
In-Reply-To: <20131025111905.GL23937@order.stressinduktion.org>
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com> <52697C33.7010904@gmail.com> <CAKD1Yr1nNa8nBMYeyUVcmpLb6buwHFCD4LGq9xbVpde83a0QTw@mail.gmail.com> <526A1D22.2090407@si6networks.com> <CAKD1Yr1w=U3fKijOawDhM6mEVDYaoK7QL1aaGzRZO_SdShmCKw@mail.gmail.com> <20131025084236.GD23937@order.stressinduktion.org> <CAKD1Yr0SMb-pAy2TYA3FVx1CzngwG=nr8w=Rg+g+qh++isHEmg@mail.gmail.com> <20131025111905.GL23937@order.stressinduktion.org>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 25 Oct 2013 20:39:13 +0900
Message-ID: <CAKD1Yr0xwmDgnWDJYx25yTGLbnM46zcFPgeqxMirR7V0cBcz4Q@mail.gmail.com>
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
To: Hannes Frederic Sowa <hannes@stressinduktion.org>
Content-Type: multipart/alternative; boundary=089e013a009e4c139204e98f34aa
Cc: Fernando Gont <fgont@si6networks.com>, 6man <ipv6@ietf.org>, draft-gont-6man-deprecate-eui64-based-addresses@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 11:39:40 -0000

--089e013a009e4c139204e98f34aa
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Oct 25, 2013 at 8:19 PM, Hannes Frederic Sowa <
hannes@stressinduktion.org> wrote:

> > Would a sysctl / file in /proc/net/ipv6/conf/... work?
>
> Yes, I guess so. I thought about a netlink api which should give a bit more
> flexibility to protect users from accidentally rewriting their secrets and
> thus installing new generated addresses.
>
> Some simple user interface for this api could be implemented in iproute2
> and NetworkManager could be just another user of this.
>

Seems a bit complicated, though? You'd have to define the netlink
attribute, extension, teach iproute about it, and so on. Also, the IPv6
stack already extensively uses sysctls for configuration.


> We must also have those addresses up before NetworkManager starts so
> that services can bind() to those IPs while boot-up when receiving
> RA information. I already thought about seeding this secret from
> the initramfs (or we handle the file with the secret as a firmware and
> request it from the kernel in-time).
>

Wouldn't it be natural to do this in the distro startup scripts, though?
That way there'd be no dependency on NetworkManager, and it would be
available before any network interfaces were brought up. At its simplest,
the secret could live in an appropriately-protected file on disk; on first
boot the script would seed it with randomness, and at every boot it would
write it into the sysctl. For booting from initramfs, you could simply use
old-style autoconf addresses.


> A kernel parameter could then be used to switch off the "old style"
> addresses.
>

/proc/sys/net/ipv6/conf/{eth0,wlan0,...,default}/autoconf_eui64 ?

--089e013a009e4c139204e98f34aa
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Fri, Oct 25, 2013 at 8:19 PM, Hannes Frederic Sowa <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:hannes@stressinduktion.org" target=3D"_=
blank">hannes@stressinduktion.org</a>&gt;</span> wrote:<br><div class=3D"gm=
ail_extra">

<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"im"=
>&gt; Would a sysctl / file in /proc/net/ipv6/conf/... work?<br>
<br>
</div>Yes, I guess so. I thought about a netlink api which should give a bi=
t more<br>
flexibility to protect users from accidentally rewriting their secrets and<=
br>
thus installing new generated addresses.<br>
<br>
Some simple user interface for this api could be implemented in iproute2<br=
>
and NetworkManager could be just another user of this.<br></blockquote><div=
><br></div><div>Seems a bit complicated, though? You&#39;d have to define t=
he netlink attribute, extension, teach iproute about it, and so on. Also, t=
he IPv6 stack already extensively uses sysctls for configuration.</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
<div class=3D"im"><span style=3D"color:rgb(34,34,34)">We must also have tho=
se addresses up before NetworkManager starts so</span><br></div>
that services can bind() to those IPs while boot-up when receiving<br>
RA information. I already thought about seeding this secret from<br>
the initramfs (or we handle the file with the secret as a firmware and<br>
request it from the kernel in-time).<br></blockquote><div><br></div><div>Wo=
uldn&#39;t it be natural to do this in the distro startup scripts, though? =
That way there&#39;d be no dependency on NetworkManager, and it would be av=
ailable before any network interfaces were brought up. At its simplest, the=
 secret could live in an appropriately-protected file on disk; on first boo=
t the script would seed it with randomness, and at every boot it would writ=
e it into the sysctl. For booting from initramfs, you could simply use old-=
style autoconf addresses.</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">A kernel parameter could then =
be used to switch off the &quot;old style&quot;<br>
addresses.<br></blockquote><div><br></div><div>/proc/sys/net/ipv6/conf/{eth=
0,wlan0,...,default}/autoconf_eui64 ?</div></div></div></div>

--089e013a009e4c139204e98f34aa--

From hannes@stressinduktion.org  Fri Oct 25 04:57:11 2013
Return-Path: <hannes@stressinduktion.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CBF211E8353 for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 04:57:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xV2q3t149-gy for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 04:57:06 -0700 (PDT)
Received: from order.stressinduktion.org (order.stressinduktion.org [87.106.68.36]) by ietfa.amsl.com (Postfix) with ESMTP id 4937111E83C8 for <ipv6@ietf.org>; Fri, 25 Oct 2013 04:56:51 -0700 (PDT)
Received: by order.stressinduktion.org (Postfix, from userid 500) id 023BB1A0C27B; Fri, 25 Oct 2013 13:56:50 +0200 (CEST)
Date: Fri, 25 Oct 2013 13:56:50 +0200
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
Message-ID: <20131025115650.GA9906@order.stressinduktion.org>
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com> <52697C33.7010904@gmail.com> <CAKD1Yr1nNa8nBMYeyUVcmpLb6buwHFCD4LGq9xbVpde83a0QTw@mail.gmail.com> <526A1D22.2090407@si6networks.com> <CAKD1Yr1w=U3fKijOawDhM6mEVDYaoK7QL1aaGzRZO_SdShmCKw@mail.gmail.com> <20131025084236.GD23937@order.stressinduktion.org> <CAKD1Yr0SMb-pAy2TYA3FVx1CzngwG=nr8w=Rg+g+qh++isHEmg@mail.gmail.com> <20131025111905.GL23937@order.stressinduktion.org> <CAKD1Yr0xwmDgnWDJYx25yTGLbnM46zcFPgeqxMirR7V0cBcz4Q@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CAKD1Yr0xwmDgnWDJYx25yTGLbnM46zcFPgeqxMirR7V0cBcz4Q@mail.gmail.com>
Cc: Fernando Gont <fgont@si6networks.com>, 6man <ipv6@ietf.org>, draft-gont-6man-deprecate-eui64-based-addresses@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 11:57:11 -0000

Hello!

On Fri, Oct 25, 2013 at 08:39:13PM +0900, Lorenzo Colitti wrote:
> On Fri, Oct 25, 2013 at 8:19 PM, Hannes Frederic Sowa <
> hannes@stressinduktion.org> wrote:
> 
> > > Would a sysctl / file in /proc/net/ipv6/conf/... work?
> >
> > Yes, I guess so. I thought about a netlink api which should give a bit more
> > flexibility to protect users from accidentally rewriting their secrets and
> > thus installing new generated addresses.
> >
> > Some simple user interface for this api could be implemented in iproute2
> > and NetworkManager could be just another user of this.
> >
> 
> Seems a bit complicated, though? You'd have to define the netlink
> attribute, extension, teach iproute about it, and so on. Also, the IPv6
> stack already extensively uses sysctls for configuration.

I have not yet thought that much about the interface. It well may be that
netlink is too complicated for that job.

> > We must also have those addresses up before NetworkManager starts so
> > that services can bind() to those IPs while boot-up when receiving
> > RA information. I already thought about seeding this secret from
> > the initramfs (or we handle the file with the secret as a firmware and
> > request it from the kernel in-time).
> >
> 
> Wouldn't it be natural to do this in the distro startup scripts, though?
> That way there'd be no dependency on NetworkManager, and it would be
> available before any network interfaces were brought up. At its simplest,
> the secret could live in an appropriately-protected file on disk; on first
> boot the script would seed it with randomness, and at every boot it would
> write it into the sysctl. For booting from initramfs, you could simply use
> old-style autoconf addresses.
> 
> 
> > A kernel parameter could then be used to switch off the "old style"
> > addresses.
> >
> 
> /proc/sys/net/ipv6/conf/{eth0,wlan0,...,default}/autoconf_eui64 ?

This is racy as we can only toggle this from user-space. If we want to
completly abandon eui-64 generated addresses we have to let the kernel know
before that. We enter user-space with LL addresses already installed and may
race with RA announcements.

Also the /proc/sys/net/ipv6/conf/<interface> directories are inherently
racy and people have trouble understanding how the /all/ or /default/
switches overload the interface specific directories.

But it could be a nice addition for testing, yes. But I dislike them as
the main configuration method for that.

Greetings,

  Hannes


From sarikaya2012@gmail.com  Fri Oct 25 07:36:28 2013
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F03811E8153 for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 07:36:13 -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=[AWL=0.435,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6VbiIem1Nuop for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 07:36:06 -0700 (PDT)
Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 965B821E80AC for <ipv6@ietf.org>; Fri, 25 Oct 2013 07:36:05 -0700 (PDT)
Received: by mail-la0-f52.google.com with SMTP id eh20so3181338lab.11 for <ipv6@ietf.org>; Fri, 25 Oct 2013 07:36:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=PwqWWWZzji1R6+3WZpvcYQLfujIkozmAIq2JN5IPIoI=; b=elndD+n4ZAVY/G66zc7xKKV/2mwvRsXt8zTQnWQ8u9t8PL9QY/g/QYTR6kOOUrtzeU Mh0JBQzKBegnCBz1W/gJ13Jn4FBL93Xh2Qkv3Zww9kAyGeCdXUwkytxB9kWo8rMmN9Yr NvvDMmmFguay3l4eTGbSyb0BeMwx4suWLKAEc9L2k6xI+4KOBF3oh1/2MD9ZcwrrLh8I 1COH+j3y/Ek4reSZEwiGWJxlzBArPHj2APLirASVFSqpEIQjfID74NY38avT0BBajrSL VNpvic5zOE5fXUouaND9PIDzyqPBD+gZYeUL2bGeA8LFUHg91eqWNP2nUdAiVTISt8y6 Vucw==
MIME-Version: 1.0
X-Received: by 10.112.89.100 with SMTP id bn4mr2555230lbb.16.1382711764464; Fri, 25 Oct 2013 07:36:04 -0700 (PDT)
Received: by 10.114.98.227 with HTTP; Fri, 25 Oct 2013 07:36:04 -0700 (PDT)
In-Reply-To: <DD9D29B2-CFE4-49A0-9330-70B05CA994AA@gmail.com>
References: <DD9D29B2-CFE4-49A0-9330-70B05CA994AA@gmail.com>
Date: Fri, 25 Oct 2013 09:36:04 -0500
Message-ID: <CAC8QAccdNkF5ZeNvVzbQA3_Ph5qO20bcdmEMXvNQWOXP6vyyEA@mail.gmail.com>
Subject: Re: IETF88 6MAN Agenda
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Bob Hinden <bob.hinden@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c379ec8c37fd04e991abc5
Cc: IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 25 Oct 2013 14:36:28 -0000

--001a11c379ec8c37fd04e991abc5
Content-Type: text/plain; charset=ISO-8859-1

Hi Bob,

I had requested a slot for my draft (rfc4191bis) and there was some
discussion.

Kind regards,

Behcet


On Thu, Oct 24, 2013 at 6:55 PM, Bob Hinden <bob.hinden@gmail.com> wrote:

> The agenda for 6man has been posted at
>
>   http://www.ietf.org/proceedings/88/agenda/agenda-88-6man
>
> We were able to accommodate most requests, but for some new drafts that
> have not had enough discussion, we are starting something new.
>
> For the last 20 minutes of the session we will have four "Speed Talks".
>  These will be limited to five minutes and three slides each.  The prupose
> is to allow the authors to present a quick summary of their proposal to
> generate discussion on the mailing list.
>
> There were a few requests we did not give agenda time to.  There were
> topics that had been presented at earlier 6man session and the chairs did
> not feel that the working group had expressed enough interested to allocate
> another speaking slot.  The authors should see if they can develop interest
> on the mailing list.  We will be contacting each person directly.
>
> Speakers should send a pdf of their slides to the chairs no later than
> Saturday November 2.  The session is at 9am on Monday, so we need to have
> everything uploaded well before the session starts.
>
> Thanks,
> Bob & Ole
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

--001a11c379ec8c37fd04e991abc5
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div>Hi Bob,<br><br></div>I had requested a slot=
 for my draft (rfc4191bis) and there was some discussion.<br><br></div>Kind=
 regards,<br><br></div>Behcet<br></div><div class=3D"gmail_extra"><br><br><=
div class=3D"gmail_quote">
On Thu, Oct 24, 2013 at 6:55 PM, Bob Hinden <span dir=3D"ltr">&lt;<a href=
=3D"mailto:bob.hinden@gmail.com" target=3D"_blank">bob.hinden@gmail.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">
The agenda for 6man has been posted at<br>
<br>
=A0 <a href=3D"http://www.ietf.org/proceedings/88/agenda/agenda-88-6man" ta=
rget=3D"_blank">http://www.ietf.org/proceedings/88/agenda/agenda-88-6man</a=
><br>
<br>
We were able to accommodate most requests, but for some new drafts that hav=
e not had enough discussion, we are starting something new.<br>
<br>
For the last 20 minutes of the session we will have four &quot;Speed Talks&=
quot;. =A0These will be limited to five minutes and three slides each. =A0T=
he prupose is to allow the authors to present a quick summary of their prop=
osal to generate discussion on the mailing list.<br>

<br>
There were a few requests we did not give agenda time to. =A0There were top=
ics that had been presented at earlier 6man session and the chairs did not =
feel that the working group had expressed enough interested to allocate ano=
ther speaking slot. =A0The authors should see if they can develop interest =
on the mailing list. =A0We will be contacting each person directly.<br>

<br>
Speakers should send a pdf of their slides to the chairs no later than Satu=
rday November 2. =A0The session is at 9am on Monday, so we need to have eve=
rything uploaded well before the session starts.<br>
<br>
Thanks,<br>
Bob &amp; Ole<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>

--001a11c379ec8c37fd04e991abc5--

From alexandru.petrescu@gmail.com  Fri Oct 25 09:51:59 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2385811E819F for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 09:51:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.273
X-Spam-Level: 
X-Spam-Status: No, score=-10.273 tagged_above=-999 required=5 tests=[AWL=-0.024, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 86tH817yd-SG for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 09:51:54 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) by ietfa.amsl.com (Postfix) with ESMTP id DAA2421F9CAD for <ipv6@ietf.org>; Fri, 25 Oct 2013 09:51:52 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r9PGppDe018547 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ipv6@ietf.org>; Fri, 25 Oct 2013 18:51:51 +0200
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r9PGppEN013358 for <ipv6@ietf.org>; Fri, 25 Oct 2013 18:51:51 +0200 (envelope-from alexandru.petrescu@gmail.com)
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 r9PGplop017310 for <ipv6@ietf.org>; Fri, 25 Oct 2013 18:51:50 +0200
Message-ID: <526AA1A3.2020009@gmail.com>
Date: Fri, 25 Oct 2013 18:51:47 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com> <52697C33.7010904@gmail.com>
In-Reply-To: <52697C33.7010904@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 16:51:59 -0000

Le 24/10/2013 21:59, Brian E Carpenter a écrit :
> Unfortunately I feel that this is operationally unacceptable.

I agree.

Not only operationally it may prove difficult to upgrade everything from
RFC2464, but all the IPv6-over-foo specs of future deployment may need
to accept it as well.

E.g. will this 48bit prohibition also include prohibiting the 'short'
16bit of 802.15.4?  Or is that less of risk given it's a shorter address
and thus less unique?

(in detail:
it cites [RFC2464] Ethernet, [RFC2467] FDDI, and [RFC2470] Token Ring,
but would one go ammend also other IPv6 over foo documents such as:
RFC2492 ATM,
RFC4944 802.15.4,
RFC5072 PPP using Ethernet hardware IDs,
RFC5692 802.16,
draft-ietf-6lowpan-btle-12,
draft-ietf-6man-6lobac-01,
draft-brandt-6man-lowpanz-02,
IPv6-over-USB unspecified, but using hardware IDs.

and why not the methods of forming IPv6 addresses containing an IPv4 
address which may be related in other ways to other privacy aspects like 
geographical localization.)

Alex

>
> There are many (I suppose thousands) of sites that rely on MAC
> addresses to manage their assets, and in many cases to trace
> malicious users. It's certainly true that in theory, they can do
> this by using ND or DHCPv6 logging, as today they use ARP cache or
> DHCP logging to trace IPv4 users, and they may have to do this anyway
> when some users implement some form of obscure IID generation. But I
> just don't see site managers in general (and therefore vendors)
> accepting this:
>
> "Nodes MUST NOT employ IPv6 address generation schemes that embed the
> underlying hardware address in the Interface Identifier."
>
> I would suggest that this might fly:
>
> "Nodes SHOULD NOT employ IPv6 address generation schemes that embed
> the underlying hardware address in the Interface Identifier, and
> such schemes MUST NOT be enabled by default in any implementation."
>
> Even that might prove unrealistic.
>
> Incidentally, your case would be strengthened by referring to
> draft-ietf-6man-ug, which makes it plain that the case for EUI64 is
> weaker than was originally thought.
>
> Brian
> --------------------------------------------------------------------
>  IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>



From alexandru.petrescu@gmail.com  Fri Oct 25 09:54:52 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9128421E80A5 for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 09:54:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.273
X-Spam-Level: 
X-Spam-Status: No, score=-10.273 tagged_above=-999 required=5 tests=[AWL=-0.024, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ix7ZIzXWdtBF for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 09:54:47 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) by ietfa.amsl.com (Postfix) with ESMTP id 7882221E8082 for <ipv6@ietf.org>; Fri, 25 Oct 2013 09:54:41 -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 r9PGseVQ019388 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ipv6@ietf.org>; Fri, 25 Oct 2013 18:54:40 +0200
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r9PGseIh014156 for <ipv6@ietf.org>; Fri, 25 Oct 2013 18:54:40 +0200 (envelope-from alexandru.petrescu@gmail.com)
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 r9PGsdka018767 for <ipv6@ietf.org>; Fri, 25 Oct 2013 18:54:40 +0200
Message-ID: <526AA24F.6010609@gmail.com>
Date: Fri, 25 Oct 2013 18:54:39 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification for draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar>
In-Reply-To: <52695DDE.70909@gont.com.ar>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 16:54:52 -0000

If we're again at deprecating things one aspect that I'd really like
removed is this 64bit border for SLAAC over Ethernet.

One should be able to do SLAAC over Ethernet (and all its backward
compatible IEEE links) with Interface Identifiers optionally  shorter
than 64bit.

Alex

Le 24/10/2013 19:50, Fernando Gont a écrit :
> Folks,
>
> We have posted a new I-D entitled "Deprecating EUI-64 Based IPv6
> Addresses"
> (http://www.ietf.org/internet-drafts/draft-gont-6man-deprecate-eui64-based-addresses-00.txt).
>
>  It's a spin-off of the work we've been doing on IPv6 addressing
> secuity/privacy considerations
> (draft-ietf-6man-ipv6-address-generation-privacy and
> draft-ietf-6man-stable-privacy-addresses), and the idea had already
> been discussed among several folks mstly off-list and at IETF meeting
> corridors.
>
> Any comments will be appreciated.
>
> Thanks!
>
> Best regards, Fernando
>
>
>
>
> -------- Original Message -------- Subject: New Version Notification
> for draft-gont-6man-deprecate-eui64-based-addresses-00.txt Date: Mon,
> 21 Oct 2013 15:43:46 -0700 From: internet-drafts@ietf.org To:
> Fernando Gont <fgont@si6networks.com>, Will Liu
> <liushucheng@huawei.com>, Alissa Cooper <acooper@cdt.org>, Dave
> Thaler <dthaler@microsoft.com>
>
>
> A new version of I-D,
> draft-gont-6man-deprecate-eui64-based-addresses-00.txt has been
> successfully submitted by Fernando Gont and posted to the IETF
> repository.
>
> Filename:	 draft-gont-6man-deprecate-eui64-based-addresses Revision:
> 00 Title:		 Deprecating EUI-64 Based IPv6 Addresses Creation date:
> 2013-10-22 Group:		 Individual Submission Number of pages: 6 URL:
> http://www.ietf.org/internet-drafts/draft-gont-6man-deprecate-eui64-based-addresses-00.txt
>
>
Status:
> http://datatracker.ietf.org/doc/draft-gont-6man-deprecate-eui64-based-addresses
>
>
Htmlized:
> http://tools.ietf.org/html/draft-gont-6man-deprecate-eui64-based-addresses-00
>
>
>
> Abstract: Stateless Address Autoconfiguration (SLAAC) for IPv6
> typically results in hosts configuring one or more stable addresses
> composed of a network prefix advertised by a local router, and an
> Interface Identifier that typically embeds a hardware address (e.g.,
> an IEEE LAN MAC address).  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 scheme to mitigate
> these issues. This document deprecates the use of hardware addresses
> in IPv6 Interface Identifiers, and recommends the use of an
> alternative scheme ([I-D.ietf-6man-stable-privacy-addresses]) for the
> generation of IPv6 stable addresses.
>
>
>
>
>
> 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 alexandru.petrescu@gmail.com  Fri Oct 25 10:04:15 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D707A11E836B for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 10:04:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.272
X-Spam-Level: 
X-Spam-Status: No, score=-10.272 tagged_above=-999 required=5 tests=[AWL=-0.023, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8GcS12osRyeH for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 10:04:10 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) by ietfa.amsl.com (Postfix) with ESMTP id 6780411E8201 for <ipv6@ietf.org>; Fri, 25 Oct 2013 10:04:10 -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 r9PH48Yp010840 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ipv6@ietf.org>; Fri, 25 Oct 2013 19:04:08 +0200
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r9PH48aS016792 for <ipv6@ietf.org>; Fri, 25 Oct 2013 19:04:08 +0200 (envelope-from alexandru.petrescu@gmail.com)
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 r9PH482u022737 for <ipv6@ietf.org>; Fri, 25 Oct 2013 19:04:08 +0200
Message-ID: <526AA488.3080001@gmail.com>
Date: Fri, 25 Oct 2013 19:04:08 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com>	<52697C33.7010904@gmail.com> <a06240804ce8f365bd832@[10.0.1.3]>	<5269936F.7020705@gmail.com>	<E9BB1094-64E9-4219-B801-7205D2B0A1E4@ecs.soton.ac.uk>	<EMEW3|caa096f62332b0b87f0053a710e89364p9NN1V03tjc|ecs.soton.ac.uk|E9BB1094-64E9-4219-B801-7205D2B0A1E4@ecs.soton.ac.uk>	<5269B3FB.8080007@gmail.com>	<76A6422A-EEE4-4C87-9505-ABDC04063621@ecs.soton.ac.uk>	<EMEW3|abf1cccb479ec105214e7466c7c3a9e6p9O11y03tjc|ecs.soton.ac.uk|76A6422A-EEE4-4C87-9505-ABDC04063621@ecs.soton.ac.uk>	<5D36713D8A4E7348A7E10DF7437A4B923AD4D6E5@nkgeml512-mbx.china.huawei.com>	<5269CB80.3050103@si6networks.com> <5D36713D8A4E7348A7E10DF7437A4B923AD4D760@nkgeml512-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AD4D760@nkgeml512-mbx.china.huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 17:04:16 -0000

Le 25/10/2013 04:21, Sheng Jiang a écrit :
>> Sheng,
>>
>> On 10/24/2013 10:06 PM, Sheng Jiang wrote:
>>> Agree with Tim and Brian. The reality is this has been widely
>>> used in so many implementations.
>>
>> Isn't that the case with essentially any spec you update?
>>
>> What we're trying to do here is what should happen when looking
>> forward... what devices should be shipping in the future.
>
> My understanding is that published RFC would take influence on all
> current implementations, not only future devices. If IETF published
> a RFC deprecate eui64-based IPv6 addresses, it means all current
> implementations need to be modified too.
>
> We could compare to oil-based cars. We should encourage use of
> electronic cars for environment protection. But we cannot enforce
> people to change their current oil-based car. The right message is
> one SHOULD buy electronic car when he change a new car. Even so, it
> should not be "MUST".

I agree and I'd go even further with the comparison.

The initial thought is to encourage people to change their oil-based
cars.  Then we'd advise to do so just when buying a new car.  And wiser
advice is to think twice before doing it, because it may not be that
helpful as one initially thought (well-to-wheel analysis suggestions may
surprise).

Alex

>
> Sheng
>
>>> We all know how difficult for these implementations to be
>>> changed. We have similar experience with IPv6 transition - to
>>> add IPv6 stack into any one implementations is not difficult.
>>> But changing all or most of these implementations takes years.
>>
>> I don't see that as a problem. Better to get this sort of thing in
>> at this point in time, than later.
>>
>> Besides, if there's anything to gain from the whole Snowden
>> "thing", I guess it is to gain the necessary momentum to apply
>> changes that improve security/privacy. Clearly, having a
>> device-identifier such as an IEEE address in the IPv6 IID does not
>> help security/privacy.
>>
>>
>>> On another side, I do see Fernando's point eui64-based addresses
>>>  should be used less and less. My suggestion is: instead of
>>> "deprecate" and "MUST NOT", use these softer word "Discourage"
>>> and "SHOULD NOT". Although these tough word may give out stronger
>>> message, people would choose to ignore the message when they feel
>>> it is not operable.
>>
>> What I'm sensing both on-list and off-list is that folks are fine
>> with "SHOULD NOT". So it all looks like we'll be updating the I-D
>> accordingly.
>>
>> Regarding "discourage" vs. "deprecate": Me, I'd have no issues
>> with such a change although: 1) I'd still like to hear what other
>> folks think about this 2) I guess IETF circles are familiar with
>> what "deprecate" means(*), but folks would wonder what
>> "discourage" means (i.e., whether it has any semantics other than
>> the "colloquial" meaning).
>>
>> (*) based on recent discussions, it seems that people tend to have
>>  different views on the details of what "deprecation" means.
>>
>> Thanks! (and please keep the feedback coming!) -- Fernando Gont
>> SI6 Networks e-mail: fgont@si6networks.com PGP Fingerprint: 6666
>> 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>>
>>
>>
>
> --------------------------------------------------------------------
>  IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>



From sander@steffann.nl  Fri Oct 25 10:09:46 2013
Return-Path: <sander@steffann.nl>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44C1111E831A for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 10:09:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.552
X-Spam-Level: 
X-Spam-Status: No, score=-1.552 tagged_above=-999 required=5 tests=[AWL=-1.048, BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mvfFDPjCg-cw for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 10:09:37 -0700 (PDT)
Received: from mail.sintact.nl (mail.sintact.nl [83.247.10.6]) by ietfa.amsl.com (Postfix) with ESMTP id 2414111E8361 for <ipv6@ietf.org>; Fri, 25 Oct 2013 10:09:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id BE1964A; Fri, 25 Oct 2013 19:09:35 +0200 (CEST)
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 10024) with ESMTP id ENhkW5dlcxRM; Fri, 25 Oct 2013 19:09:26 +0200 (CEST)
Received: from ip212-238-89-84.hotspotsvankpn.com (ip212-238-89-84.hotspotsvankpn.com [212.238.89.84]) by mail.sintact.nl (Postfix) with ESMTPSA id 5D20638; Fri, 25 Oct 2013 19:09:26 +0200 (CEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Subject: Re: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification for draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <526AA24F.6010609@gmail.com>
Date: Fri, 25 Oct 2013 19:09:24 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <138388CE-99F3-4F14-A17B-2D8CB2D55EFA@steffann.nl>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-Mailer: Apple Mail (2.1816)
Cc: "ipv6@ietf.org 6man-wg" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 17:09:46 -0000

Hi,

> If we're again at deprecating things one aspect that I'd really like
> removed is this 64bit border for SLAAC over Ethernet.
>=20
> One should be able to do SLAAC over Ethernet (and all its backward
> compatible IEEE links) with Interface Identifiers optionally  shorter
> than 64bit.

Now *that* would make those poor souls that only get one /64 from their =
ISP very happy :-)

I actually would like to see prefix lengths larger than 64 be supported =
for SLAAC. Is there actually a technical reason that it is not allowed? =
(hardware optimising for /64s come to mind now)  Otherwise I think it =
would be nice to make the specs a bit more flexible and allow it.

Cheers,
Sander


From iesg-secretary@ietf.org  Fri Oct 25 10:23:34 2013
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAB3311E8201; Fri, 25 Oct 2013 10:23:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.498
X-Spam-Level: 
X-Spam-Status: No, score=-102.498 tagged_above=-999 required=5 tests=[AWL=0.102, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AlZfJ4hDSBzv; Fri, 25 Oct 2013 10:23:34 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6227811E831A; Fri, 25 Oct 2013 10:23:33 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: WG Action: Rechartered IPv6 Maintenance (6man)
X-Test-IDTracker: no
X-IETF-IDTracker: 4.81
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131025172333.20763.93712.idtracker@ietfa.amsl.com>
Date: Fri, 25 Oct 2013 10:23:33 -0700
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 17:23:35 -0000

The IPv6 Maintenance (6man) working group in the Internet Area of the
IETF has been rechartered. For additional information please contact the
Area Directors or the WG Chairs.

IPv6 Maintenance (6man)
------------------------------------------------
Current Status: Active WG

Chairs:
  Robert Hinden <bob.hinden@gmail.com>
  Ole Troan <otroan@employees.org>

Assigned Area Director:
  Brian Haberman <brian@innovationslab.net>

Mailing list
  Address: ipv6@ietf.org
  To Subscribe: https://www.ietf.org/mailman/listinfo/ipv6
  Archive: http://www.ietf.org/mail-archive/web/ipv6

Charter:

The 6man working group is responsible for the maintenance, upkeep, and
advancement of the IPv6 protocol specifications and addressing
architecture. It is not chartered to develop major changes or additions
to the IPv6 specifications. The working group will address protocol
limitations/issues discovered during deployment and operation.  It will
also serve as a venue for discussing the proper location for working on
IPv6-related issues within the IETF.

6man is the design authority for extensions and modifications to the 
IPv6 protocol.  The working group may, at its discretion, review any 
document produced in another working group that extends or modifies the 
IPv6 protocol and, in consultation with the responsible ADs of both 
working groups, may recommend to the IESG that 6man working group 
consensus is needed before any of those documents can progress for 
publication.

Milestones:
  Done     - Submit RH0 Deprecation specification to IESG as a Proposed
Standard
  Done     - Submit PPP Compression Negotiation specification to IESG as
a Proposed Standard
  Done     - Determine way forward for ULA-C specification
  Nov 2013 - Resolve open issues with "U/G" bits in Interface Identifiers
  Mar 2014 - Develop approach for IPv6 Fragmentation
  Mar 2014 - Develop approaches for IPv6 Extension Headers (Hop-by-Hop
and Destination)
  Jul 2014 - Plan for advancing core IPv6 core specifications to Internet
Standard



From fgont@si6networks.com  Fri Oct 25 10:36:24 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D949611E817B for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 10:36:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RA+oOskqRY-W for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 10:36:23 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 3C4BE11E8359 for <ipv6@ietf.org>; Fri, 25 Oct 2013 10:36:22 -0700 (PDT)
Received: from [186.134.63.155] (helo=[192.168.0.6]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1VZlJ7-0003lW-5h; Fri, 25 Oct 2013 19:36:21 +0200
Message-ID: <526AAC0F.8020906@si6networks.com>
Date: Fri, 25 Oct 2013 14:36:15 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>, ipv6@ietf.org
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com>	<52697C33.7010904@gmail.com> <526AA1A3.2020009@gmail.com>
In-Reply-To: <526AA1A3.2020009@gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 17:36:24 -0000

On 10/25/2013 01:51 PM, Alexandru Petrescu wrote:
>
> Not only operationally it may prove difficult to upgrade everything from
> RFC2464, but all the IPv6-over-foo specs of future deployment may need
> to accept it as well.

Huh?

Can you elaborate how this affects deployment?

Are you suggesting that we ignore well-known problems?

Are you suggesting that we stick to a feature that allows simple
location tracking?

Or.. maybe you're fine with people deploying IPv6 NAT and that kind of
middle-box to mitigate this sort of thing?

An old-timer (who preferred to remain anonymous) just sent me this off-list:

"You know, the reaction to this personifies what is wrong with the IETF.

Here is a practice that we have known was a bad idea for 30 years and a)
they made the mistake anyway, and b) they won't fix it. "




> and why not the methods of forming IPv6 addresses containing an IPv4
> address which may be related in other ways to other privacy aspects like
> geographical localization.)

Those methods:

* Do not result from SLAAC (hence they are out of the scope of this
document), and/or,

* Are employed by automatic tunneling and have no alternative.

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





From v6ops@globis.net  Fri Oct 25 10:38:37 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3FFB11E8359; Fri, 25 Oct 2013 10:38:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BNoxocoBg6cN; Fri, 25 Oct 2013 10:38:37 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id BD21E11E837F; Fri, 25 Oct 2013 10:38:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 7EB5787007C; Fri, 25 Oct 2013 19:38:11 +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 PzFpEHYhKdgX; Fri, 25 Oct 2013 19:38:11 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 4C26387003F; Fri, 25 Oct 2013 19:38:11 +0200 (CEST)
Message-ID: <526AAC81.3050402@globis.net>
Date: Fri, 25 Oct 2013 19:38:09 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: "Ackermann, Michael" <MAckermann@bcbsm.com>
Subject: Re: [v6ops] Fw: New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-04.txt
References: <20131017032024.5051.20799.idtracker@ietfa.amsl.com> <1381980305.36254.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com> <5263C783.1080001@globis.net> <1382396300.22968.YahooMailNeo@web2801.biz.mail.ne1.yahoo.com> <526616C4.40304@globis.net> <4FC37E442D05A748896589E468752CAA0CA88734@PWN401EA160.ent.corp.bcbsm.com> <52695E3A.9090406@globis.net> <4FC37E442D05A748896589E468752CAA0CA8A36F@PWN401EA160.ent.corp.bcbsm.com>
In-Reply-To: <4FC37E442D05A748896589E468752CAA0CA8A36F@PWN401EA160.ent.corp.bcbsm.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: v6ops WG <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>, "bill.jouris@insidethestack.com" <bill.jouris@insidethestack.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 17:38:38 -0000

> Ackermann, Michael <mailto:MAckermann@bcbsm.com>
> 25 October 2013 01:44
> Ray
>
> Your Comment: 
> No. I think what I said was that the level of certainty in your measurements is dependent on the level of synchronisation of the 2 clock sources if you are calculating a delta of timestamp of clock 1 - timestamp clock 2.
> My Response:
> Then it sounds like we are in agreement.   Given the appropriate stratum level at both nodes, the desired level of time synchronization is achieved. 
>
No. We are not in agreement.

Stratum is an indication of how far down you are in the hierarchy from
any NTP Stratum 0 clock.

It says nothing about whether your stratum 0 and my stratum 0 are
synchronised.

We could both be running caesium clocks, and there could still be an
offset if I don't set my reference time of my caesium clock the same as
your reference time. When talking about microsecond or picosecond timing
that will almost certainly be significant.

You really need to know that the true provenance of the clock source is
identical in order to make PDM 1 calculations, not just the stratum.

Hence my comment to couple some sort of "clock ID" to the timestamp.
> Your Comment: 
> I think it might be instructive to go back and look at high school physics books on making measurements, precision, accuracy, and error estimations, especially when taking the difference of two measurements, or making other calculations on top of raw observations
> My Response:  Not sure exactly what this means but I can say that this sounds like theoretical doubt that time synchronization will not work properly in geographically dispersed environments?    I can tell you that it does in our experiences and that the surrounding protocols/implementations are crafted to account for such vicissitudes.  
> I will say that I have no field experience with DCF-77 sources, only GPS and Cesium.  
>
>
> Your Comment:
> Equally a stratum 0 clock can be free running if it loses it's radio signal.
> My Response: 
> This comment sort of confused me as well, but suffice to say, if any component is broken, results will be impaired.   Obviously this is not limited to the time synch subject.  
>
>
> Finally, your comment about "Middleboxes".    I hope it can be as simple to accommodate as you describe.   My concern is that if there are numerous middleboxes, the fields may get repetitively overlaid, or there will need to be so many separate fields, we could incur excessive complexity or overhead.    Given that we can accomplish this with a workable solution, I am certainly all for it.   
> The more information I can have to manage networks and solve problems, the better!
>
> Thanks again for your thoughts, inputs and questions!
>
> Mike
>
>
>
>
>
>
>
>
>
>
>


From fgont@si6networks.com  Fri Oct 25 10:40:28 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA86B11E81AD for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 10:40:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eAb0aPpSUN0N for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 10:40:28 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 0408411E8359 for <ipv6@ietf.org>; Fri, 25 Oct 2013 10:40:19 -0700 (PDT)
Received: from [186.134.63.155] (helo=[192.168.0.6]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1VZlMw-0003t3-Ln; Fri, 25 Oct 2013 19:40:19 +0200
Message-ID: <526AACA5.7090604@si6networks.com>
Date: Fri, 25 Oct 2013 14:38:45 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>, ipv6@ietf.org
Subject: Re: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification for draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com>
In-Reply-To: <526AA24F.6010609@gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 17:40:28 -0000

On 10/25/2013 01:54 PM, Alexandru Petrescu wrote:
> If we're again at deprecating things one aspect that I'd really like
> removed is this 64bit border for SLAAC over Ethernet.
> 
> One should be able to do SLAAC over Ethernet (and all its backward
> compatible IEEE links) with Interface Identifiers optionally  shorter
> than 64bit.

If there's something else that needs to be fixed, then please:

1) Write an I-D that analyzes the problem, and proposes a workaround, and,

2) start a new thread. :-)

Let's keep this thread on-topic. ;-)

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





From tjc@ecs.soton.ac.uk  Fri Oct 25 12:30:30 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B323811E81C1 for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 12:30:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3JkNoECkIq6s for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 12:30:29 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 0919F11E81B6 for <ipv6@ietf.org>; Fri, 25 Oct 2013 12:30:21 -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 r9PJUJ2K017612;  Fri, 25 Oct 2013 20:30:19 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r9PJUJ2K017612
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1382729420; bh=IWxbR7DRpc6+eupSizr54qId/0U=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=QiAmxKm1UPVoGHSD4FZ7ImW27P7KIdkie8U6pFBYvVjIdCpZiauhJ8Cy7jMjuBAcG fLwwiUvoCSjMXHtVdO3bvO0y/Np9sYO99xWO8fMkX7GToGO7ZZzxTnk7EYBYjx90VL BS1j0G2t3Da1jc+Ou6JQNT4J3p5LIGEius5AXV3g=
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 p9OKUJ0959610014kb ret-id none; Fri, 25 Oct 2013 20:30:19 +0100
Received: from [192.168.1.107] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r9PJUFYa022654 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 25 Oct 2013 20:30:16 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification for draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <526AACA5.7090604@si6networks.com>
Date: Fri, 25 Oct 2013 20:30:15 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.1510)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p9OKUJ095961001400; tid=p9OKUJ0959610014kb; 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: r9PJUJ2K017612
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: Alexandru Petrescu <alexandru.petrescu@gmail.com>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 19:30:30 -0000

On 25 Oct 2013, at 18:38, Fernando Gont <fgont@si6networks.com> wrote:

> On 10/25/2013 01:54 PM, Alexandru Petrescu wrote:
>> If we're again at deprecating things one aspect that I'd really like
>> removed is this 64bit border for SLAAC over Ethernet.
>>=20
>> One should be able to do SLAAC over Ethernet (and all its backward
>> compatible IEEE links) with Interface Identifiers optionally  shorter
>> than 64bit.
>=20
> If there's something else that needs to be fixed, then please:
>=20
> 1) Write an I-D that analyzes the problem, and proposes a workaround, =
and,
>=20
> 2) start a new thread. :-)
>=20
> Let's keep this thread on-topic. ;-)

Well, you're proposing deprecating EUI-64, so there is no longer any =
reason to be constrained to /64.... so your replacement should consider =
the possibility of it being used with longer subnet prefixes at some =
point in the future?

Tim=

From fgont@si6networks.com  Fri Oct 25 12:38:53 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DED2511E81B2 for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 12:38:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kHXFqkDKVagB for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 12:38:52 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 9928711E81CB for <ipv6@ietf.org>; Fri, 25 Oct 2013 12:38:51 -0700 (PDT)
Received: from [186.134.63.155] (helo=[192.168.0.6]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1VZnDd-0006kV-8w; Fri, 25 Oct 2013 21:38:49 +0200
Message-ID: <526AC8AF.4060608@si6networks.com>
Date: Fri, 25 Oct 2013 16:38:23 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification for draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Alexandru Petrescu <alexandru.petrescu@gmail.com>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 19:38:53 -0000

On 10/25/2013 04:30 PM, Tim Chown wrote:
>>> One should be able to do SLAAC over Ethernet (and all its
>>> backward compatible IEEE links) with Interface Identifiers
>>> optionally  shorter than 64bit.
>> 
>> If there's something else that needs to be fixed, then please:
>> 
>> 1) Write an I-D that analyzes the problem, and proposes a
>> workaround, and,
>> 
>> 2) start a new thread. :-)
>> 
>> Let's keep this thread on-topic. ;-)
> 
> Well, you're proposing deprecating EUI-64, so there is no longer any
> reason to be constrained to /64.... 

Is this the sole reason for requiring subnets to be a /64?


> so your replacement should
> consider the possibility of it being used with longer subnet prefixes
> at some point in the future?

It is considered in draft-ietf-6man-stable-privacy-addresses, already
(although it notes that IPv6 are currently required to be 64 bits long)
-- i.e., if the /64 requirement were to change, we're still fine with
draft-ietf-6man-stable-privacy-addresses.

Thanks!

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





From hannes@stressinduktion.org  Fri Oct 25 13:06:46 2013
Return-Path: <hannes@stressinduktion.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFF5F11E81E9 for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 13:06:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JD2Fk0PO4VVj for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 13:06:38 -0700 (PDT)
Received: from order.stressinduktion.org (order.stressinduktion.org [87.106.68.36]) by ietfa.amsl.com (Postfix) with ESMTP id 0AEAE11E8137 for <ipv6@ietf.org>; Fri, 25 Oct 2013 13:06:32 -0700 (PDT)
Received: by order.stressinduktion.org (Postfix, from userid 500) id 3A6CE1A0C27B; Fri, 25 Oct 2013 22:06:30 +0200 (CEST)
Date: Fri, 25 Oct 2013 22:06:30 +0200
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Fernando Gont <fgont@si6networks.com>
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
Message-ID: <20131025200630.GF12895@order.stressinduktion.org>
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com> <52697C33.7010904@gmail.com> <5269B633.8010802@si6networks.com> <5269D03A.8030809@gmail.com> <5269DBBA.8020606@si6networks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <5269DBBA.8020606@si6networks.com>
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 20:06:47 -0000

On Thu, Oct 24, 2013 at 11:47:22PM -0300, Fernando Gont wrote:
> Brian,
> 
> On 10/24/2013 10:58 PM, Brian E Carpenter wrote:
> [...]
> > IPv6. My guess is that large campus-style sites will not
> > allow RFC4941 because they don't have the logging to allow
> > a traceback to the user. So they'll either go for stateful
> > DHCPv6 if they can find working products for all platforms,
> > or stick to SLAAC/EUI-64. The reason is indeed the stable
> > mapping, not the fact that it's bit-for-bit mapping of
> > the MAC address.
> 
> That's the point: we're not deprecating the stable mappings. Just
> improving them.

Are these mappings really stable?

Linux based virtualization does often create interfaces, thus installing
a the addresses and then change the mac address to a stable one from
the virtualization managment engine. So a mapping MAC <=> IPv6 address does
not work very well there.

Greetings,

  Hannes


From tjc@ecs.soton.ac.uk  Fri Oct 25 13:08:25 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0409111E81F5 for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 13:08:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fl4hwREFcAci for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 13:08:24 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 996A311E8200 for <ipv6@ietf.org>; Fri, 25 Oct 2013 13:08:10 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r9PK7rci024048; Fri, 25 Oct 2013 21:07:53 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r9PK7rci024048
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1382731673; bh=HFAVvochTUei30rsDSOGHZzwr/0=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=ffVo1vJpblKS+ZVgK3B5ORKXCNTGreKwVQK9mNWI/ZPMhQ1hUxxATKF1ypBDTW/Yn yodkuFLMLHYWRHCvrLIKDazoUCP+IDZP9SqFWq3ZNbZTVLeaVmeWNhv9C6G5FrQey+ Qf98H6KT3+rmXr3hZgaA0pzcW8+AGhJcUIZhEjvk=
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 p9OL7r0959610156w8 ret-id none; Fri, 25 Oct 2013 21:07:53 +0100
Received: from [192.168.1.107] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r9PK6W3j030242 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 25 Oct 2013 21:06:33 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <5269D03A.8030809@gmail.com>
Date: Fri, 25 Oct 2013 21:06:32 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|6c915c4e4e63530092c3f6edabbf8a7ep9OL7r03tjc|ecs.soton.ac.uk|28EF616C-5765-4D3D-9593-86DE8BB538C5@ecs.soton.ac.uk>
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com> <52697C33.7010904@gmail.com> <5269B633.8010802@si6networks.com> <5269D03A.8030809@gmail.com> <28EF616C-5765-4D3D-9593-86DE8BB538C5@ecs.soton.ac.uk>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1510)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p9OL7r095961015600; tid=p9OL7r0959610156w8; 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: r9PK7rci024048
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: Fernando Gont <fgont@si6networks.com>, 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 20:08:25 -0000

On 25 Oct 2013, at 02:58, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

> On 25/10/2013 13:07, Fernando Gont wrote:
>> On 10/24/2013 04:59 PM, Brian E Carpenter wrote:
>>> Unfortunately I feel that this is operationally unacceptable.
>>>=20
>>> There are many (I suppose thousands) of sites that rely on MAC
>>> addresses to manage their assets, and in many cases to trace
>>> malicious users.=20
>>=20
>> Question:
>>=20
>> Do you argue that they rely on
>> 1) the MAC address being present in the IID, or,
>> 2) the IPv6 address (and hence the IPv6 -> link layer address =
mapping)
>>   being stable?
>=20
> I actually think that today, not too many sites have decided how
> to handle this for IPv6, but the decisions whether to use SLAAC
> or DHCPv6, and whether to allow RFC4941 addresses or insist
> on Modified EUI-64, have to be taken as each site rolls out
> IPv6. My guess is that large campus-style sites will not
> allow RFC4941 because they don't have the logging to allow
> a traceback to the user.

This is not true.  There are open source packages that allow you to =
harvest switch port, MACs, IPs etc, dual-stack.  OK, so the db gets big =
if RFC4941 refresh is rapid, but it works.

How do you prevent 4941 anyway on campus BYOD, if you allow EUI-64?  =
What product does that?

The approach has to be expect anything, and monitor/log it.

Tim=

From rdroms@cisco.com  Fri Oct 25 13:21:22 2013
Return-Path: <rdroms@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAC1211E8152; Fri, 25 Oct 2013 13:21:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KDSb-6Le18vk; Fri, 25 Oct 2013 13:21:16 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id BFD0811E8108; Fri, 25 Oct 2013 13:21:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3820; q=dns/txt; s=iport; t=1382732476; x=1383942076; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=p9lTnSrPdiv2prTRTCaSTLQh4sCVtV0d3koY4fuQ1wk=; b=L+XFUCMTg7x9/duAXO51IAzP0P35V9enMba/oCss574VltlSblDCjTw1 pkBlVvQLHF+JVe8xKnRWWWCOZ6u4+LeVyK2mJ0JHI+6mRpD9Lv2rp/I1F 3F9gwxyYuYm+X1ozt/w4An1qXWXSp01X7yjREzRNyCqLl96QvhwC34aCX c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtcGAL7RalKtJXHA/2dsb2JhbABZgweBDL5IgSMWbQeCJQEBAQMBeQULAgEIEgYKGQshERcOAgQOBQiHbQMJBq9XDYlrjGOCPQIxB4MfgQ0DiQeNGI47hTeBaIE+gio
X-IronPort-AV: E=Sophos;i="4.93,572,1378857600"; d="scan'208";a="276801832"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-8.cisco.com with ESMTP; 25 Oct 2013 20:21:16 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r9PKLG7G011288 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 25 Oct 2013 20:21:16 GMT
Received: from xmb-aln-x04.cisco.com ([169.254.9.229]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.02.0318.004; Fri, 25 Oct 2013 15:21:16 -0500
From: "Ralph Droms (rdroms)" <rdroms@cisco.com>
To: "6man@ietf.org" <6man@ietf.org>
Subject: Re: draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re: [Roll] [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope value of 3 - subnet-local)
Thread-Topic: draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re: [Roll] [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope value of 3 - subnet-local)
Thread-Index: AQHO0b/BbRYL5zf1Mk6G4zsqvD6ovQ==
Date: Fri, 25 Oct 2013 20:21:15 +0000
Message-ID: <4518F39EB578034D8C99A9B7776CDBA301C067D0@xmb-aln-x04.cisco.com>
References: <3599.1381852752@sandelman.ca> <CE82BA46.24343%d.sturek@att.net> <CABOxzu2nLuny5uySEEdb6ji9ucE6xqGZ6DLe-mc6KUqVszNfFg@mail.gmail.com> <525DC6C9.2010808@gridmerge.com> <CABOxzu2apwBRpU1h4mKJwpO+U+Y9Q_q-h5AhZ+hGzAdjdPdmUQ@mail.gmail.com> <525E5064.4050109@gridmerge.com> <CABOxzu0L-EY0iDGpAJ+ER15CPL-3v8F77ewn-G=gZYODixevZg@mail.gmail.com> <3CC8783F-F4DA-47B9-A051-DBBA6EF00C19@gmail.com>
In-Reply-To: <3CC8783F-F4DA-47B9-A051-DBBA6EF00C19@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.44.68.183]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <A05873E7592E9D44B967A8ACFEE5AFEB@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Routing Over Low power and Lossy networks <roll@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 20:21:22 -0000

I think I read consensus from the WG to make the following changes to draft=
-ietf-6man-multicast-scopes, and list the document as "Updates RFC 4007":

*** Add as a new last paragraph in section 2:

   The following change is applied to section 2.7 of RFC 4291:

   OLD:

         Admin-Local scope is the smallest scope that must be
         administratively configured, i.e., not automatically derived
         from physical connectivity or other, non-multicast-related
         configuration.

   NEW:

         Interface-Local, Link-Local, and Realm-Local scope boundaries
         are automatically derived from physical connectivity or
         other, non-multicast related configuration.  Global scope has
         no boundary.  The boundaries of all other non-reserved scopes
         are administratively configured.

*** Add section 3 (and renumber current section 3-5):

3.  Updates to RFC 4007, section 5

   Section 5 of RFC 4007 and section 2.7 of RFC 4291 disagree about the
   way in which multicast scope 3 is configured.  To resolve that disagreem=
ent,
   change the last bullet in the list in section 5 of RFC 4007 as follows:

OLD:

   o  The boundaries of zones of a scope other than interface-local,
      link-local, and global must be defined and configured by network
      administrators.

NEW:

   o  The boundaries of zones of a scope are defined by the IPv6
      addressing architecture [RFC4291].

I haven't seen any discussion of changing Realm-Local to Multilink-Local be=
yond Kerry's initial suggestion and Robert's support of the change.

- Ralph

On Oct 17, 2013, at 12:10 PM 10/17/13, Ralph Droms <rdroms.ietf@gmail.com> =
wrote:

> Kerry correctly points out that RFC 4007 and RFC 4291 are in conflict reg=
arding the way in which multicast scope 3 is defined:
>=20
> RFC 4007, section 5:
>=20
>   o  The boundaries of zones of a scope other than interface-local,
>      link-local, and global must be defined and configured by network
>      administrators.
>=20
> RFC 4291, section 2.7:
>=20
>         Admin-Local scope is the smallest scope that must be
>         administratively configured, i.e., not automatically derived
>         from physical connectivity or other, non-multicast-related
>         configuration.
>=20
> Noting this conflict, I propose adding a bit of text to draft-ietf-6man-m=
ulticast-scopes to update RFC 4007 for consistency with RFC 4291:
>=20
> Add section 3 (and renumber current section 3-5):
>=20
> 3.  Updates to RFC 4007, section 5
>=20
>   Section 5 of RFC 4007 and section 2.7 of RFC 4291 disagree about the
>   way in which multicast scope 3 is configured.  To resolve that disagree=
ment,
>   change the last bullet in the list in section 5 of RFC 4007 as follows:
>=20
> OLD:
>=20
>   o  The boundaries of zones of a scope other than interface-local,
>      link-local, and global must be defined and configured by network
>      administrators.
>=20
> NEW:
>=20
>   o  Admin-Local scope is the smallest scope that must be
>      administratively configured, i.e., not automatically derived
>      from physical connectivity or other, non-multicast-related
>      configuration.
>=20
> Looking for consensus in the 6man WG before I make this change...
>=20
> - Ralph
>=20
> On Oct 16, 2013, at 10:04 AM 10/16/13, Kerry Lynn <kerlyn@ieee.org> wrote=
:
>=20
>> [...]
>=20
>> I think Ralph's approach is the correct one.  His draft-droms-6man-multi=
cast-scopes belongs in
>> 6man as it re-defines a reserved code point in the IPv6 addressing archi=
tecture.  It nominally
>> updates RFC 4291 but should probably also update RFC 4007 as these RFCs =
are in conflict
>> regarding the automatic definition of scope 0x03.
> [...]
>=20


From dthaler@microsoft.com  Fri Oct 25 13:39:07 2013
Return-Path: <dthaler@microsoft.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A81DB11E8208; Fri, 25 Oct 2013 13:39:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.63
X-Spam-Level: 
X-Spam-Status: No, score=-103.63 tagged_above=-999 required=5 tests=[AWL=-0.031, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fdEMBgvehcYt; Fri, 25 Oct 2013 13:39:03 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1lp0154.outbound.protection.outlook.com [207.46.163.154]) by ietfa.amsl.com (Postfix) with ESMTP id 3411711E8190; Fri, 25 Oct 2013 13:38:46 -0700 (PDT)
Received: from BY2PR03MB269.namprd03.prod.outlook.com (10.242.37.11) by BY2PR03MB270.namprd03.prod.outlook.com (10.242.37.12) with Microsoft SMTP Server (TLS) id 15.0.800.7; Fri, 25 Oct 2013 20:38:44 +0000
Received: from BY2PR03MB269.namprd03.prod.outlook.com ([169.254.5.163]) by BY2PR03MB269.namprd03.prod.outlook.com ([169.254.5.31]) with mapi id 15.00.0800.005; Fri, 25 Oct 2013 20:38:44 +0000
From: Dave Thaler <dthaler@microsoft.com>
To: "Ralph Droms (rdroms)" <rdroms@cisco.com>, "6man@ietf.org" <6man@ietf.org>
Subject: RE: draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re: [Roll] [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope	value of 3 - subnet-local)
Thread-Topic: draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re: [Roll] [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope	value of 3 - subnet-local)
Thread-Index: AQHO0b/UxrZjYDMCZkmp4wiEoc30O5oF4HVA
Date: Fri, 25 Oct 2013 20:38:43 +0000
Message-ID: <1daea916972b4e60be575e5f5276cb78@BY2PR03MB269.namprd03.prod.outlook.com>
References: <3599.1381852752@sandelman.ca> <CE82BA46.24343%d.sturek@att.net> <CABOxzu2nLuny5uySEEdb6ji9ucE6xqGZ6DLe-mc6KUqVszNfFg@mail.gmail.com> <525DC6C9.2010808@gridmerge.com> <CABOxzu2apwBRpU1h4mKJwpO+U+Y9Q_q-h5AhZ+hGzAdjdPdmUQ@mail.gmail.com> <525E5064.4050109@gridmerge.com> <CABOxzu0L-EY0iDGpAJ+ER15CPL-3v8F77ewn-G=gZYODixevZg@mail.gmail.com> <3CC8783F-F4DA-47B9-A051-DBBA6EF00C19@gmail.com> <4518F39EB578034D8C99A9B7776CDBA301C067D0@xmb-aln-x04.cisco.com>
In-Reply-To: <4518F39EB578034D8C99A9B7776CDBA301C067D0@xmb-aln-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:4898:80e8:ee31::3]
x-forefront-prvs: 0010D93EFE
x-forefront-antispam-report: SFV:NSPM; SFS:(479174003)(377454003)(13464003)(189002)(199002)(51704005)(24454002)(31966008)(74502001)(69226001)(51856001)(59766001)(46102001)(77982001)(74316001)(76482001)(54316002)(56776001)(47976001)(79102001)(74662001)(47446002)(54356001)(4396001)(63696002)(33646001)(76576001)(76786001)(77096001)(76796001)(56816003)(49866001)(53806001)(47736001)(50986001)(81542001)(81342001)(65816001)(80022001)(15975445006)(74876001)(19580395003)(19580405001)(83322001)(81816001)(74706001)(81686001)(80976001)(74366001)(85306002)(83072001)(24736002)(3826001); DIR:OUT; SFP:; SCL:1; SRVR:BY2PR03MB270; H:BY2PR03MB269.namprd03.prod.outlook.com; CLIP:2001:4898:80e8:ee31::3; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
Cc: Routing Over Low power and Lossy networks <roll@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 20:39:07 -0000

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> Ralph Droms (rdroms)
> Sent: Friday, October 25, 2013 1:21 PM
> To: 6man@ietf.org
> Cc: Routing Over Low power and Lossy networks
> Subject: Re: draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re:
> [Roll] [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope valu=
e of 3 -
> subnet-local)
>=20
> I think I read consensus from the WG to make the following changes to dra=
ft-
> ietf-6man-multicast-scopes, and list the document as "Updates RFC 4007":
>=20
> *** Add as a new last paragraph in section 2:
>=20
>    The following change is applied to section 2.7 of RFC 4291:
>=20
>    OLD:
>=20
>          Admin-Local scope is the smallest scope that must be
>          administratively configured, i.e., not automatically derived
>          from physical connectivity or other, non-multicast-related
>          configuration.
>=20
>    NEW:
>=20
>          Interface-Local, Link-Local, and Realm-Local scope boundaries
>          are automatically derived from physical connectivity or
>          other, non-multicast related configuration.  Global scope has
>          no boundary.  The boundaries of all other non-reserved scopes
>          are administratively configured.

I disagree with the last sentence above.  Specifically
"non-reserved" should be removed.  That is, we should not start
precluding admin configuration of reserved scopes, given we didn't
before.  They just didn't have defined names or uses, but they could
have been used within private environments.

-Dave

>=20
> *** Add section 3 (and renumber current section 3-5):
>=20
> 3.  Updates to RFC 4007, section 5
>=20
>    Section 5 of RFC 4007 and section 2.7 of RFC 4291 disagree about the
>    way in which multicast scope 3 is configured.  To resolve that disagre=
ement,
>    change the last bullet in the list in section 5 of RFC 4007 as follows=
:
>=20
> OLD:
>=20
>    o  The boundaries of zones of a scope other than interface-local,
>       link-local, and global must be defined and configured by network
>       administrators.
>=20
> NEW:
>=20
>    o  The boundaries of zones of a scope are defined by the IPv6
>       addressing architecture [RFC4291].
>=20
> I haven't seen any discussion of changing Realm-Local to Multilink-Local
> beyond Kerry's initial suggestion and Robert's support of the change.
>=20
> - Ralph
>=20
> On Oct 17, 2013, at 12:10 PM 10/17/13, Ralph Droms
> <rdroms.ietf@gmail.com> wrote:
>=20
> > Kerry correctly points out that RFC 4007 and RFC 4291 are in conflict
> regarding the way in which multicast scope 3 is defined:
> >
> > RFC 4007, section 5:
> >
> >   o  The boundaries of zones of a scope other than interface-local,
> >      link-local, and global must be defined and configured by network
> >      administrators.
> >
> > RFC 4291, section 2.7:
> >
> >         Admin-Local scope is the smallest scope that must be
> >         administratively configured, i.e., not automatically derived
> >         from physical connectivity or other, non-multicast-related
> >         configuration.
> >
> > Noting this conflict, I propose adding a bit of text to draft-ietf-6man=
-
> multicast-scopes to update RFC 4007 for consistency with RFC 4291:
> >
> > Add section 3 (and renumber current section 3-5):
> >
> > 3.  Updates to RFC 4007, section 5
> >
> >   Section 5 of RFC 4007 and section 2.7 of RFC 4291 disagree about the
> >   way in which multicast scope 3 is configured.  To resolve that
> disagreement,
> >   change the last bullet in the list in section 5 of RFC 4007 as follow=
s:
> >
> > OLD:
> >
> >   o  The boundaries of zones of a scope other than interface-local,
> >      link-local, and global must be defined and configured by network
> >      administrators.
> >
> > NEW:
> >
> >   o  Admin-Local scope is the smallest scope that must be
> >      administratively configured, i.e., not automatically derived
> >      from physical connectivity or other, non-multicast-related
> >      configuration.
> >
> > Looking for consensus in the 6man WG before I make this change...
> >
> > - Ralph
> >
> > On Oct 16, 2013, at 10:04 AM 10/16/13, Kerry Lynn <kerlyn@ieee.org>
> wrote:
> >
> >> [...]
> >
> >> I think Ralph's approach is the correct one.  His
> >> draft-droms-6man-multicast-scopes belongs in 6man as it re-defines a
> >> reserved code point in the IPv6 addressing architecture.  It
> >> nominally updates RFC 4291 but should probably also update RFC 4007 as
> these RFCs are in conflict regarding the automatic definition of scope 0x=
03.
> > [...]
> >
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

From rdroms@cisco.com  Fri Oct 25 13:45:15 2013
Return-Path: <rdroms@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABB5421F9FDE; Fri, 25 Oct 2013 13:45:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZoytbKGi1DUx; Fri, 25 Oct 2013 13:45:08 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id A2FA421F9FCE; Fri, 25 Oct 2013 13:45:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5644; q=dns/txt; s=iport; t=1382733901; x=1383943501; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=zjq9XTarseY+9VlRGbeadkTKF8VNflkxJ4pZFOL9rTE=; b=NH4OAqi8h3UeqiCi68CosLfJE6kAITrKGuFzTmP9OO9ds+FQ5p8iIzO4 dxIiW9aFhitlJz7v00Mjgt0au2s+ssKdCKgLtZzQWlVHAXYRFKDHCL+r4 x+gN13hpfRO5aU2cIrN2W/PJCIYemgl5NCWEohziBcxIxzJbgn2c+4Q/j E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag4FAG3XalKtJXG//2dsb2JhbABZgwc4VL5IgSMWdIIlAQEBBAEBATc0CwwEAgEIDgMBAwEBAQoUBQQHIQYLFAMGCAIEDgUIh20DDw2vRg2JZwSMY4E4gQUCMQcGgxmBDQOWH447hTeBaIE+gio
X-IronPort-AV: E=Sophos;i="4.93,573,1378857600"; d="scan'208";a="276817098"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-8.cisco.com with ESMTP; 25 Oct 2013 20:44:59 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r9PKiweM020371 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 25 Oct 2013 20:44:58 GMT
Received: from xmb-aln-x04.cisco.com ([169.254.9.229]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.02.0318.004; Fri, 25 Oct 2013 15:44:58 -0500
From: "Ralph Droms (rdroms)" <rdroms@cisco.com>
To: Dave Thaler <dthaler@microsoft.com>
Subject: Re: draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re: [Roll] [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope	value of 3 - subnet-local)
Thread-Topic: draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re: [Roll] [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope	value of 3 - subnet-local)
Thread-Index: AQHO0cMRVKgL102kqEWw4KBFp4Nd5w==
Date: Fri, 25 Oct 2013 20:44:57 +0000
Message-ID: <4518F39EB578034D8C99A9B7776CDBA301C06DD6@xmb-aln-x04.cisco.com>
References: <3599.1381852752@sandelman.ca> <CE82BA46.24343%d.sturek@att.net> <CABOxzu2nLuny5uySEEdb6ji9ucE6xqGZ6DLe-mc6KUqVszNfFg@mail.gmail.com> <525DC6C9.2010808@gridmerge.com> <CABOxzu2apwBRpU1h4mKJwpO+U+Y9Q_q-h5AhZ+hGzAdjdPdmUQ@mail.gmail.com> <525E5064.4050109@gridmerge.com> <CABOxzu0L-EY0iDGpAJ+ER15CPL-3v8F77ewn-G=gZYODixevZg@mail.gmail.com> <3CC8783F-F4DA-47B9-A051-DBBA6EF00C19@gmail.com> <4518F39EB578034D8C99A9B7776CDBA301C067D0@xmb-aln-x04.cisco.com> <1daea916972b4e60be575e5f5276cb78@BY2PR03MB269.namprd03.prod.outlook.com>
In-Reply-To: <1daea916972b4e60be575e5f5276cb78@BY2PR03MB269.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.44.68.183]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <88FC4D114D123C489DF2DA6FDB96D533@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Routing Over Low power and Lossy networks <roll@ietf.org>, "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 20:45:16 -0000

On Oct 25, 2013, at 4:38 PM 10/25/13, Dave Thaler <dthaler@microsoft.com> w=
rote:

>> -----Original Message-----
>> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
>> Ralph Droms (rdroms)
>> Sent: Friday, October 25, 2013 1:21 PM
>> To: 6man@ietf.org
>> Cc: Routing Over Low power and Lossy networks
>> Subject: Re: draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re:
>> [Roll] [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope val=
ue of 3 -
>> subnet-local)
>>=20
>> I think I read consensus from the WG to make the following changes to dr=
aft-
>> ietf-6man-multicast-scopes, and list the document as "Updates RFC 4007":
>>=20
>> *** Add as a new last paragraph in section 2:
>>=20
>>   The following change is applied to section 2.7 of RFC 4291:
>>=20
>>   OLD:
>>=20
>>         Admin-Local scope is the smallest scope that must be
>>         administratively configured, i.e., not automatically derived
>>         from physical connectivity or other, non-multicast-related
>>         configuration.
>>=20
>>   NEW:
>>=20
>>         Interface-Local, Link-Local, and Realm-Local scope boundaries
>>         are automatically derived from physical connectivity or
>>         other, non-multicast related configuration.  Global scope has
>>         no boundary.  The boundaries of all other non-reserved scopes
>>         are administratively configured.
>=20
> I disagree with the last sentence above.  Specifically
> "non-reserved" should be removed.  That is, we should not start
> precluding admin configuration of reserved scopes, given we didn't
> before.  They just didn't have defined names or uses, but they could
> have been used within private environments.

Good catch.  So the last sentence should read:

  The boundaries of all other scopes are administratively configured.

?

- Ralph


>=20
> -Dave
>=20
>>=20
>> *** Add section 3 (and renumber current section 3-5):
>>=20
>> 3.  Updates to RFC 4007, section 5
>>=20
>>   Section 5 of RFC 4007 and section 2.7 of RFC 4291 disagree about the
>>   way in which multicast scope 3 is configured.  To resolve that disagre=
ement,
>>   change the last bullet in the list in section 5 of RFC 4007 as follows=
:
>>=20
>> OLD:
>>=20
>>   o  The boundaries of zones of a scope other than interface-local,
>>      link-local, and global must be defined and configured by network
>>      administrators.
>>=20
>> NEW:
>>=20
>>   o  The boundaries of zones of a scope are defined by the IPv6
>>      addressing architecture [RFC4291].
>>=20
>> I haven't seen any discussion of changing Realm-Local to Multilink-Local
>> beyond Kerry's initial suggestion and Robert's support of the change.
>>=20
>> - Ralph
>>=20
>> On Oct 17, 2013, at 12:10 PM 10/17/13, Ralph Droms
>> <rdroms.ietf@gmail.com> wrote:
>>=20
>>> Kerry correctly points out that RFC 4007 and RFC 4291 are in conflict
>> regarding the way in which multicast scope 3 is defined:
>>>=20
>>> RFC 4007, section 5:
>>>=20
>>>  o  The boundaries of zones of a scope other than interface-local,
>>>     link-local, and global must be defined and configured by network
>>>     administrators.
>>>=20
>>> RFC 4291, section 2.7:
>>>=20
>>>        Admin-Local scope is the smallest scope that must be
>>>        administratively configured, i.e., not automatically derived
>>>        from physical connectivity or other, non-multicast-related
>>>        configuration.
>>>=20
>>> Noting this conflict, I propose adding a bit of text to draft-ietf-6man=
-
>> multicast-scopes to update RFC 4007 for consistency with RFC 4291:
>>>=20
>>> Add section 3 (and renumber current section 3-5):
>>>=20
>>> 3.  Updates to RFC 4007, section 5
>>>=20
>>>  Section 5 of RFC 4007 and section 2.7 of RFC 4291 disagree about the
>>>  way in which multicast scope 3 is configured.  To resolve that
>> disagreement,
>>>  change the last bullet in the list in section 5 of RFC 4007 as follows=
:
>>>=20
>>> OLD:
>>>=20
>>>  o  The boundaries of zones of a scope other than interface-local,
>>>     link-local, and global must be defined and configured by network
>>>     administrators.
>>>=20
>>> NEW:
>>>=20
>>>  o  Admin-Local scope is the smallest scope that must be
>>>     administratively configured, i.e., not automatically derived
>>>     from physical connectivity or other, non-multicast-related
>>>     configuration.
>>>=20
>>> Looking for consensus in the 6man WG before I make this change...
>>>=20
>>> - Ralph
>>>=20
>>> On Oct 16, 2013, at 10:04 AM 10/16/13, Kerry Lynn <kerlyn@ieee.org>
>> wrote:
>>>=20
>>>> [...]
>>>=20
>>>> I think Ralph's approach is the correct one.  His
>>>> draft-droms-6man-multicast-scopes belongs in 6man as it re-defines a
>>>> reserved code point in the IPv6 addressing architecture.  It
>>>> nominally updates RFC 4291 but should probably also update RFC 4007 as
>> these RFCs are in conflict regarding the automatic definition of scope 0=
x03.
>>> [...]
>>>=20
>>=20
>> --------------------------------------------------------------------
>> 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 dthaler@microsoft.com  Fri Oct 25 13:49:41 2013
Return-Path: <dthaler@microsoft.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AB3D11E8204; Fri, 25 Oct 2013 13:49:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.629
X-Spam-Level: 
X-Spam-Status: No, score=-103.629 tagged_above=-999 required=5 tests=[AWL=-0.030, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N2vDunxy9LZ3; Fri, 25 Oct 2013 13:49:22 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1lp0149.outbound.protection.outlook.com [207.46.163.149]) by ietfa.amsl.com (Postfix) with ESMTP id A47EC11E81DC; Fri, 25 Oct 2013 13:49:16 -0700 (PDT)
Received: from BY2PR03MB269.namprd03.prod.outlook.com (10.242.37.11) by BY2PR03MB270.namprd03.prod.outlook.com (10.242.37.12) with Microsoft SMTP Server (TLS) id 15.0.800.7; Fri, 25 Oct 2013 20:49:14 +0000
Received: from BY2PR03MB269.namprd03.prod.outlook.com ([169.254.5.163]) by BY2PR03MB269.namprd03.prod.outlook.com ([169.254.5.31]) with mapi id 15.00.0800.005; Fri, 25 Oct 2013 20:49:14 +0000
From: Dave Thaler <dthaler@microsoft.com>
To: "Ralph Droms (rdroms)" <rdroms@cisco.com>
Subject: RE: draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re: [Roll] [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope	value of 3 - subnet-local)
Thread-Topic: draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re: [Roll] [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope	value of 3 - subnet-local)
Thread-Index: AQHO0cMU/XWHe3FPLUK0axFdo1U6Q5oF46Ew
Date: Fri, 25 Oct 2013 20:49:14 +0000
Message-ID: <d0f709553dd746018cc3dfeaba041d9f@BY2PR03MB269.namprd03.prod.outlook.com>
References: <3599.1381852752@sandelman.ca> <CE82BA46.24343%d.sturek@att.net> <CABOxzu2nLuny5uySEEdb6ji9ucE6xqGZ6DLe-mc6KUqVszNfFg@mail.gmail.com> <525DC6C9.2010808@gridmerge.com> <CABOxzu2apwBRpU1h4mKJwpO+U+Y9Q_q-h5AhZ+hGzAdjdPdmUQ@mail.gmail.com> <525E5064.4050109@gridmerge.com> <CABOxzu0L-EY0iDGpAJ+ER15CPL-3v8F77ewn-G=gZYODixevZg@mail.gmail.com> <3CC8783F-F4DA-47B9-A051-DBBA6EF00C19@gmail.com> <4518F39EB578034D8C99A9B7776CDBA301C067D0@xmb-aln-x04.cisco.com> <1daea916972b4e60be575e5f5276cb78@BY2PR03MB269.namprd03.prod.outlook.com> <4518F39EB578034D8C99A9B7776CDBA301C06DD6@xmb-aln-x04.cisco.com>
In-Reply-To: <4518F39EB578034D8C99A9B7776CDBA301C06DD6@xmb-aln-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:4898:80e8:ee31::3]
x-forefront-prvs: 0010D93EFE
x-forefront-antispam-report: SFV:NSPM; SFS:(24454002)(189002)(51704005)(199002)(80022001)(83322001)(74876001)(81542001)(81342001)(65816001)(85306002)(74366001)(83072001)(81816001)(74706001)(80976001)(81686001)(56776001)(54316002)(76482001)(47976001)(59766001)(77982001)(46102001)(51856001)(74316001)(54356001)(79102001)(74662001)(47446002)(74502001)(31966008)(69226001)(76796001)(56816003)(76576001)(76786001)(33646001)(77096001)(53806001)(49866001)(47736001)(50986001)(4396001)(63696002)(3826001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BY2PR03MB270; H:BY2PR03MB269.namprd03.prod.outlook.com; CLIP:2001:4898:80e8:ee31::3; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
Cc: Routing Over Low power and Lossy networks <roll@ietf.org>, "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 20:49:41 -0000

Ralph wrote:
[...]
> >>   NEW:
> >>
> >>         Interface-Local, Link-Local, and Realm-Local scope boundaries
> >>         are automatically derived from physical connectivity or
> >>         other, non-multicast related configuration.  Global scope has
> >>         no boundary.  The boundaries of all other non-reserved scopes
> >>         are administratively configured.
> >
> > I disagree with the last sentence above.  Specifically "non-reserved"
> > should be removed.  That is, we should not start precluding admin
> > configuration of reserved scopes, given we didn't before.  They just
> > didn't have defined names or uses, but they could have been used
> > within private environments.
>=20
> Good catch.  So the last sentence should read:
>=20
>   The boundaries of all other scopes are administratively configured.
>=20
> ?

Yes.

-Dave


From kerlyn2001@gmail.com  Fri Oct 25 14:07:10 2013
Return-Path: <kerlyn2001@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF33E11E8204; Fri, 25 Oct 2013 14:07:08 -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=[AWL=0.067,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nvKDiEXXEITI; Fri, 25 Oct 2013 14:07:07 -0700 (PDT)
Received: from mail-ob0-x234.google.com (mail-ob0-x234.google.com [IPv6:2607:f8b0:4003:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id A2F0411E8210; Fri, 25 Oct 2013 14:06:48 -0700 (PDT)
Received: by mail-ob0-f180.google.com with SMTP id wo20so1484079obc.39 for <multiple recipients>; Fri, 25 Oct 2013 14:06:26 -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=jUaQLYWxXb9weVRFehkbFYex7Vl477zHI4SEu0fJO4U=; b=u9Qh3lxJ4q/gP9cCyN8Cku/cEG9D7c27FfTopfW/IRQA+QHYENhNHv8sId7peSUytV PszFyar4bfSZRrRW7hcpaHxKLgNmmbnSiuiGACsvbVQyzHotMhI4UDpLK04+Jwpb2/TN e66WLj0kFsQG/glyVPSmf62OU9JZYWxdRLUClpdvQ6g+KIpXEECOjnyOQFZBDtMsjYib z+8abSdIQ9n+PtX7SBHGt2xWwHSXrOq9ENK0racM/chk1Ylvb/4Bku5vC3Nf6KHzEf6c 7BmEWTLDT+4X6CASln70+kZ7CTULTHcm2CevN1IiGUyuw6giEl26Yl/OHyoVx0KjuPy7 xbLg==
MIME-Version: 1.0
X-Received: by 10.182.220.225 with SMTP id pz1mr4575581obc.51.1382735186522; Fri, 25 Oct 2013 14:06:26 -0700 (PDT)
Sender: kerlyn2001@gmail.com
Received: by 10.60.73.6 with HTTP; Fri, 25 Oct 2013 14:06:26 -0700 (PDT)
In-Reply-To: <4518F39EB578034D8C99A9B7776CDBA301C06DD6@xmb-aln-x04.cisco.com>
References: <3599.1381852752@sandelman.ca> <CE82BA46.24343%d.sturek@att.net> <CABOxzu2nLuny5uySEEdb6ji9ucE6xqGZ6DLe-mc6KUqVszNfFg@mail.gmail.com> <525DC6C9.2010808@gridmerge.com> <CABOxzu2apwBRpU1h4mKJwpO+U+Y9Q_q-h5AhZ+hGzAdjdPdmUQ@mail.gmail.com> <525E5064.4050109@gridmerge.com> <CABOxzu0L-EY0iDGpAJ+ER15CPL-3v8F77ewn-G=gZYODixevZg@mail.gmail.com> <3CC8783F-F4DA-47B9-A051-DBBA6EF00C19@gmail.com> <4518F39EB578034D8C99A9B7776CDBA301C067D0@xmb-aln-x04.cisco.com> <1daea916972b4e60be575e5f5276cb78@BY2PR03MB269.namprd03.prod.outlook.com> <4518F39EB578034D8C99A9B7776CDBA301C06DD6@xmb-aln-x04.cisco.com>
Date: Fri, 25 Oct 2013 17:06:26 -0400
X-Google-Sender-Auth: 8K5Ip9gJrJZ90a3kkgdfpJQpo5Y
Message-ID: <CABOxzu1XwxMSHWUkQX4hkbstOYWu=AWFkvBPhNJfg8Hw7tJOGg@mail.gmail.com>
Subject: Re: [Roll] draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re: [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope value of 3 - subnet-local)
From: Kerry Lynn <kerlyn@ieee.org>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c30fac9c789604e9971fee
Cc: "6man@ietf.org" <6man@ietf.org>, Dave Thaler <dthaler@microsoft.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 21:07:10 -0000

--001a11c30fac9c789604e9971fee
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Oct 25, 2013 at 4:44 PM, Ralph Droms (rdroms) <rdroms@cisco.com>wrote:

>
> On Oct 25, 2013, at 4:38 PM 10/25/13, Dave Thaler <dthaler@microsoft.com>
> wrote:
>
> >> -----Original Message-----
> >> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> >> Ralph Droms (rdroms)
> >> Sent: Friday, October 25, 2013 1:21 PM
> >> To: 6man@ietf.org
> >> Cc: Routing Over Low power and Lossy networks
> >> Subject: Re: draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re:
> >> [Roll] [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope
> value of 3 -
> >> subnet-local)
> >>
> >> I think I read consensus from the WG to make the following changes to
> draft-
> >> ietf-6man-multicast-scopes, and list the document as "Updates RFC 4007":
> >>
> >> *** Add as a new last paragraph in section 2:
> >>
> >>   The following change is applied to section 2.7 of RFC 4291:
> >>
> >>   OLD:
> >>
> >>         Admin-Local scope is the smallest scope that must be
> >>         administratively configured, i.e., not automatically derived
> >>         from physical connectivity or other, non-multicast-related
> >>         configuration.
> >>
> >>   NEW:
> >>
> >>         Interface-Local, Link-Local, and Realm-Local scope boundaries
> >>         are automatically derived from physical connectivity or
> >>         other, non-multicast related configuration.  Global scope has
> >>         no boundary.  The boundaries of all other non-reserved scopes
> >>         are administratively configured.
> >
> > I disagree with the last sentence above.  Specifically
> > "non-reserved" should be removed.  That is, we should not start
> > precluding admin configuration of reserved scopes, given we didn't
> > before.  They just didn't have defined names or uses, but they could
> > have been used within private environments.
>
> Logically, the last sentence above doesn't entail how the boundaries
of reserved scopes are configured (the inference is that they may be
administratively or automatically configured).


> Good catch.  So the last sentence should read:
>
>   The boundaries of all other scopes are administratively configured.
>
> ?
>
> This makes it clear that the boundary of 11 of the 15 scopes defined in
RFC 4291 sect 2.7 (including 0) are administratively configured.  So it
is not equivalent in meaning to the old text if that was the intention.

-K-

- Ralph
>
>
> >
> > -Dave
> >
> >>
> >> *** Add section 3 (and renumber current section 3-5):
> >>
> >> 3.  Updates to RFC 4007, section 5
> >>
> >>   Section 5 of RFC 4007 and section 2.7 of RFC 4291 disagree about the
> >>   way in which multicast scope 3 is configured.  To resolve that
> disagreement,
> >>   change the last bullet in the list in section 5 of RFC 4007 as
> follows:
> >>
> >> OLD:
> >>
> >>   o  The boundaries of zones of a scope other than interface-local,
> >>      link-local, and global must be defined and configured by network
> >>      administrators.
> >>
> >> NEW:
> >>
> >>   o  The boundaries of zones of a scope are defined by the IPv6
> >>      addressing architecture [RFC4291].
> >>
> >> I haven't seen any discussion of changing Realm-Local to Multilink-Local
> >> beyond Kerry's initial suggestion and Robert's support of the change.
> >>
> >> - Ralph
> >>
> >> On Oct 17, 2013, at 12:10 PM 10/17/13, Ralph Droms
> >> <rdroms.ietf@gmail.com> wrote:
> >>
> >>> Kerry correctly points out that RFC 4007 and RFC 4291 are in conflict
> >> regarding the way in which multicast scope 3 is defined:
> >>>
> >>> RFC 4007, section 5:
> >>>
> >>>  o  The boundaries of zones of a scope other than interface-local,
> >>>     link-local, and global must be defined and configured by network
> >>>     administrators.
> >>>
> >>> RFC 4291, section 2.7:
> >>>
> >>>        Admin-Local scope is the smallest scope that must be
> >>>        administratively configured, i.e., not automatically derived
> >>>        from physical connectivity or other, non-multicast-related
> >>>        configuration.
> >>>
> >>> Noting this conflict, I propose adding a bit of text to
> draft-ietf-6man-
> >> multicast-scopes to update RFC 4007 for consistency with RFC 4291:
> >>>
> >>> Add section 3 (and renumber current section 3-5):
> >>>
> >>> 3.  Updates to RFC 4007, section 5
> >>>
> >>>  Section 5 of RFC 4007 and section 2.7 of RFC 4291 disagree about the
> >>>  way in which multicast scope 3 is configured.  To resolve that
> >> disagreement,
> >>>  change the last bullet in the list in section 5 of RFC 4007 as
> follows:
> >>>
> >>> OLD:
> >>>
> >>>  o  The boundaries of zones of a scope other than interface-local,
> >>>     link-local, and global must be defined and configured by network
> >>>     administrators.
> >>>
> >>> NEW:
> >>>
> >>>  o  Admin-Local scope is the smallest scope that must be
> >>>     administratively configured, i.e., not automatically derived
> >>>     from physical connectivity or other, non-multicast-related
> >>>     configuration.
> >>>
> >>> Looking for consensus in the 6man WG before I make this change...
> >>>
> >>> - Ralph
> >>>
> >>> On Oct 16, 2013, at 10:04 AM 10/16/13, Kerry Lynn <kerlyn@ieee.org>
> >> wrote:
> >>>
> >>>> [...]
> >>>
> >>>> I think Ralph's approach is the correct one.  His
> >>>> draft-droms-6man-multicast-scopes belongs in 6man as it re-defines a
> >>>> reserved code point in the IPv6 addressing architecture.  It
> >>>> nominally updates RFC 4291 but should probably also update RFC 4007 as
> >> these RFCs are in conflict regarding the automatic definition of scope
> 0x03.
> >>> [...]
> >>>
> >>
> >> --------------------------------------------------------------------
> >> 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
> > --------------------------------------------------------------------
>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>

--001a11c30fac9c789604e9971fee
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Fri, Oct 25, 2013 at 4:44 PM, Ralph Droms (rdroms) <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:rdroms@cisco.com" target=3D"_blank">rdr=
oms@cisco.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div clas=
s=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><br>
On Oct 25, 2013, at 4:38 PM 10/25/13, Dave Thaler &lt;<a href=3D"mailto:dth=
aler@microsoft.com">dthaler@microsoft.com</a>&gt; wrote:<br>
<div class=3D"im"><br>
&gt;&gt; -----Original Message-----<br>
&gt;&gt; From: <a href=3D"mailto:ipv6-bounces@ietf.org">ipv6-bounces@ietf.o=
rg</a> [mailto:<a href=3D"mailto:ipv6-bounces@ietf.org">ipv6-bounces@ietf.o=
rg</a>] On Behalf Of<br>
&gt;&gt; Ralph Droms (rdroms)<br>
&gt;&gt; Sent: Friday, October 25, 2013 1:21 PM<br>
&gt;&gt; To: <a href=3D"mailto:6man@ietf.org">6man@ietf.org</a><br>
&gt;&gt; Cc: Routing Over Low power and Lossy networks<br>
&gt;&gt; Subject: Re: draft-ietf-6man-multicast-scopes updates RFC 4007 (Wa=
s Re:<br>
&gt;&gt; [Roll] [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify sco=
pe value of 3 -<br>
&gt;&gt; subnet-local)<br>
&gt;&gt;<br>
</div><div class=3D"im">&gt;&gt; I think I read consensus from the WG to ma=
ke the following changes to draft-<br>
&gt;&gt; ietf-6man-multicast-scopes, and list the document as &quot;Updates=
 RFC 4007&quot;:<br>
&gt;&gt;<br>
&gt;&gt; *** Add as a new last paragraph in section 2:<br>
&gt;&gt;<br>
&gt;&gt; =A0 The following change is applied to section 2.7 of RFC 4291:<br=
>
&gt;&gt;<br>
&gt;&gt; =A0 OLD:<br>
&gt;&gt;<br>
&gt;&gt; =A0 =A0 =A0 =A0 Admin-Local scope is the smallest scope that must =
be<br>
&gt;&gt; =A0 =A0 =A0 =A0 administratively configured, i.e., not automatical=
ly derived<br>
&gt;&gt; =A0 =A0 =A0 =A0 from physical connectivity or other, non-multicast=
-related<br>
&gt;&gt; =A0 =A0 =A0 =A0 configuration.<br>
&gt;&gt;<br>
&gt;&gt; =A0 NEW:<br>
&gt;&gt;<br>
&gt;&gt; =A0 =A0 =A0 =A0 Interface-Local, Link-Local, and Realm-Local scope=
 boundaries<br>
&gt;&gt; =A0 =A0 =A0 =A0 are automatically derived from physical connectivi=
ty or<br>
&gt;&gt; =A0 =A0 =A0 =A0 other, non-multicast related configuration. =A0Glo=
bal scope has<br>
&gt;&gt; =A0 =A0 =A0 =A0 no boundary. =A0The boundaries of all other non-re=
served scopes<br>
&gt;&gt; =A0 =A0 =A0 =A0 are administratively configured.<br>
&gt;<br>
</div>&gt; I disagree with the last sentence above. =A0Specifically<br>
&gt; &quot;non-reserved&quot; should be removed. =A0That is, we should not =
start<br>
&gt; precluding admin configuration of reserved scopes, given we didn&#39;t=
<br>
&gt; before. =A0They just didn&#39;t have defined names or uses, but they c=
ould<br>
&gt; have been used within private environments.<br>
<br></blockquote><div><div>Logically, the last sentence above doesn&#39;t e=
ntail how the boundaries<br>of reserved scopes are configured (the inferenc=
e is that they may be<br></div><div>administratively or automatically confi=
gured).<br>
</div>=A0
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Good catch. =A0So the last sentence should read:<br>
<br>
=A0 The boundaries of all other scopes are administratively configured.<br>
<br>
?<br>
<br></blockquote>This makes it clear that the boundary of 11 of the 15 scop=
es defined in<br>RFC 4291 sect 2.7 (including 0) are administratively confi=
gured.=A0 So it<br></div><div class=3D"gmail_quote">is not equivalent in me=
aning to the old text if that was the intention.<br>
<br></div><div class=3D"gmail_quote">-K-<br><br></div><div class=3D"gmail_q=
uote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex">
- Ralph<br>
<br>
<br>
&gt;<br>
&gt; -Dave<br>
<div><div class=3D"h5">&gt;<br>
&gt;&gt;<br>
&gt;&gt; *** Add section 3 (and renumber current section 3-5):<br>
&gt;&gt;<br>
&gt;&gt; 3. =A0Updates to RFC 4007, section 5<br>
&gt;&gt;<br>
&gt;&gt; =A0 Section 5 of RFC 4007 and section 2.7 of RFC 4291 disagree abo=
ut the<br>
&gt;&gt; =A0 way in which multicast scope 3 is configured. =A0To resolve th=
at disagreement,<br>
&gt;&gt; =A0 change the last bullet in the list in section 5 of RFC 4007 as=
 follows:<br>
&gt;&gt;<br>
&gt;&gt; OLD:<br>
&gt;&gt;<br>
&gt;&gt; =A0 o =A0The boundaries of zones of a scope other than interface-l=
ocal,<br>
&gt;&gt; =A0 =A0 =A0link-local, and global must be defined and configured b=
y network<br>
&gt;&gt; =A0 =A0 =A0administrators.<br>
&gt;&gt;<br>
&gt;&gt; NEW:<br>
&gt;&gt;<br>
&gt;&gt; =A0 o =A0The boundaries of zones of a scope are defined by the IPv=
6<br>
&gt;&gt; =A0 =A0 =A0addressing architecture [RFC4291].<br>
&gt;&gt;<br>
&gt;&gt; I haven&#39;t seen any discussion of changing Realm-Local to Multi=
link-Local<br>
&gt;&gt; beyond Kerry&#39;s initial suggestion and Robert&#39;s support of =
the change.<br>
&gt;&gt;<br>
&gt;&gt; - Ralph<br>
&gt;&gt;<br>
&gt;&gt; On Oct 17, 2013, at 12:10 PM 10/17/13, Ralph Droms<br>
&gt;&gt; &lt;<a href=3D"mailto:rdroms.ietf@gmail.com">rdroms.ietf@gmail.com=
</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt;&gt; Kerry correctly points out that RFC 4007 and RFC 4291 are in c=
onflict<br>
&gt;&gt; regarding the way in which multicast scope 3 is defined:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; RFC 4007, section 5:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; =A0o =A0The boundaries of zones of a scope other than interfac=
e-local,<br>
&gt;&gt;&gt; =A0 =A0 link-local, and global must be defined and configured =
by network<br>
&gt;&gt;&gt; =A0 =A0 administrators.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; RFC 4291, section 2.7:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; =A0 =A0 =A0 =A0Admin-Local scope is the smallest scope that mu=
st be<br>
&gt;&gt;&gt; =A0 =A0 =A0 =A0administratively configured, i.e., not automati=
cally derived<br>
&gt;&gt;&gt; =A0 =A0 =A0 =A0from physical connectivity or other, non-multic=
ast-related<br>
&gt;&gt;&gt; =A0 =A0 =A0 =A0configuration.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Noting this conflict, I propose adding a bit of text to draft-=
ietf-6man-<br>
&gt;&gt; multicast-scopes to update RFC 4007 for consistency with RFC 4291:=
<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Add section 3 (and renumber current section 3-5):<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; 3. =A0Updates to RFC 4007, section 5<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; =A0Section 5 of RFC 4007 and section 2.7 of RFC 4291 disagree =
about the<br>
&gt;&gt;&gt; =A0way in which multicast scope 3 is configured. =A0To resolve=
 that<br>
&gt;&gt; disagreement,<br>
&gt;&gt;&gt; =A0change the last bullet in the list in section 5 of RFC 4007=
 as follows:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; OLD:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; =A0o =A0The boundaries of zones of a scope other than interfac=
e-local,<br>
&gt;&gt;&gt; =A0 =A0 link-local, and global must be defined and configured =
by network<br>
&gt;&gt;&gt; =A0 =A0 administrators.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; NEW:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; =A0o =A0Admin-Local scope is the smallest scope that must be<b=
r>
&gt;&gt;&gt; =A0 =A0 administratively configured, i.e., not automatically d=
erived<br>
&gt;&gt;&gt; =A0 =A0 from physical connectivity or other, non-multicast-rel=
ated<br>
&gt;&gt;&gt; =A0 =A0 configuration.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Looking for consensus in the 6man WG before I make this change=
...<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; - Ralph<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; On Oct 16, 2013, at 10:04 AM 10/16/13, Kerry Lynn &lt;<a href=
=3D"mailto:kerlyn@ieee.org">kerlyn@ieee.org</a>&gt;<br>
&gt;&gt; wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; [...]<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; I think Ralph&#39;s approach is the correct one. =A0His<br=
>
&gt;&gt;&gt;&gt; draft-droms-6man-multicast-scopes belongs in 6man as it re=
-defines a<br>
&gt;&gt;&gt;&gt; reserved code point in the IPv6 addressing architecture. =
=A0It<br>
&gt;&gt;&gt;&gt; nominally updates RFC 4291 but should probably also update=
 RFC 4007 as<br>
&gt;&gt; these RFCs are in conflict regarding the automatic definition of s=
cope 0x03.<br>
&gt;&gt;&gt; [...]<br>
&gt;&gt;&gt;<br>
&gt;&gt;<br>
</div></div><div class=3D"im">&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>
</div>&gt;&gt; ------------------------------------------------------------=
--------<br>
<div class=3D"im">&gt; ----------------------------------------------------=
----------------<br>
&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>
</div>&gt; ----------------------------------------------------------------=
----<br>
<div class=3D""><div class=3D"h5"><br>
_______________________________________________<br>
Roll mailing list<br>
<a href=3D"mailto:Roll@ietf.org">Roll@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/roll" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/roll</a><br>
</div></div></blockquote></div><br></div></div>

--001a11c30fac9c789604e9971fee--

From ietf@rozanak.com  Fri Oct 25 15:11:51 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 857EF11E81EC for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 15:11:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.196
X-Spam-Level: 
X-Spam-Status: No, score=-2.196 tagged_above=-999 required=5 tests=[AWL=0.403,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dLxFWRnS-Igd for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 15:11:46 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id B0A4D21F9D7A for <ipv6@ietf.org>; Fri, 25 Oct 2013 15:11:46 -0700 (PDT)
Received: from kopoli (g231250140.adsl.alicedsl.de [92.231.250.140]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0LuwOn-1VifMK1bxB-00zocG; Fri, 25 Oct 2013 18:11:44 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: "'Andrew Yourtchenko'" <ayourtch@gmail.com>
References: <014301cece8a$2b780e20$82682a60$@rozanak.com> <CAPi140PStSx+HDM9rpgVjPed3OFD=gpsXkOdH2HiC7mf350f+Q@mail.gmail.com>
In-Reply-To: <CAPi140PStSx+HDM9rpgVjPed3OFD=gpsXkOdH2HiC7mf350f+Q@mail.gmail.com>
Subject: RE: ra privacy: an improvement to privacy extension plus source code
Date: Sat, 26 Oct 2013 00:11:37 +0200
Message-ID: <008501ced1cf$2fab1620$8f014260$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIlK4lRrTNvcfZ9YadRSmQ5Etnr3AGQizLOmUy5ZvA=
Content-Language: en-us
X-Provags-ID: V02:K0:NqgHUecy6/gDOXQ2oUcBEnrgPAheBxruLaHJyH3shdj wp7pRv0HwMCQ2NtiJXiBCiUocbNDL1betxVqSwRwkm632WX12i C7+WYg9Ob+6NEd3PeuNRhrNBFYLIAMRkwVDt6clfMlFPviKHhn QTpkVHxzEaNPT9Wh4v2XYkoCAV9tXVjzsoF26T9CXKu088U/UL vyEQmDURwPnuozr9Nogbt8ziNOaDd2gJYQulVJ7obHtMqB6Acv X8+cYoao0162l0Qggg+TtZSSiwmVoFjOsROCCNYRBTNHbhIwMM fuhKAd/n7PtnG9okTeOrX3woXYxAxrReqsNVIY4TcIwG2OUm4G E+Pcd6GPFtZIQpCbxSN4=
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 22:11:51 -0000

Hi Andrew,
Thanks a lot for taking time to review this
http://tools.ietf.org/html/draft-rafiee-6man-ra-privacy . 

> "- RFC 4941 specifies the use of EUI-64 to generate the public address
>    of node
> "
> 
> I would not agree with this. 4941 refers to 4862 for generating the public
> address, which in turn suggests to use "interface identifier"
> when creating a global address, and does not mandate EUI-64 as the only
> mechanism (as evidenced in some implementations, namely, Windows). The
> 4291, on the other hand, does talk about EUI-64 *format* but it also
> specifically mentions the MAC addresses are not necessary to be used. So,
> IMHO this is not a problem.

I call this the problem because when you have both temporary addresses and
public/permanent addresses that is generated based on EUI-64 or EUI-48(MAC),
your public address will allow the attackers to track your node. 

> 
> Anyway if the nodes want to use the stable public addresses that are scan-
> resistant, there is a draft by Fernando Gont which solves this problem.
I'd
> rather see you contribute to that one if that solution is not good enough
you
> think, rather than having yet another fork.

I guess you missed the point again. That draft generates a stable IID which
means that the node will have the same IID whenever it is fixed in a same
network. IPv6 addresses are the public addresses so the node use this
address to access websites or other data through the internet and this
address soon will be known to all websites or resources on that this user
use it. If as a mistake this user also check a resources which belongs to an
attacker. The attacker will have his IP address and this IP never changes
until the router prefix changes. This actually will not happen at least in
the short time or it can be permanent. 
So, this allows the attacker to access the information of this user. 
This is why I like privacy extension approach more. Because it also changes
the IID within the same subnet but in ra-privacy, I explained that if the
node wants to have this public addresses it should not generate it based on
EUI-64 or MAC and might change it based on Stable addresses that, at least,
we can decrease the chance of exposing hardware information.  
The new draft recently sent  "deprecated addresses" actually contains most
part of information which this draft was addressed and addressing.



>    - If the node is changing the physical link, it may keep the IID
>    already used on the link it is leaving, to form an IPv6 address on
>    the new link using SLAAC.
> "
> 
> This is a problem I agree is a problem, which has been fixed in some
> implementations; and arguably in the other implementations a bug should be
> filed "If the prefix changes, the node MUST NOT reuse the already used
> temporary IID". But, maybe to fix this bug, an update to
> 4941 could be useful.

You say this fixed in implementation. My question is why we have standards?
If implementers wants to implement something in whatever way they like, then
I guess we cannot communicate via internet anymore as it would be ruled by
incompatible systems and we will back to 19 century. 
I am open to suggestions and improve it.


> Fernando's draft also specifies that IID of the "stable addresses"
> needs to be different on different prefixes, so this problem only applies
to
> temporary addresses.

That is true. Ra-privacy has no recommendation about public addresses except
not to use the hardware information or EUI-64 RFC. The recommendation in
this draft is about temporary addresses and a few explanation of the current
problem with Privacy Extension.


> 
> I read the 4941 and I think it is flexible enough allow oneself to both
shoot
> oneself in the foot and to make a sane implementation. So I am not sure
this
> is a valid problem to solve.

I just noticed some ambiguous words in this RFC. It does not effect on the
proper implementation but will effect on new implementation of this RFC or
any bad implementation of this RFC.

> "
>    - This document also clarifies the use of other algorithm and compare
>    it with CGA and DHCPv6 when there is no stable storage available. So
>    that the node may be able to make use of a greatly randomized IID
>    because, according to section 3.2.2 of RFC 4941, there is nothing to
>    force the use of RFC 4086.
> "
> 
> We had tons of the discussions about the algorithm. I maintain that it
boils
> down to:

> "On each link change, take 64 bits of random data and put it into IID.
> Ensure the random data is good quality".
> 
> There is a significant body of work on generating good random numbers and
I
> do not see this draft contributing anything new to it, in this regard.
> 
> So, as I support only 1 portion of the draft out of 4, in general I am
still
> opposed to it.
> 

Spending time on implementation was only for showing how ra-privacy works in
compare with Privacy extension and how good it can generates random number
with this suggested algorithm. Test it please and then say it wasn't any
contribution for generating a good random number.  
Again I am open to good suggestions if you have any.

Thank you,
-----------smile----------
Hosnieh
. success is a journey, not a destination..
You cannot change your destination overnight, but you can change your
direction ... Focus on the journey




From brian.e.carpenter@gmail.com  Fri Oct 25 17:17:47 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3411811E819C for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 17:17:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.521
X-Spam-Level: 
X-Spam-Status: No, score=-102.521 tagged_above=-999 required=5 tests=[AWL=0.078, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uBEYrCrSkznK for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 17:17:44 -0700 (PDT)
Received: from mail-pb0-x234.google.com (mail-pb0-x234.google.com [IPv6:2607:f8b0:400e:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 3E43911E81DF for <ipv6@ietf.org>; Fri, 25 Oct 2013 17:17:42 -0700 (PDT)
Received: by mail-pb0-f52.google.com with SMTP id rr4so2613684pbb.11 for <ipv6@ietf.org>; Fri, 25 Oct 2013 17:17: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=HlMLKlTpSUixj2Wa3sEmnks1n0Dd8Uc1vBjMuXWaguI=; b=OvixMW9pEtWMDjE1BamFIugoDuOCc340pif2L7KfY3cHvwFYQNi8dU7QjKmJ1cVR4t oOEh4S9V9eH12JRi/hYP0moNPHc5Kz5vLRwYIEqbfic5yma0Ov1zr8wnA+fuI8pnLKwx lXX6qpGrWuPQswZwexTnwcaxHW4TVYpacP66XlioGwn0Bjgu/iTV9cRG+UcjLp0nWyJj 96v2SPwM89JpzgtTYflzFy4OWDAnnIDcR/7pUekevBwUPrtURPjet2FZiJKK6wxI2iz3 O+uYbQJaiTWz/3UazY6g5sB8ZB4j21N1E2QLV8IgOIsu7O4avPkTWVPM9zxdKHfkhJKF ttqw==
X-Received: by 10.68.244.2 with SMTP id xc2mr4217618pbc.58.1382746661983; Fri, 25 Oct 2013 17:17:41 -0700 (PDT)
Received: from [192.168.178.20] (85.201.69.111.dynamic.snap.net.nz. [111.69.201.85]) by mx.google.com with ESMTPSA id nj9sm12205443pbc.13.2013.10.25.17.17.39 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 25 Oct 2013 17:17:41 -0700 (PDT)
Message-ID: <526B0A30.9060600@gmail.com>
Date: Sat, 26 Oct 2013 13:17: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: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Why /64 [was Deprecating EUI-64 Based IPv6 Addresses]
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar>	<526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com>	<E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Fernando Gont <fgont@si6networks.com>, Alexandru Petrescu <alexandru.petrescu@gmail.com>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Oct 2013 00:17:47 -0000

1. Why do people find it so hard to change the Subject when changing the subject?

2. Since we have a bunch of IID specs that all assume /64, and a large bunch of
code (and, I suspect, silicon) that assumes /64, we really need a very serious
practical analysis document before any possible decision.

Regards
   Brian

On 26/10/2013 08:30, Tim Chown wrote:
> On 25 Oct 2013, at 18:38, Fernando Gont <fgont@si6networks.com> wrote:
> 
>> On 10/25/2013 01:54 PM, Alexandru Petrescu wrote:
>>> If we're again at deprecating things one aspect that I'd really like
>>> removed is this 64bit border for SLAAC over Ethernet.
>>>
>>> One should be able to do SLAAC over Ethernet (and all its backward
>>> compatible IEEE links) with Interface Identifiers optionally  shorter
>>> than 64bit.
>> If there's something else that needs to be fixed, then please:
>>
>> 1) Write an I-D that analyzes the problem, and proposes a workaround, and,
>>
>> 2) start a new thread. :-)
>>
>> Let's keep this thread on-topic. ;-)
> 
> Well, you're proposing deprecating EUI-64, so there is no longer any reason to be constrained to /64.... so your replacement should consider the possibility of it being used with longer subnet prefixes at some point in the future?
> 
> Tim
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 

From fgont@si6networks.com  Fri Oct 25 17:36:27 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0DA111E8210 for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 17:36:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4kIA8x-JtB4S for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 17:36:27 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id A30F511E81FD for <ipv6@ietf.org>; Fri, 25 Oct 2013 17:36:23 -0700 (PDT)
Received: from 200-081-044-004.wireless.movistar.net.ar ([200.81.44.4] helo=[192.168.43.189]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1VZrrW-0006bK-Jb; Sat, 26 Oct 2013 02:36:19 +0200
Message-ID: <526B0E15.8080602@si6networks.com>
Date: Fri, 25 Oct 2013 21:34:29 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>,  Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: Why /64 [was Deprecating EUI-64 Based IPv6 Addresses]
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar>	<526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com>	<E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526B0A30.9060600@gmail.com>
In-Reply-To: <526B0A30.9060600@gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Alexandru Petrescu <alexandru.petrescu@gmail.com>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Oct 2013 00:36:28 -0000

On 10/25/2013 09:17 PM, Brian E Carpenter wrote:
> 1. Why do people find it so hard to change the Subject when changing the subject?
> 
> 2. Since we have a bunch of IID specs that all assume /64, and a large bunch of
> code (and, I suspect, silicon) that assumes /64, we really need a very serious
> practical analysis document before any possible decision.

That's why I think that relaxing the /64 requirement is a whole
different game. -- If anything, a first step would be to relax this for
hosts, and *at some point in the future*, relax it for routers --
otherwise, a "legacy" host that expects a /64 might break or fail to do
SLAAC if an updated router where to advertise, say, a /80.

OTOH, deprecating Modified EUI-64 is a local policy which is
incrementally-deployable.

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





From brian.e.carpenter@gmail.com  Fri Oct 25 17:54:49 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCEB911E819C for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 17:54:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.522
X-Spam-Level: 
X-Spam-Status: No, score=-102.522 tagged_above=-999 required=5 tests=[AWL=0.077, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7JYamWUdHhTB for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 17:54:49 -0700 (PDT)
Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id D6DE211E818F for <ipv6@ietf.org>; Fri, 25 Oct 2013 17:54:48 -0700 (PDT)
Received: by mail-pa0-f41.google.com with SMTP id rd3so31978pab.0 for <ipv6@ietf.org>; Fri, 25 Oct 2013 17:54:48 -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=HtAfuIWt9Ysrcl7WtgYS1VsIe77zWkxGyXAZCRDA028=; b=PMxJTplVeVP5zpqZ14xI/hcSXWH318qNNElMuDbffJapyzkCf+meOTMSKcs4245Lwz Rmj2nSDdjAQH9Vr3RhYTPIKum4bHruYsk94NTTCFHSw4m2nyMKS2M36Uscgq7GPbdBwk nVKZOECuuHx+4cLyi5GSgQiPVf+75YUkL8RmLD9g4c+4KOuLzXuQzSucjLjCHmiyDUnq dnplOR62HY8h33M3gt6zNLUpR7/1qrRRLqSPBGv76exhtTZOkpoytD2Ov7R26ejYyrqu dS5WSvrQy3bcenONJQcN5y2b2tTAfhpHNMXw+TwW9sArYKfEWa8+nIuBSrH05RZ6gSkQ kjUw==
X-Received: by 10.68.58.137 with SMTP id r9mr4333617pbq.148.1382748888688; Fri, 25 Oct 2013 17:54:48 -0700 (PDT)
Received: from [192.168.178.20] (85.201.69.111.dynamic.snap.net.nz. [111.69.201.85]) by mx.google.com with ESMTPSA id sd3sm12277628pbb.42.2013.10.25.17.54.46 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 25 Oct 2013 17:54:48 -0700 (PDT)
Message-ID: <526B12E2.5050503@gmail.com>
Date: Sat, 26 Oct 2013 13:54:58 +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: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com> <52697C33.7010904@gmail.com> <5269B633.8010802@si6networks.com> <5269D03A.8030809@gmail.com> <28EF616C-5765-4D3D-9593-86DE8BB538C5@ecs.soton.ac.uk> <EMEW3|6c915c4e4e63530092c3f6edabbf8a7ep9OL7r03tjc|ecs.soton.ac.uk|28EF616C-5765-4D3D-9593-86DE8BB538C5@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|6c915c4e4e63530092c3f6edabbf8a7ep9OL7r03tjc|ecs.soton.ac.uk|28EF616C-5765-4D3D-9593-86DE8BB538C5@ecs.soton.ac.uk>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Fernando Gont <fgont@si6networks.com>, 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Oct 2013 00:54:50 -0000

On 26/10/2013 09:06, Tim Chown wrote:
> On 25 Oct 2013, at 02:58, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
>> On 25/10/2013 13:07, Fernando Gont wrote:
>>> On 10/24/2013 04:59 PM, Brian E Carpenter wrote:
>>>> Unfortunately I feel that this is operationally unacceptable.
>>>>
>>>> There are many (I suppose thousands) of sites that rely on MAC
>>>> addresses to manage their assets, and in many cases to trace
>>>> malicious users. 
>>> Question:
>>>
>>> Do you argue that they rely on
>>> 1) the MAC address being present in the IID, or,
>>> 2) the IPv6 address (and hence the IPv6 -> link layer address mapping)
>>>   being stable?
>> I actually think that today, not too many sites have decided how
>> to handle this for IPv6, but the decisions whether to use SLAAC
>> or DHCPv6, and whether to allow RFC4941 addresses or insist
>> on Modified EUI-64, have to be taken as each site rolls out
>> IPv6. My guess is that large campus-style sites will not
>> allow RFC4941 because they don't have the logging to allow
>> a traceback to the user.
> 
> This is not true.  There are open source packages that allow you to harvest switch port, MACs, IPs etc, dual-stack.  OK, so the db gets big if RFC4941 refresh is rapid, but it works.

If you happen to run such a package. But lots of sites don't, and maybe don't want
to. I don't see why the IETF has the right to dictate here. That's why
I prefer SHOULD NOT.

> How do you prevent 4941 anyway on campus BYOD, if you allow EUI-64?  What product does that?

You probably can't. Actually that's why some campuses have separate
networks for BYOD, where other restrictions apply.

> The approach has to be expect anything, and monitor/log it.

Certainly, on BYOD.

    Brian

From fgont@si6networks.com  Fri Oct 25 18:13:00 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3C0621E8093 for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 18:13:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7JtddGs0QZ5a for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 18:13:00 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 02F6811E818F for <ipv6@ietf.org>; Fri, 25 Oct 2013 18:13:00 -0700 (PDT)
Received: from 200-081-044-004.wireless.movistar.net.ar ([200.81.44.4] helo=[192.168.43.189]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1VZsQv-0007PR-7a; Sat, 26 Oct 2013 03:12:58 +0200
Message-ID: <526B169A.7020208@si6networks.com>
Date: Fri, 25 Oct 2013 22:10:50 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>,  Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com> <52697C33.7010904@gmail.com> <5269B633.8010802@si6networks.com> <5269D03A.8030809@gmail.com> <28EF616C-5765-4D3D-9593-86DE8BB538C5@ecs.soton.ac.uk> <EMEW3|6c915c4e4e63530092c3f6edabbf8a7ep9OL7r03tjc|ecs.soton.ac.uk|28EF616C-5765-4D3D-9593-86DE8BB538C5@ecs.soton.ac.uk> <526B12E2.5050503@gmail.com>
In-Reply-To: <526B12E2.5050503@gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Oct 2013 01:13:00 -0000

Hi, Brian,

On 10/25/2013 09:54 PM, Brian E Carpenter wrote:
>>>> Do you argue that they rely on 1) the MAC address being present
>>>> in the IID, or, 2) the IPv6 address (and hence the IPv6 -> link
>>>> layer address mapping) being stable?
>>> I actually think that today, not too many sites have decided how 
>>> to handle this for IPv6, but the decisions whether to use SLAAC 
>>> or DHCPv6, and whether to allow RFC4941 addresses or insist on
>>> Modified EUI-64, have to be taken as each site rolls out IPv6. My
>>> guess is that large campus-style sites will not allow RFC4941
>>> because they don't have the logging to allow a traceback to the
>>> user.
>> 
>> This is not true.  There are open source packages that allow you to
>> harvest switch port, MACs, IPs etc, dual-stack.  OK, so the db gets
>> big if RFC4941 refresh is rapid, but it works.
> 
> If you happen to run such a package. But lots of sites don't, and
> maybe don't want to. I don't see why the IETF has the right to
> dictate here. That's why I prefer SHOULD NOT.

I'm not sure I follow. What's the implication of having this logging
feature (or not) on this I-D?

You only need such loggig feature if the IPv6/MAC mapping changes. This
I-D is simply about stable addresses... so such discussion is orthogonal.

Am I missing something?

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





From brian.e.carpenter@gmail.com  Fri Oct 25 18:51:45 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1F1211E80E8 for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 18:51:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.523
X-Spam-Level: 
X-Spam-Status: No, score=-102.523 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4ZDJeOX5JrE1 for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 18:51:45 -0700 (PDT)
Received: from mail-pb0-x235.google.com (mail-pb0-x235.google.com [IPv6:2607:f8b0:400e:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id D36BA11E8228 for <ipv6@ietf.org>; Fri, 25 Oct 2013 18:51:44 -0700 (PDT)
Received: by mail-pb0-f53.google.com with SMTP id up7so4174518pbc.12 for <ipv6@ietf.org>; Fri, 25 Oct 2013 18:51:44 -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=tnIpv6GdhMGLhrsHs3x3+KCKh8DwBu0U7rSpWPUc+Ug=; b=Y0fc/9m1SD9FvHk2uSD1owHCDtZcRbi5KGnlT4ueFfk/oUoiM2kGI+DdUdgxBRLPQ1 Hi/24uIk8JWDXOXvjeUO50+2E59Tz2P7vdvxtfXu31CtywdrxZB3uOvxgy8soqN7dIat AGmvYsRUqmjyc3dfzJlBY9yDu/LXn68/LBxKoiUW5+KI0A8y8WWxKeLdi+jqB3IEVh6w dudvSfWUNtw8phcYzaCcvnt+vvBK3mrksfttZAIIdRiW2aLJTItOeImZFWrk/xc6NGTZ pQcXTmaytzuSK59+Ux8TupY2e9ersoSque4Ov04tutgSMetDl+fi4GOfhcFXPHoasav5 QQYg==
X-Received: by 10.66.218.226 with SMTP id pj2mr13583042pac.62.1382752304621; Fri, 25 Oct 2013 18:51:44 -0700 (PDT)
Received: from [192.168.178.20] (85.201.69.111.dynamic.snap.net.nz. [111.69.201.85]) by mx.google.com with ESMTPSA id og5sm12526491pbb.10.2013.10.25.18.51.42 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 25 Oct 2013 18:51:44 -0700 (PDT)
Message-ID: <526B203A.6040008@gmail.com>
Date: Sat, 26 Oct 2013 14:51: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-gont-6man-deprecate-eui64-based-addresses-00.txt
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com> <52697C33.7010904@gmail.com> <5269B633.8010802@si6networks.com> <5269D03A.8030809@gmail.com> <28EF616C-5765-4D3D-9593-86DE8BB538C5@ecs.soton.ac.uk> <EMEW3|6c915c4e4e63530092c3f6edabbf8a7ep9OL7r03tjc|ecs.soton.ac.uk|28EF616C-5765-4D3D-9593-86DE8BB538C5@ecs.soton.ac.uk> <526B12E2.5050503@gmail.com> <526B169A.7020208@si6networks.com>
In-Reply-To: <526B169A.7020208@si6networks.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Oct 2013 01:51:45 -0000

On 26/10/2013 14:10, Fernando Gont wrote:
> Hi, Brian,
> 
> On 10/25/2013 09:54 PM, Brian E Carpenter wrote:
>>>>> Do you argue that they rely on 1) the MAC address being present
>>>>> in the IID, or, 2) the IPv6 address (and hence the IPv6 -> link
>>>>> layer address mapping) being stable?
>>>> I actually think that today, not too many sites have decided how 
>>>> to handle this for IPv6, but the decisions whether to use SLAAC 
>>>> or DHCPv6, and whether to allow RFC4941 addresses or insist on
>>>> Modified EUI-64, have to be taken as each site rolls out IPv6. My
>>>> guess is that large campus-style sites will not allow RFC4941
>>>> because they don't have the logging to allow a traceback to the
>>>> user.
>>> This is not true.  There are open source packages that allow you to
>>> harvest switch port, MACs, IPs etc, dual-stack.  OK, so the db gets
>>> big if RFC4941 refresh is rapid, but it works.
>> If you happen to run such a package. But lots of sites don't, and
>> maybe don't want to. I don't see why the IETF has the right to
>> dictate here. That's why I prefer SHOULD NOT.
> 
> I'm not sure I follow. What's the implication of having this logging
> feature (or not) on this I-D?
> 
> You only need such loggig feature if the IPv6/MAC mapping changes. This
> I-D is simply about stable addresses... so such discussion is orthogonal.
> 
> Am I missing something?

It's about operations people (and products) that currently rely on EUI-64.
I don't think anyone's arguing that we can't move away from EUI-64 over time.

    Brian

From tjc@ecs.soton.ac.uk  Sat Oct 26 00:43:08 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E60AF11E827B for <ipv6@ietfa.amsl.com>; Sat, 26 Oct 2013 00:43:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1NoQuGjsgNZt for <ipv6@ietfa.amsl.com>; Sat, 26 Oct 2013 00:43:07 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 13EAB11E816F for <ipv6@ietf.org>; Sat, 26 Oct 2013 00:43:06 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r9Q7h1xQ016962 for <ipv6@ietf.org>; Sat, 26 Oct 2013 08:43:01 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r9Q7h1xQ016962
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1382773381; bh=aSv32y1TXWCuayLUZNi7hH7rIhY=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=eW7spgg/pjT3zA1waUc80Wju8VCv7zCvyXbQqSVBVxpwUOSGuc/sWUZFZlM95NUYC Q3mpp6ZVVx3JZX/qfqPAxeP+84roIo6kRSxh99+99U9ZVITz2PoMOn6S8/OPwwgu9m kvj5Vgf49hG7Oxvj1hZWkFQdPze/BmAL5Eurit+c=
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 p9P8h10959612525Vo ret-id none; Sat, 26 Oct 2013 08:43:01 +0100
Received: from [192.168.1.108] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r9Q7fgg0023568 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ipv6@ietf.org>; Sat, 26 Oct 2013 08:41:43 +0100
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Subject: Re: Why /64 [was Deprecating EUI-64 Based IPv6 Addresses]
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <526B0E15.8080602@si6networks.com>
Date: Sat, 26 Oct 2013 08:41:42 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|d9e74aba9561d767d4403c2b6597aed6p9P8h103tjc|ecs.soton.ac.uk|F6264230-19EB-4FEC-910C-C86F14C28A83@ecs.soton.ac.uk>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar>	<526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com>	<E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526B0A30.9060600@gmail.com> <526B0E15.8080602@si6networks.com> <F6264230-19EB-4FEC-910C-C86F14C28A83@ecs.soton.ac.uk>
To: 6man List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.1816)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p9P8h1095961252500; tid=p9P8h10959612525Vo; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r9Q7h1xQ016962
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Oct 2013 07:43:09 -0000

On 26 Oct 2013, at 01:34, Fernando Gont <fgont@si6networks.com> wrote:

> On 10/25/2013 09:17 PM, Brian E Carpenter wrote:
>> 1. Why do people find it so hard to change the Subject when changing =
the subject?
>>=20
>> 2. Since we have a bunch of IID specs that all assume /64, and a =
large bunch of
>> code (and, I suspect, silicon) that assumes /64, we really need a =
very serious
>> practical analysis document before any possible decision.
>=20
> That's why I think that relaxing the /64 requirement is a whole
> different game. -- If anything, a first step would be to relax this =
for
> hosts, and *at some point in the future*, relax it for routers --
> otherwise, a "legacy" host that expects a /64 might break or fail to =
do
> SLAAC if an updated router where to advertise, say, a /80.
>=20
> OTOH, deprecating Modified EUI-64 is a local policy which is
> incrementally-deployable.

Well yes, there=92s obviously a large deployed code base where /64 has =
been assumed. And changing that assumption may simply not be practical.

But=85 for example, some people who were concerned over the ND cache =
problem have run with /120 and DHCPv6. I=92m not advocating that. Indeed =
the homenet arch text specifically mentions not using such =93tricks" =
where the ISP only allocates one /64 to a home which requires multiple =
subnets.

I=92m just suggesting it would be interesting to spend a little time to =
figure out where the /64 really is =93burnt in=94 so that, if there were =
a desire to explore proposing a /80 or /96 or whatever for a future =
SLAAC, we would have a clearer idea of what the implications would be, =
and how/if an incremental progression to variable length SLAAC could be =
facilitated.

Tim


From fred@cisco.com  Sat Oct 26 00:57:09 2013
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBDBB11E828D for <ipv6@ietfa.amsl.com>; Sat, 26 Oct 2013 00:57:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.49
X-Spam-Level: 
X-Spam-Status: No, score=-110.49 tagged_above=-999 required=5 tests=[AWL=0.109, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z-+GIDqp831X for <ipv6@ietfa.amsl.com>; Sat, 26 Oct 2013 00:56:57 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 153DE11E8214 for <ipv6@ietf.org>; Sat, 26 Oct 2013 00:56:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1687; q=dns/txt; s=iport; t=1382774211; x=1383983811; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=SFYqdHdjN8yvc+9o4KBxkhrv8LgQ04Vj3XQ8yFTtaiU=; b=SGhSd9pq4UbvOuMbneRXj/RQeoi0xHsH6VjV3xukNH+YGEJByIB260a8 pcf/g8iCS22sMcQYI+1XdiHv68/IBbO+g5jAFeTtScXnMLIf53+ijZIWR y4KwOy/Ls8boXKImYesPxcN5b90HUKMisROMgN7nXc+EbP174Zb4fVu+q o=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAOl0a1KtJV2c/2dsb2JhbABZgweBDL5OgR4WdIIlAQEBAwF5BQsCAQgiJCERJQIEDgUIBodnAwkGrw0NiWuMZYI/MQeDH4ENA5AtgTCEQo47hTeDJoIq
X-IronPort-AV: E=Sophos;i="4.93,575,1378857600";  d="asc'?scan'208";a="276957064"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-5.cisco.com with ESMTP; 26 Oct 2013 07:56:50 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r9Q7uo1Q026398 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 26 Oct 2013 07:56:50 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.23]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.02.0318.004; Sat, 26 Oct 2013 02:56:50 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Why /64 [was Deprecating EUI-64 Based IPv6 Addresses]
Thread-Topic: Why /64 [was Deprecating EUI-64 Based IPv6 Addresses]
Thread-Index: AQHO0eDV+XxNGbX310SeHcIFG0/evpoG8gYA
Date: Sat, 26 Oct 2013 07:56:49 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553BA7B8B0@xmb-rcd-x09.cisco.com>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar>	<526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526B0A30.9060600@gmail.com>
In-Reply-To: <526B0A30.9060600@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.61.201.55]
Content-Type: multipart/signed; boundary="Apple-Mail=_823AD423-92F6-4C75-A754-AD2526B41ABA"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: Fernando Gont <fgont@si6networks.com>, Tim Chown <tjc@ecs.soton.ac.uk>, "<ipv6@ietf.org>" <ipv6@ietf.org>, Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Oct 2013 07:57:09 -0000

--Apple-Mail=_823AD423-92F6-4C75-A754-AD2526B41ABA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Oct 26, 2013, at 2:17 AM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

> 2. Since we have a bunch of IID specs that all assume /64, and a large =
bunch of
> code (and, I suspect, silicon) that assumes /64, we really need a very =
serious
> practical analysis document before any possible decision.

I find that less compelling than you, in that people can and do assign =
addresses using DHCP/DHCPv6, and for the most part use the addresses DNS =
or their communications peer tells them to use. For example, in data =
centers, I have heard suggestions from a number of quarters that would =
assign a /64 to a rack and /80's in tenants within it, using a /48 =
assigned by tenant-aware DHCP services in SDN networks. This would allow =
general data center routing to be stable (one routes to the rack) and =
leaves the differentiation among subnets for tenants local to the rack. =
The IPv6 prefix is a CIDR prefix, of a length selected by the operator, =
in a DHCP world.

--Apple-Mail=_823AD423-92F6-4C75-A754-AD2526B41ABA
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 - http://gpgtools.org

iD8DBQFSa3XabjEdbHIsm0MRAldFAKCaYL64WAdULBTe1aSa0M1u5yK3CQCgr3G3
2J4pxfMdoXX/PfXVtAGaU5I=
=7uTX
-----END PGP SIGNATURE-----

--Apple-Mail=_823AD423-92F6-4C75-A754-AD2526B41ABA--

From tjc@ecs.soton.ac.uk  Sat Oct 26 01:11:11 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6982121F9CA1 for <ipv6@ietfa.amsl.com>; Sat, 26 Oct 2013 01:11:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EMdNZdsSmSdv for <ipv6@ietfa.amsl.com>; Sat, 26 Oct 2013 01:11:08 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id AC92721E8063 for <ipv6@ietf.org>; Sat, 26 Oct 2013 01:11:07 -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 r9Q8B2O5022139 for <ipv6@ietf.org>; Sat, 26 Oct 2013 09:11:02 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r9Q8B2O5022139
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1382775062; bh=aaoE8C6WDBh4t+iznivVFHBB0JE=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=Om9hxcmfHONFp/fUr4BCC0h9kTzf3t9WNCI47JfSztE6vXN9NF3kZ8LW8e4sGhgIJ S4ItZqZOofQdb51zFZ9yopmzIgl5GJohdHFK4O1fFvvvIKLhXYdRTUmxM8pe2UBv7g EHSVcUOLrdJHSfsjnyXqzCDK0KNc9iJV79n+mUrY=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p9P9B20959612661aN ret-id none; Sat, 26 Oct 2013 09:11:02 +0100
Received: from [192.168.1.108] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r9Q8AbvW030164 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ipv6@ietf.org>; Sat, 26 Oct 2013 09:10:37 +0100
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <526B12E2.5050503@gmail.com>
Date: Sat, 26 Oct 2013 09:10:36 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|c7d4fb9d67291232de8dad9b63e0d4c7p9P9B203tjc|ecs.soton.ac.uk|57A8D976-A4FD-414E-8D79-4A7B1567DDCF@ecs.soton.ac.uk>
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com> <52697C33.7010904@gmail.com> <5269B633.8010802@si6networks.com> <5269D03A.8030809@gmail.com> <28EF616C-5765-4D3D-9593-86DE8BB538C5@ecs.soton.ac.uk> <EMEW3|6c915c4e4e63530092c3f6edabbf8a7ep9OL7r03tjc|ecs.soton.ac.uk|28EF616C-5765-4D3D-9593-86DE8BB538C5@ecs.soton.ac.uk> <526B12E2.5050503@gmail.com> <57A8D976-A4FD-414E-8D79-4A7B1567DDCF@ecs.soton.ac.uk>
To: 6man <ipv6@ietf.org>
X-Mailer: Apple Mail (2.1816)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p9P9B2095961266100; tid=p9P9B20959612661aN; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r9Q8B2O5022139
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Oct 2013 08:11:12 -0000

On 26 Oct 2013, at 01:54, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

> On 26/10/2013 09:06, Tim Chown wrote:
>>=20
>>=20
>> This is not true.  There are open source packages that allow you to =
harvest switch port, MACs, IPs etc, dual-stack.  OK, so the db gets big =
if RFC4941 refresh is rapid, but it works.
>=20
> If you happen to run such a package. But lots of sites don't, and =
maybe don't want
> to. I don't see why the IETF has the right to dictate here. That's why
> I prefer SHOULD NOT.

And lots of sites don=92t run IPv6, yet alone IPv6 SLAAC/RFC4941.=20

But as they deploy IPv6, they have a timely opportunity to review =
requirements on their management and monitoring platforms, many of which =
will have poor IPv6 support anyway. Customers should be asking their =
vendors if/how their products support IPv6 address =
tracking/accountability.  Even if parts of the campus are managed and =
relatively locked down (and thus may not use 4941 through it being =
disabled on the host), the same platform is likely to be used =
campus-wide, so support for tracking should be sought.

>> How do you prevent 4941 anyway on campus BYOD, if you allow EUI-64?  =
What product does that?
>=20
> You probably can=92t.

Can savi help here?

> Actually that's why some campuses have separate
> networks for BYOD, where other restrictions apply.

Sure, on managed administrative subnets the network and the hosts can be =
relatively locked down. But if we want to give our students/academics =
increased privacy their desktops, and the eduroam wireless where the =
BYODs are, should run 4941.  The recent NSA stuff will only increase the =
desire of university users to have greater privacy (perceived or real).

> It's about operations people (and products) that currently rely on =
EUI-64.

What are those products?  Do we have examples of where this reliance =
lies?

> I don't think anyone's arguing that we can't move away from EUI-64 =
over time.

Indeed.

Tim=

From fred@cisco.com  Sat Oct 26 01:43:00 2013
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28BFD11E8147 for <ipv6@ietfa.amsl.com>; Sat, 26 Oct 2013 01:43:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.499
X-Spam-Level: 
X-Spam-Status: No, score=-110.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nAo1FgArbIOB for <ipv6@ietfa.amsl.com>; Sat, 26 Oct 2013 01:42:54 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 8F97711E80F9 for <ipv6@ietf.org>; Sat, 26 Oct 2013 01:42:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1167; q=dns/txt; s=iport; t=1382776974; x=1383986574; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=EU7oyYE/JC8sW5Q5MxpeLXDXO4DFeNUaQhWzKsLJURw=; b=T88c0d1L7sesgwGiRbBMt0xsuvVh0AGOHbZGErqOH8bk+kJfOaa3eN9a Ntq793/GFPsGzid9d7ZgC0SKSXWWRc69j4yLOZkdpgnY4N+d493B79MSk Mi/nUni5z4Emyo6cxoW/YmfESnEItvzj7gDEYShYYZNBGjBk8iQapstSX A=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFALR/a1KtJV2c/2dsb2JhbABZgweBDL5OgR4WdIIlAQEBAwF5EAIBFhQkMiUCBA4FCAaHcwa4Zo8kMQeDH4ENA5AtgTCYNIMmgio
X-IronPort-AV: E=Sophos;i="4.93,575,1378857600";  d="asc'?scan'208";a="276949067"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-7.cisco.com with ESMTP; 26 Oct 2013 08:42:52 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r9Q8gprf025759 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 26 Oct 2013 08:42:51 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.23]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.02.0318.004; Sat, 26 Oct 2013 03:42:51 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Fernando Gont <fgont@si6networks.com>
Subject: Why /64
Thread-Topic: Why /64
Thread-Index: AQHO0ida5dK4DGXhYECHnD78yEvvsQ==
Date: Sat, 26 Oct 2013 08:42:50 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com>
In-Reply-To: <526AC8AF.4060608@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.61.201.55]
Content-Type: multipart/signed; boundary="Apple-Mail=_E43CB496-E593-4CF2-8B41-7A82E9BFC680"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, "<ipv6@ietf.org>" <ipv6@ietf.org>, Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Oct 2013 08:43:00 -0000

--Apple-Mail=_E43CB496-E593-4CF2-8B41-7A82E9BFC680
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Oct 25, 2013, at 9:38 PM, Fernando Gont <fgont@si6networks.com> =
wrote:

>> Well, you're proposing deprecating EUI-64, so there is no longer any
>> reason to be constrained to /64....=20
>=20
> Is this the sole reason for requiring subnets to be a /64?

It was the driver for the change from RFC 1884's /80 (with a 48 bit MAC =
in the IID) to RFC 2373's /64 (with an EUI-64). I would think that any =
argument today about the /64 would be about inertia if not the EUI-64.

--Apple-Mail=_E43CB496-E593-4CF2-8B41-7A82E9BFC680
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 - http://gpgtools.org

iD8DBQFSa4CrbjEdbHIsm0MRAlXkAKD6petiV3Q3yUvPEJLZMhkSVOlXOQCg73aU
DSZLabY/Hs4McBLrOObo87M=
=Jke0
-----END PGP SIGNATURE-----

--Apple-Mail=_E43CB496-E593-4CF2-8B41-7A82E9BFC680--

From cabo@tzi.org  Sat Oct 26 02:41:07 2013
Return-Path: <cabo@tzi.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AD6C11E8174 for <ipv6@ietfa.amsl.com>; Sat, 26 Oct 2013 02:41:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.207
X-Spam-Level: 
X-Spam-Status: No, score=-106.207 tagged_above=-999 required=5 tests=[AWL=0.042, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cfrq1GL2kvh0 for <ipv6@ietfa.amsl.com>; Sat, 26 Oct 2013 02:41:01 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 0F4EB11E8171 for <ipv6@ietf.org>; Sat, 26 Oct 2013 02:40:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r9Q9er3m014020; Sat, 26 Oct 2013 11:40:53 +0200 (CEST)
Received: from [192.168.217.105] (p54892A8D.dip0.t-ipconnect.de [84.137.42.141]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3889CBD0; Sat, 26 Oct 2013 11:40:53 +0200 (CEST)
Subject: Re: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification for draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Content-Type: text/plain; charset=windows-1252
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <138388CE-99F3-4F14-A17B-2D8CB2D55EFA@steffann.nl>
Date: Sat, 26 Oct 2013 11:40:51 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <015A331F-8894-4A43-B3E8-E77DE7312595@tzi.org>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <138388CE-99F3-4F14-A17B-2D8CB2D55EFA@steffann.nl>
To: Sander Steffann <sander@steffann.nl>
X-Mailer: Apple Mail (2.1816)
Cc: "ipv6@ietf.org 6man-wg" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Oct 2013 09:41:07 -0000

On 25 Oct 2013, at 19:09, Sander Steffann <sander@steffann.nl> wrote:

> make the specs a bit more flexible

Flexibility is overrated.

If you make it easier for a site to live with a /64 by making it easier =
to split that into /80 networks, the next thing you=92ll notice that =
sites start to be allocated /80s.

There has never been a reason to give a site a /64.  So arguing =93there =
is no reason to give a site a /80=94 is besides the point.  It is just a =
logical consequence of the principle of pushing out work to others.

Gr=FC=DFe, Carsten

PS.: Besides, a 64-bit IID is the minimum size where the birthday =
paradox is unlikely to bite you.


From fred@cisco.com  Sat Oct 26 04:24:35 2013
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6645611E824A for <ipv6@ietfa.amsl.com>; Sat, 26 Oct 2013 04:24:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.507
X-Spam-Level: 
X-Spam-Status: No, score=-110.507 tagged_above=-999 required=5 tests=[AWL=0.092, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id irR6z8dhswSL for <ipv6@ietfa.amsl.com>; Sat, 26 Oct 2013 04:24:29 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 94B2311E8186 for <ipv6@ietf.org>; Sat, 26 Oct 2013 04:24:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2069; q=dns/txt; s=iport; t=1382786665; x=1383996265; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=lr7D7Fawsmn2EVDykdb6izfgbF4RUns7NL4h8qr9pzQ=; b=XQoKDhcdDKN7+qpvxxZWhCqr4aAZsSOAXcej41gipxCVxeUnHTXwk8Jq Ii8+f4Rg/V4D8Xi6wDL6lSGPRjXdJ2C92Tde0veupSgPXfzq0hdV5I0l4 pAGlsnGzkRRMQvDoTK9wedO+GcVWoPtspur7ZITLaZwJbesvvR7mqFUr2 Q=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFACqma1KtJV2b/2dsb2JhbABZgweBDL5OgR4WdIIlAQEBAwF3AgULAgEIDhQZCzIlAgQOBQgGh3MGuEiPJDEHgx+BDQOQLYEwmDSBaIE+gio
X-IronPort-AV: E=Sophos;i="4.93,576,1378857600";  d="asc'?scan'208";a="276991611"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-8.cisco.com with ESMTP; 26 Oct 2013 11:24:04 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r9QBO3ns000906 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 26 Oct 2013 11:24:03 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.23]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.02.0318.004; Sat, 26 Oct 2013 06:24:03 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification for	draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
Thread-Topic: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification for	draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
Thread-Index: AQHO0aUPq0S7Vs80bkauiNcL+ai8l5oHD3GAgAAczIA=
Date: Sat, 26 Oct 2013 11:24:03 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553BA7BA90@xmb-rcd-x09.cisco.com>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <138388CE-99F3-4F14-A17B-2D8CB2D55EFA@steffann.nl> <015A331F-8894-4A43-B3E8-E77DE7312595@tzi.org>
In-Reply-To: <015A331F-8894-4A43-B3E8-E77DE7312595@tzi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.61.197.203]
Content-Type: multipart/signed; boundary="Apple-Mail=_7E6DB478-FC60-4FCD-84B3-43646F022A19"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "ipv6@ietf.org 6man-wg" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Oct 2013 11:24:35 -0000

--Apple-Mail=_7E6DB478-FC60-4FCD-84B3-43646F022A19
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Oct 26, 2013, at 11:40 AM, Carsten Bormann <cabo@tzi.org> wrote:

> PS.: Besides, a 64-bit IID is the minimum size where the birthday =
paradox is unlikely to bite you.

Given that, in the EUI-64 as we use it, 16 bits are absolutely =
predictable (we insert a well-known 16 bits), I'd be interested to see =
the proof that the modified EUI-64 and the EUI-48 are even *different* =
with respect to the birthday paradox.

Further, a discussion of the length of a field with respect to the =
birthday paradox depends on a lot of things. If the NICs in use tend to =
come from a single vendor (How many Lenovo PCs are their in your =
company?), 22 bits are highly likely to be that vendor's Vendor Code. 2 =
bits are predictable from the fact that it is an assigned unicast =
address. So the probability of a collision in that case is determined by =
24 bits of the original MAC address, not the fact that it is represented =
in a 48 or 64 bit container.

If the birthday paradox tells us that a 64 bit Modified EUI-64 is =
adequate, then a random (24 + log2(number of vendor codes in use on a =
given LAN)) bit number is adequate.

This is also non-responsive to the DHCP question; the probability of =
assigning the same IID to two different interfaces in that case =
correlates with the ability of the operator to manage IIDs, not =
probability functions.

--Apple-Mail=_7E6DB478-FC60-4FCD-84B3-43646F022A19
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 - http://gpgtools.org

iD8DBQFSa6ZLbjEdbHIsm0MRAo5kAKDQEkpv6IJvKY0nlWa7SCXkxTBSqwCeJjFo
V6lB+2wbdODN7BdMfqjTYTE=
=VN/F
-----END PGP SIGNATURE-----

--Apple-Mail=_7E6DB478-FC60-4FCD-84B3-43646F022A19--

From fred@cisco.com  Sat Oct 26 04:46:14 2013
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D23AB11E8232 for <ipv6@ietfa.amsl.com>; Sat, 26 Oct 2013 04:46:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.331
X-Spam-Level: 
X-Spam-Status: No, score=-110.331 tagged_above=-999 required=5 tests=[AWL=0.268, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NVBenusftozk for <ipv6@ietfa.amsl.com>; Sat, 26 Oct 2013 04:46:06 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id CA40211E817A for <6man@ietf.org>; Sat, 26 Oct 2013 04:46:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2974; q=dns/txt; s=iport; t=1382787967; x=1383997567; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=9h+amxGIvsRPjoDzIjdp8hP9KDX6R6a/o9Q7+qZbP6s=; b=VlIZ3/ASh6XuqDY8VTvsgLmMIumTlR1W1zeCNj9xFj5AlO2T+MnE/CZN QtYGdKnbsozEmGHj/Q7ErAtJJNWM+qy0bpFONoI0iAEgHF9d+oEEPQ+/C gizX4aesyTl/lPLhwAT9uLd8hUlvhehqSyK7Tvx4ikWj6UprC+K7dPx5h 0=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAM2qa1KtJV2Z/2dsb2JhbABZgweBDL5OgR4WdIIlAQEBAwF3AgULAgEIIhkLMhcBDQIEDgUIBodzBrhIjyQxB4MfgQ0DkC2BMJg0gWiBPoIq
X-IronPort-AV: E=Sophos;i="4.93,576,1378857600";  d="asc'?scan'208";a="276994949"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-8.cisco.com with ESMTP; 26 Oct 2013 11:45:59 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r9QBjxjW018915 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 26 Oct 2013 11:45:59 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.23]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.02.0318.004; Sat, 26 Oct 2013 06:45:58 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Fernando Gont <fernando@gont.com.ar>
Subject: Re: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification for draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
Thread-Topic: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification for draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
Thread-Index: AQHO0VVwKLd/nawZzUOPqLyJvbz9W5oHMv2A
Date: Sat, 26 Oct 2013 11:45:58 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553BA7BABF@xmb-rcd-x09.cisco.com>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <8C48B86A895913448548E6D15DA7553BA7A268@xmb-rcd-x09.cisco.com> <526A204D.8080209@gont.com.ar>
In-Reply-To: <526A204D.8080209@gont.com.ar>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.61.197.203]
Content-Type: multipart/signed; boundary="Apple-Mail=_6F97A630-26B5-461F-B04F-640EBB52C0AD"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "6man@ietf.org" <6man@ietf.org>, "<draft-gont-6man-deprecate-eui64-based-addresses@tools.ietf.org>" <draft-gont-6man-deprecate-eui64-based-addresses@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Oct 2013 11:46:14 -0000

--Apple-Mail=_6F97A630-26B5-461F-B04F-640EBB52C0AD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Oct 25, 2013, at 9:39 AM, Fernando Gont <fernando@gont.com.ar> wrote:

> You mean the advice should be "SHOULD do =
draft-ietf-6man-stable-privacy-addresses but MAY do Modified EUI-64"? or =
something else?
>=20
> Me, I'd say that the propoer advice would seem to be "SHOULD NOT do =
EUI-64", thus meaning that you can do it if you have a very good reason =
to.
>=20
> I don't personally bother if Modified EUI-64 is an option, as long as =
it's not the default option (and as long as the consequences are =
understood when overriding a more sane default).

I'll agree with you that it is fine as an option if not the default. =
Like you, I prefer a random number when SLAAC is in use. I find a lot of =
the discussion of "but you can't randomize the <whatever> bit" tiresome; =
there is no case that I'm aware of in which we look at individual bits =
in the IID to determine how it was generated, and we certainly do not =
try to extract a MAC address from it. So imposing MAC Address =
definitions on bits in the IID is an unreasonable hobble.

But "MAY" vs "SHOULD NOT"? If it can happen at all, then the vast =
majority of systems, that base the IID on a MAC address, have every =
reason to continue to do so. Until they have all been retired (how many =
systems in the world still run Windows 95?) we will have some that do. =
And by the way, the fact that someone in the IETF wrote an RFC tends to =
not motivate vendors; customer requirements motivate vendors. The MAC =
Address basis will get changed in time, but will do so when customers =
ask about it, not when the RFC Editor has finished the document =
publication process. =46rom my very pragmatic perspective, there is =
value in recognizing the fact.

Oh, by the way, there will be those that think that cryptographically =
generated and therefore secure (for some definition of that term) =
addresses have value, and the IETF will continue to recommend that. And =
then there are addresses that are manually or DHCP/DHCPv6 assigned. =
You're welcome to your opinions; they're not going away soon.

So I would not quibble over the status of the RFC 4291/4862 model beyond =
saying that *IF* SLAAC is in use, one *SHOULD* use RFC 4941 or =
draft-ietf-6man-stable-privacy-addresses.

--Apple-Mail=_6F97A630-26B5-461F-B04F-640EBB52C0AD
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 - http://gpgtools.org

iD8DBQFSa6tvbjEdbHIsm0MRAmC4AKCMYqR8uTUJBwX4LSGYcdoPWKG7RACeIVxM
0y1hA5WscuTOzbSsOXqr4SY=
=UnCH
-----END PGP SIGNATURE-----

--Apple-Mail=_6F97A630-26B5-461F-B04F-640EBB52C0AD--

From scott.brim@gmail.com  Sat Oct 26 06:09:10 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 448CD11E8232 for <ipv6@ietfa.amsl.com>; Sat, 26 Oct 2013 06:09:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.591
X-Spam-Level: 
X-Spam-Status: No, score=-102.591 tagged_above=-999 required=5 tests=[AWL=0.008, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m5VTtpcxhFrD for <ipv6@ietfa.amsl.com>; Sat, 26 Oct 2013 06:09:09 -0700 (PDT)
Received: from mail-oa0-x22b.google.com (mail-oa0-x22b.google.com [IPv6:2607:f8b0:4003:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 72BC111E8143 for <6man@ietf.org>; Sat, 26 Oct 2013 06:09:09 -0700 (PDT)
Received: by mail-oa0-f43.google.com with SMTP id m1so2009508oag.2 for <6man@ietf.org>; Sat, 26 Oct 2013 06:09:09 -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=Z9JykpOEgdXW3glx3+ouZ1TzRHW6N6ezxplxcfseB5E=; b=Iq+wlEHi9Gq2g5Oo1xWLWK0VioiMr2ViBoi7Nmt4RCy7wPMcF0UAXGq8D7rphGkVjd 4vxGrdrGGedNGRjnnG1UD89pVuXwSVc9PspoQCFooOXOtCYBNYPrE3L4njGGJNPUMqfZ pJyJYJz8KMCxhl5Bm+kjiftQNFJh9cl43ZNAfJF1E9UlzcMr9zUAIMV5ZyfEULT9Me2O /tHYdbxuWmQtsB/18X2b0i9XftTQ6I/Ae+tmORiZCuZo8nUihdyrz3uNUvvDx/UyPiyC zIksneCHX4U4lQ4cLks3ZkF3j0i0HsFr12nBxnE9bDa8VpwzKUSUar4rvqtRIpUTrfkF WP/A==
X-Received: by 10.182.113.163 with SMTP id iz3mr7208575obb.33.1382792948925; Sat, 26 Oct 2013 06:09:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.2.134 with HTTP; Sat, 26 Oct 2013 06:08:48 -0700 (PDT)
In-Reply-To: <8C48B86A895913448548E6D15DA7553BA7BABF@xmb-rcd-x09.cisco.com>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <8C48B86A895913448548E6D15DA7553BA7A268@xmb-rcd-x09.cisco.com> <526A204D.8080209@gont.com.ar> <8C48B86A895913448548E6D15DA7553BA7BABF@xmb-rcd-x09.cisco.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Sat, 26 Oct 2013 09:08:48 -0400
Message-ID: <CAPv4CP9SajtHt+JLfdFRo-mV20fSyjtNOtT-+hs5jd9BuQC09A@mail.gmail.com>
Subject: Re: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification for draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
To: "Fred Baker (fred)" <fred@cisco.com>
Content-Type: multipart/alternative; boundary=089e013cc41884cbf704e9a4922f
Cc: "6man@ietf.org" <6man@ietf.org>, Fernando Gont <fernando@gont.com.ar>, "<draft-gont-6man-deprecate-eui64-based-addresses@tools.ietf.org>" <draft-gont-6man-deprecate-eui64-based-addresses@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Oct 2013 13:09:10 -0000

--089e013cc41884cbf704e9a4922f
Content-Type: text/plain; charset=ISO-8859-1

On Sat, Oct 26, 2013 at 7:45 AM, Fred Baker (fred) <fred@cisco.com> wrote:

> But "MAY" vs "SHOULD NOT"? If it can happen at all, then the vast majority
> of systems, that base the IID on a MAC address, have every reason to
> continue to do so.


It seems reasonable to me to document a recommendation, for the future,
even if it will take 15 years for the not-best-practice to fade.  Therefore
it seems reasonable to me to put in a SHOULD, along with all of the reasons
discussed here why the installed base doesn't have to at this time.

Scott

--089e013cc41884cbf704e9a4922f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Sat, Oct 26, 2013 at 7:45 AM, Fred Baker (fred) <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:fred@cisco.com" target=3D"_blank">fred@cisco.com</a>&gt;</s=
pan> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">But &quot;MAY&quot; vs &quot;SHOULD NOT&quot=
;? If it can happen at all, then the vast majority of systems, that base th=
e IID on a MAC address, have every reason to continue to do so.</blockquote=
>

</div><br>It seems reasonable to me to document a recommendation, for the f=
uture, even if it will take 15 years for the not-best-practice to fade. =A0=
Therefore it seems reasonable to me to put in a SHOULD, along with all of t=
he reasons discussed here why the installed base doesn&#39;t have to at thi=
s time.</div>

<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Scott</div>=
</div>

--089e013cc41884cbf704e9a4922f--

From fred@cisco.com  Sat Oct 26 07:08:26 2013
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E45DC11E82AB for <ipv6@ietfa.amsl.com>; Sat, 26 Oct 2013 07:08:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.36
X-Spam-Level: 
X-Spam-Status: No, score=-110.36 tagged_above=-999 required=5 tests=[AWL=0.238, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZGZ9A-rdrLiN for <ipv6@ietfa.amsl.com>; Sat, 26 Oct 2013 07:07:45 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 9CE9211E82A2 for <6man@ietf.org>; Sat, 26 Oct 2013 07:07:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3203; q=dns/txt; s=iport; t=1382796464; x=1384006064; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=i5f5M6L72PIawdKXbguNbuDXtV1ww+Nuh2rsSdv/EHo=; b=WYBWmUlADa5nBsyIsM3qKTXEAugPsJDMaLIhSEMO+0bNhR1ulsWSubYJ ym5q9WR/oOeTUoSdIhWeFKnjJmiKFW3ix9o2izUEjVezuxsLtgNyyiJ4M Ze8eqJ6Mq+FhmwkrMuSIO+LeVDMobWh5vaJrXtPDcEA9Cu+OOX/m6v0c9 0=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgsFAB7Ma1KtJXHA/2dsb2JhbABZgweBDL5OgSAWdIIlAQEBAwF3AhACAQgEARMKGQshESUCBA4FCAaHZwMJBq4+DYlrjGWCPzEHgx+BDQOQLYEwhEKOO4U3gWiBPoIq
X-IronPort-AV: E=Sophos;i="4.93,576,1378857600";  d="asc'?scan'208,217";a="277029953"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-3.cisco.com with ESMTP; 26 Oct 2013 14:07:44 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r9QE7hiA022896 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 26 Oct 2013 14:07:43 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.23]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.02.0318.004; Sat, 26 Oct 2013 09:07:43 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification for draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
Thread-Topic: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification for draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
Thread-Index: AQHO0kyVMUtljwaBoECV1N1dSIOQ2ZoHWLCA
Date: Sat, 26 Oct 2013 14:07:43 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553BA7BC27@xmb-rcd-x09.cisco.com>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <8C48B86A895913448548E6D15DA7553BA7A268@xmb-rcd-x09.cisco.com> <526A204D.8080209@gont.com.ar> <8C48B86A895913448548E6D15DA7553BA7BABF@xmb-rcd-x09.cisco.com> <CAPv4CP9SajtHt+JLfdFRo-mV20fSyjtNOtT-+hs5jd9BuQC09A@mail.gmail.com>
In-Reply-To: <CAPv4CP9SajtHt+JLfdFRo-mV20fSyjtNOtT-+hs5jd9BuQC09A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.61.200.22]
Content-Type: multipart/signed; boundary="Apple-Mail=_5257F404-DE38-4DE9-9B55-94E3904F6A8A"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "6man@ietf.org" <6man@ietf.org>, Fernando Gont <fernando@gont.com.ar>, "<draft-gont-6man-deprecate-eui64-based-addresses@tools.ietf.org>" <draft-gont-6man-deprecate-eui64-based-addresses@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Oct 2013 14:08:27 -0000

--Apple-Mail=_5257F404-DE38-4DE9-9B55-94E3904F6A8A
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_47854CB6-A16A-4B79-B860-D6A0974A93B8"


--Apple-Mail=_47854CB6-A16A-4B79-B860-D6A0974A93B8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Oct 26, 2013, at 3:08 PM, Scott Brim <scott.brim@gmail.com>
 wrote:

>=20
> On Sat, Oct 26, 2013 at 7:45 AM, Fred Baker (fred) <fred@cisco.com> =
wrote:
> But "MAY" vs "SHOULD NOT"? If it can happen at all, then the vast =
majority of systems, that base the IID on a MAC address, have every =
reason to continue to do so.
>=20
> It seems reasonable to me to document a recommendation, for the =
future, even if it will take 15 years for the not-best-practice to fade. =
 Therefore it seems reasonable to me to put in a SHOULD, along with all =
of the reasons discussed here why the installed base doesn't have to at =
this time.

Which is the argument for saying "should 4861 or =
stable-privacy-addresses".


--Apple-Mail=_47854CB6-A16A-4B79-B860-D6A0974A93B8
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Oct 26, 2013, at 3:08 PM, Scott Brim &lt;<a href="mailto:scott.brim@gmail.com">scott.brim@gmail.com</a>&gt;</div><div>&nbsp;wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Oct 26, 2013 at 7:45 AM, Fred Baker (fred) <span dir="ltr">&lt;<a href="mailto:fred@cisco.com" target="_blank">fred@cisco.com</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">But "MAY" vs "SHOULD NOT"? If it can happen at all, then the vast majority of systems, that base the IID on a MAC address, have every reason to continue to do so.</blockquote>

</div><br>It seems reasonable to me to document a recommendation, for the future, even if it will take 15 years for the not-best-practice to fade. &nbsp;Therefore it seems reasonable to me to put in a SHOULD, along with all of the reasons discussed here why the installed base doesn't have to at this time.</div>

</div></blockquote><br></div><div>Which is the argument for saying "should 4861 or stable-privacy-addresses".</div><br></body></html>
--Apple-Mail=_47854CB6-A16A-4B79-B860-D6A0974A93B8--

--Apple-Mail=_5257F404-DE38-4DE9-9B55-94E3904F6A8A
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 - http://gpgtools.org

iD8DBQFSa8ytbjEdbHIsm0MRAq7dAJ9Fsool+fxaoRmvYl3CE4hWskaB4ACdFLmT
1xIJskEBHeVdjp8i8PLEV50=
=JcQN
-----END PGP SIGNATURE-----

--Apple-Mail=_5257F404-DE38-4DE9-9B55-94E3904F6A8A--

From cabo@tzi.org  Sat Oct 26 07:10:42 2013
Return-Path: <cabo@tzi.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B17811E82A7 for <ipv6@ietfa.amsl.com>; Sat, 26 Oct 2013 07:10:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.209
X-Spam-Level: 
X-Spam-Status: No, score=-106.209 tagged_above=-999 required=5 tests=[AWL=0.040, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2vCJcNK1-R0c for <ipv6@ietfa.amsl.com>; Sat, 26 Oct 2013 07:10:36 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 37EBD11E814D for <ipv6@ietf.org>; Sat, 26 Oct 2013 07:10:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r9QEATGX001891; Sat, 26 Oct 2013 16:10:29 +0200 (CEST)
Received: from [192.168.217.105] (p54892A8D.dip0.t-ipconnect.de [84.137.42.141]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 1E714C41; Sat, 26 Oct 2013 16:10:28 +0200 (CEST)
Subject: Re: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification for	draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Content-Type: text/plain; charset=windows-1252
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <8C48B86A895913448548E6D15DA7553BA7BA90@xmb-rcd-x09.cisco.com>
Date: Sat, 26 Oct 2013 16:10:26 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <58354929-0CB4-45F2-BA6B-759DE26180BB@tzi.org>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <138388CE-99F3-4F14-A17B-2D8CB2D55EFA@steffann.nl> <015A331F-8894-4A43-B3E8-E77DE7312595@tzi.org> <8C48B86A895913448548E6D15DA7553BA7BA90@xmb-rcd-x09.cisco.com>
To: "Fred Baker (fred)" <fred@cisco.com>
X-Mailer: Apple Mail (2.1816)
Cc: "ipv6@ietf.org 6man-wg" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Oct 2013 14:10:42 -0000

On 26 Oct 2013, at 13:24, Fred Baker (fred) <fred@cisco.com> wrote:

>> PS.: Besides, a 64-bit IID is the minimum size where the birthday =
paradox is unlikely to bite you.
>=20
> Given that, in the EUI-64 as we use it,

As you use it.  (In 6LoWPAN, we don=92t have 16 constant bits. But we do =
have OUIs.)

But I wasn=92t talking about EUI-nn at all; these are supposed (I know) =
to be managed so there aren=92t any collisions.  I was talking about =
using the IID in roles such as CGA, where it is really nice to have =
enough bits, and a small probability of collision.  64 bits (a couple of =
which are often taken for other fluff like CGA=92s Sec) is just barely =
enough.

Gr=FC=DFe, Carsten


From fred@cisco.com  Sat Oct 26 07:22:35 2013
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FE4111E8259 for <ipv6@ietfa.amsl.com>; Sat, 26 Oct 2013 07:22:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.513
X-Spam-Level: 
X-Spam-Status: No, score=-110.513 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qMDQhSsONvlE for <ipv6@ietfa.amsl.com>; Sat, 26 Oct 2013 07:22:29 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id BE8E711E814D for <ipv6@ietf.org>; Sat, 26 Oct 2013 07:22:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2060; q=dns/txt; s=iport; t=1382797349; x=1384006949; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=rc7XKUWyiSoHtxP+5XX4Kx82oZc81jh74QQLwK01gAw=; b=K4crAHuCzH37/dwIAQQuIMF9TI8salxsI6h+Rpj7xPnRXBMiKCyrkBph bCIQXHa/ueiyFlFKNhBLM5Cc3F79lLyBz1Ia3G7DiR+5GM3ZIIc2dFcKn HU/lXw3djQ5JIXjsFrztbr+VlZLb5BwGrJA9gT4G4IZj25A70bMpgBp5Z E=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgsFAGzPa1KtJXHA/2dsb2JhbABZgweBDL5OgSAWdIIlAQEBAwF3AgULAgEIDgoKGQsyJQIEDgUIBodzBrgsjyQxB4MfgQ0DkC2BMJg0gWiBPoIq
X-IronPort-AV: E=Sophos;i="4.93,576,1378857600";  d="asc'?scan'208";a="276971330"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-2.cisco.com with ESMTP; 26 Oct 2013 14:22:29 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r9QEMTfk032210 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 26 Oct 2013 14:22:29 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.23]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.02.0318.004; Sat, 26 Oct 2013 09:22:28 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification for	draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
Thread-Topic: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification for	draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
Thread-Index: AQHO0lUk+RphN9L0qk+6JEHG0Fwa8JoHXLYA
Date: Sat, 26 Oct 2013 14:22:28 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553BA7BC61@xmb-rcd-x09.cisco.com>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <138388CE-99F3-4F14-A17B-2D8CB2D55EFA@steffann.nl> <015A331F-8894-4A43-B3E8-E77DE7312595@tzi.org> <8C48B86A895913448548E6D15DA7553BA7BA90@xmb-rcd-x09.cisco.com> <58354929-0CB4-45F2-BA6B-759DE26180BB@tzi.org>
In-Reply-To: <58354929-0CB4-45F2-BA6B-759DE26180BB@tzi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.61.200.22]
Content-Type: multipart/signed; boundary="Apple-Mail=_08C6B4E2-14D4-401A-96DF-B91341B13ED5"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "ipv6@ietf.org 6man-wg" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Oct 2013 14:22:35 -0000

--Apple-Mail=_08C6B4E2-14D4-401A-96DF-B91341B13ED5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Oct 26, 2013, at 4:10 PM, Carsten Bormann <cabo@tzi.org> wrote:
> On 26 Oct 2013, at 13:24, Fred Baker (fred) <fred@cisco.com> wrote:
>>> PS.: Besides, a 64-bit IID is the minimum size where the birthday =
paradox is unlikely to bite you.
>>=20
>> Given that, in the EUI-64 as we use it,
>=20
> As you use it.  (In 6LoWPAN, we don=92t have 16 constant bits. But we =
do have OUIs.)

If by 6LowPAN you mean IEEE 802.15.4, OK. That, of course, doesn't =
generalize to "all HAN networks", which was the charter of 6LowPAN. We =
could discuss G.9972, IEEE 1901 (which has both an Internet Access and a =
HAN link layer specification), and others. But I digress.

In this context, we're talking about RFCs 4291, 4862, and 4941, =
draft-ietf-6man-stable-privacy-addresses, and the silly assumption that =
interfaces necessarily have EUI-anything addresses to base their IIDs =
on.

> But I wasn=92t talking about EUI-nn at all; these are supposed (I =
know) to be managed so there aren=92t any collisions.  I was talking =
about using the IID in roles such as CGA, where it is really nice to =
have enough bits, and a small probability of collision.  64 bits (a =
couple of which are often taken for other fluff like CGA=92s Sec) is =
just barely enough.

In which case a stable privacy address or an RFC 4941 address would not =
be directly useful.

--Apple-Mail=_08C6B4E2-14D4-401A-96DF-B91341B13ED5
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 - http://gpgtools.org

iD8DBQFSa9AcbjEdbHIsm0MRAk3JAJ4hoOKm8DyhUMvVt4vl3ydjwu/QxACglFSv
fFTV8C0LUirWRCoJesvc5XY=
=zwhD
-----END PGP SIGNATURE-----

--Apple-Mail=_08C6B4E2-14D4-401A-96DF-B91341B13ED5--

From lorenzo@google.com  Sun Oct 27 01:55:25 2013
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD09D11E8138 for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 01:55: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=[AWL=0.077, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AIWTuC9CNdT8 for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 01:55:23 -0700 (PDT)
Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 2EAF411E8140 for <ipv6@ietf.org>; Sun, 27 Oct 2013 01:55:22 -0700 (PDT)
Received: by mail-ie0-f172.google.com with SMTP id tp5so9561079ieb.3 for <ipv6@ietf.org>; Sun, 27 Oct 2013 01:55: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=CpG9PMJlYWEvBfXvBuC9GtYUNkbFJR31T+R402Et97s=; b=kaJQFXfiPbtM5f+FpGEMdilwbR/WZIcyACYVT9bihtjQEH0uqtoVRtPUl32R2eTfcK Rc3wBPdYoAnKxofO/jqn11Uh1GzCUJCAQTrwTkDAeSY8Bi5N4DJ/Gh5MxR0bTfmcUKxc pGQxP1R0wRO+nCX0GFEKGjmPzQBHRUf82UnYLtoV+t9WSsUI+IUvVdfqE3pDhsXa3oDU oH/z8CPJRKg7fLgDLqg8JpClFlsKEFvsRXrgk1TyiysU9Y4+DGXyQ/Yc7Z6iSRGa73TY QKld20ZbuCTRXBmc6S4Yzb13Pe5Ls6WV9g2eVCSlUIQC5caAQHMI6mTnZh0axy3YG0Tq llDw==
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=CpG9PMJlYWEvBfXvBuC9GtYUNkbFJR31T+R402Et97s=; b=meoxTTk8mTFHxjB6eXd2VWQLzcUOWSreXkQBPwLCWVwkFwAON+ecVuOUcq0FTtbsFZ ZLCfUFGhOjFfo0Y4Ld2wDy2DF2UiR57kHuTdmeTPZkpqcGTf7pHJbzMCGUofvqZ+Mej2 bJaslg4Bk2sAjYyMALrm0gXMyGIu1RjBO8MBi1IV3aoJydARj3IhsCjvPQjiMVKMlnCb NdVS4ES0D+tWuEIdWjqdPvfCc372KmZoBxE6ZjwxME1yvkTemg97NvZlfY/8D+9wrpk6 45qkyxz4t3PDNkoZR6f4ORAbQl5TvMM1rJuUZEeagaVlxkXXAzJioqUEO6tAZxRdpDAU EzcA==
X-Gm-Message-State: ALoCoQnXFzeMBPqdcVhps9I3N92++KOMFHZ5vXQgbm7y2GeHgbhQ7r03eCWhKqTNVFTHVRnSrafZuoO9xXd1Knitau4db74O1xib937BGzA2nmKBzzOKGWpOxAp19ZNt37QBpE4YeLZUeLnMrZqcluLRUMfawvHiwVSn7tMbWF3444A6/g7wyyDALCFpfuhkpIxbfd7RzU1t
X-Received: by 10.50.114.168 with SMTP id jh8mr4546095igb.6.1382864121101; Sun, 27 Oct 2013 01:55:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.86.106 with HTTP; Sun, 27 Oct 2013 01:55:00 -0700 (PDT)
In-Reply-To: <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sun, 27 Oct 2013 17:55:00 +0900
Message-ID: <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com>
Subject: Re: Why /64
To: "Fred Baker (fred)" <fred@cisco.com>
Content-Type: multipart/alternative; boundary=089e01229f86b6418504e9b5249a
Cc: Fernando Gont <fgont@si6networks.com>, Tim Chown <tjc@ecs.soton.ac.uk>, "<ipv6@ietf.org>" <ipv6@ietf.org>, Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 27 Oct 2013 08:55:25 -0000

--089e01229f86b6418504e9b5249a
Content-Type: text/plain; charset=ISO-8859-1

On Sat, Oct 26, 2013 at 5:42 PM, Fred Baker (fred) <fred@cisco.com> wrote:

> > Is this the sole reason for requiring subnets to be a /64?
>
> It was the driver for the change from RFC 1884's /80 (with a 48 bit MAC in
> the IID) to RFC 2373's /64 (with an EUI-64). I would think that any
> argument today about the /64 would be about inertia if not the EUI-64.
>

I think the split /64 extremely useful because it provides a minimum size
assignment that makes autoconfiguration easy, allows privacy, and gives
users the capability to number multiple applications or multiple devices
without having to use NAT.

I have personally had more than one conversation with operators who cannot
see why they would ever want to give a user more than one IPv6 address,
because a) that's what they do in IPv4, and b) a /64 is a waste of space.
Mobile operators seem particularly prone to this line of reasoning. Telling
them that there's plenty of space to give every device a /64, or that their
service is better if users are allowed more than a /64 for privacy reasons,
or that it allows users to connect multiple devices, etc. has no effect.
Saying "it's specified in the standards and some implementations might not
work if you don't do it" has proven to be a much better argument so far.
Often those same operators then come to appreciate the flexibility once
they have deployed using /64 or larger and see how it makes things better
and easier.

It's true that some operators can decide to use only DHCPv6 and hand out
/128s today, but since some platforms don't support DHCPv6, that decision
has compatibility consequences.

If we ditch the one-size-fits all subnet size and leave the subnet size up
to the operator, it's virtually certain that we will end up with some
deployments that hand out /128s. That makes IPv4-style NAT virtually
inevitable, because users will want to connect more than one device
regardless of what the operator wants them to do. Since apps have to adapt
to the lowest-common denominator connection, there's a good chance that
apps will have to keep IPv4-style NAT traversal mechanisms around forever.
I think that's a fundamentally bad deal, because there's no real reason to
employ address sharing if you have enough addresses; the side-effects of
NAT that people seem to like (e.g., security) come from stateful inpection,
not from the translation itself.

On the other hand, if we do keep a one-size-fits-all subnet size, then I
think /64 is the best choice, not just for backwards compatibility reasons,
but for lots of other reasons such as because it splits the address in two
halves that are natural machine integer sizes, provides enough space to
protect against the birthday paradox, and so on.

Cheers,
Lorenzo

--089e01229f86b6418504e9b5249a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Sat, Oct 26, 2013 at 5:42 PM, Fred Baker (fred) <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:fred@cisco.com" target=3D"_blank">fred@cis=
co.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gm=
ail_quote">



<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">&gt; Is this the sole reason for requiring subnets to be a=
 /64?<br>



<br>
It was the driver for the change from RFC 1884&#39;s /80 (with a 48 bit MAC=
 in the IID) to RFC 2373&#39;s /64 (with an EUI-64). I would think that any=
 argument today about the /64 would be about inertia if not the EUI-64.<br>



</blockquote><div><br></div><div>I think the split /64 extremely useful bec=
ause it provides a minimum size assignment that makes autoconfiguration eas=
y, allows privacy, and gives users the capability to number multiple applic=
ations or multiple devices without having to use NAT.</div>


<div><br></div><div>
I have personally had more than one conversation with operators who cannot =
see why they would ever want to give a user more than one IPv6 address, bec=
ause a) that&#39;s what they do in IPv4, and b) a /64 is a waste of space. =
Mobile operators seem particularly prone to this line of reasoning. Telling=
 them that there&#39;s plenty of space to give every device a /64, or that =
their service is better if users are allowed more than a /64 for privacy re=
asons, or that it allows users to connect multiple devices, etc. has no eff=
ect. Saying &quot;it&#39;s specified in the standards and some implementati=
ons might not work if you don&#39;t do it&quot; has proven to be a much bet=
ter argument so far. Often those same operators then come to appreciate the=
 flexibility once they have deployed using /64 or larger and see how it mak=
es things better and easier.</div>


<div><br></div><div><div>It&#39;s true that some operators can decide to us=
e only DHCPv6 and hand out /128s today, but since some platforms don&#39;t =
support DHCPv6, that decision has compatibility consequences.</div></div>


<div><br></div><div><div>If we ditch the one-size-fits all subnet size and =
leave the subnet size up to the operator, it&#39;s virtually certain that w=
e will end up with some deployments that hand out /128s. That makes IPv4-st=
yle NAT virtually inevitable, because users will want to connect more than =
one device regardless of what the operator wants them to do. Since apps hav=
e to adapt to the lowest-common denominator connection, there&#39;s a good =
chance that apps will have to keep IPv4-style NAT traversal mechanisms arou=
nd forever. I think that&#39;s a fundamentally bad deal, because there&#39;=
s no real reason to employ address sharing if you have enough addresses; th=
e side-effects of NAT that people seem to like (e.g., security) come from s=
tateful inpection, not from the translation itself.</div>


<div><br></div><div>On the other hand, if we do keep a one-size-fits-all su=
bnet size, then I think /64 is the best choice, not just for backwards comp=
atibility reasons, but for lots of other reasons such as because it splits =
the address in two halves that are natural machine integer sizes, provides =
enough space to protect against the birthday paradox, and so on.</div>


</div><div><br></div><div>Cheers,</div><div>Lorenzo</div></div></div></div>

--089e01229f86b6418504e9b5249a--

From jeroen@massar.ch  Sun Oct 27 02:26:56 2013
Return-Path: <jeroen@massar.ch>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B81F921E8094 for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 02:26:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ifWS4MkQ4BB1 for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 02:26:53 -0700 (PDT)
Received: from icaras.de.unfix.org (icaras.de.unfix.org [IPv6:2a01:4f8:130:74c1:5054:ff:fec4:f7d4]) by ietfa.amsl.com (Postfix) with ESMTP id 5623221E8089 for <ipv6@ietf.org>; Sun, 27 Oct 2013 02:26:52 -0700 (PDT)
Received: from kami.ch.unfix.org (kami.ch.unfix.org [IPv6:2001:1620:f42:99:7256:81ff:fea5:2925]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeroen) by icaras.de.unfix.org (Postfix) with ESMTPSA id 61E64801C2A2; Sun, 27 Oct 2013 10:26:43 +0100 (CET)
Message-ID: <526CDC59.4070204@massar.ch>
Date: Sun, 27 Oct 2013 10:26:49 +0100
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>, "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com>	<526AACA5.7090604@si6networks.com>	<E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<526AC8AF.4060608@si6networks.com>	<8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com>
In-Reply-To: <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Fernando Gont <fgont@si6networks.com>, Tim Chown <tjc@ecs.soton.ac.uk>, "<ipv6@ietf.org>" <ipv6@ietf.org>, Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 27 Oct 2013 09:26:56 -0000

On 2013-10-27 09:55, Lorenzo Colitti wrote:
> On Sat, Oct 26, 2013 at 5:42 PM, Fred Baker (fred) <fred@cisco.com
> <mailto:fred@cisco.com>> wrote:
> 
>     > Is this the sole reason for requiring subnets to be a /64?
> 
>     It was the driver for the change from RFC 1884's /80 (with a 48 bit
>     MAC in the IID) to RFC 2373's /64 (with an EUI-64). I would think
>     that any argument today about the /64 would be about inertia if not
>     the EUI-64.
> 
> 
> I think the split /64 extremely useful because it provides a minimum
> size assignment that makes autoconfiguration easy,

Absolutely true; but with DHCP any length would work which though is
stateful. Note that IPv4 has a autoconfig scheme too and that works fine
with a /16, thus only 16bits "lost" (as some people would say).

I am happy with the /64 though, it is nice and clean and you never have
to figure out the netmask anymore.

> allows privacy,

IMHO big nonsense. The company (amongst many others!) you work for uses
amongst others cookies to track their people, and if they really bother
could even use natural language structure, search query types, and other
behavior for breaking this 'privacy'. Also note that even if the last
64bits are random, your company should be more than able to say "oh,
there are typically X users in there, it likely is Y"...

Thus privacy, far from. The only 'privacy' you get on the IP level is
when you use the useless-for-ACL/logging is when you move to a different
network (different /48 at that, not even the /64) as then they can't
directly associate you as the previous person. But then again, those
cookies you are setting are pretty static and will nicely link them up
again.

IP-level privacy does not exist as long as upper layers have different
ways of defeating them and/or when there are statistically too few users
in even a /48.

> and gives users the capability to number multiple applications or multiple
> devices without having to use NAT.

There are a bunch of ISPs who give out "native IPv6", quite a few of
these give exactly 1 IPv6 address to their users..

As long as they do not get a routed prefix and cannot get it through
DHCPv6-PD or some other method, the user will have to NAT or do other
tricks.

For ISPs it is a business case: you want more IPs (IPv4 or IPv6), then
pay for them.

And that premise will never go away unfortunately.

As such, the rest of your mail is already happening unfortunately.

Greets,
 Jeroen


From lorenzo@google.com  Sun Oct 27 02:42:08 2013
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3D4D11E8160 for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 02:42:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.904
X-Spam-Level: 
X-Spam-Status: No, score=-1.904 tagged_above=-999 required=5 tests=[AWL=0.073,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7+eoqBaoa4Vv for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 02:42:07 -0700 (PDT)
Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com [IPv6:2607:f8b0:4001:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 55C3A11E8147 for <ipv6@ietf.org>; Sun, 27 Oct 2013 02:42:07 -0700 (PDT)
Received: by mail-ie0-f174.google.com with SMTP id qd12so9311118ieb.33 for <ipv6@ietf.org>; Sun, 27 Oct 2013 02:42:07 -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=tUvpFDlSqMFgjNcGGgxoSAx0yogFjYOF7YigeYnFdRs=; b=SdZv8wI7z9NCAUS3rzaRW2uJF1fFCtecoXVxClrA5C9nz+5YKfcll4faAxFe3BvVAG vrGDAUmJYNdFgSkCC5ibeTiWpAnjhEAXpN0UxAp0LiRhKWN8a9/0UPQYbSfgnnIXYvYw WioPt0CB4mpght0g8LlRmE5l705kuxRruPgff27Z7LwfbErUA62CrRUyset7DiZBkVWn 6qx4lPd1+idNVXCar26irDPeZKCgbfKy2749Kb1aqbRHUOVxtnlPUQqXeUCYUEFI5it4 dZcySF0AbyyU8DUUaTO4/B1VSV9vg7O+eAU54o5JVPNTxqx9Fci3QbXK8kh70tWOz64Y 9huQ==
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=tUvpFDlSqMFgjNcGGgxoSAx0yogFjYOF7YigeYnFdRs=; b=YDsQDTCGhfm79fCBs5FtN/BX1GS6A2+ArLNDz9wpQZLGa6g/ZP3xX+owECJCzL1J2b ofvtwKfr+fKwnMGzX8bfWCRDP4Brn/0uHJ+wCCcOnnK+RD9tsJ9FKAHJvbt3zru33OwA LsGSalie5cFdySDgnetw7lM+leEEvPlkfwbYeR46Prj0R470SeVOzMzAwu6IVVeLuBOY 0JOe9578xa8JuerHShUNPR8PAH90NqZ/hP5oSqJQtmwuCgRkUhi29uaJH4p2J9daPcP3 4x+NfKj4gMecYkgNsyyZ8fqiKUZm6gieKrA1idtYu/F+7FMGbIlRCJAc3LtT5viwFJFh Z3/A==
X-Gm-Message-State: ALoCoQlOUAZlWhsynWQJL6IFDR9+lYveKKjAJ+5TJvOnEV78AhiXd/hGn0k5Wxx/XoWkTYTZWSX92L1QzSGEr2zRdcBJNA4GwRTWsIraZg9GAp6ZYFGcyL1yILBUv9RyKJqDTwLlkNqtBwK+90c1cbMbNOWu55s8+QjYTWsn904vFMInXPCYDkRU4bg2oWu/misvpNScw4jd
X-Received: by 10.50.114.168 with SMTP id jh8mr4645398igb.6.1382866926807; Sun, 27 Oct 2013 02:42:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.86.106 with HTTP; Sun, 27 Oct 2013 02:41:46 -0700 (PDT)
In-Reply-To: <526CDC59.4070204@massar.ch>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sun, 27 Oct 2013 18:41:46 +0900
Message-ID: <CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com>
Subject: Re: Why /64
To: Jeroen Massar <jeroen@massar.ch>
Content-Type: multipart/alternative; boundary=089e01229f86f1db6d04e9b5cbf4
Cc: Fernando Gont <fgont@si6networks.com>, Tim Chown <tjc@ecs.soton.ac.uk>, "<ipv6@ietf.org>" <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>, Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 27 Oct 2013 09:42:08 -0000

--089e01229f86f1db6d04e9b5cbf4
Content-Type: text/plain; charset=ISO-8859-1

On Sun, Oct 27, 2013 at 6:26 PM, Jeroen Massar <jeroen@massar.ch> wrote:

> IMHO big nonsense. The company (amongst many others!) you work for uses amongst
> others cookies to track their people,
>

Not sure we want to get into that argument here, but there's a difference
because as a user you have the capability to control what cookies you
accept and when you clear them (even via a browser extension that
periodically nukes them, if you wish), but you can't really control what
address your ISP gives you.


> There are a bunch of ISPs who give out "native IPv6", quite a few of
>  these give exactly 1 IPv6 address to their users..
>
> As long as they do not get a routed prefix and cannot get it through
> DHCPv6-PD or some other method, the user will have to NAT or do other
> tricks.
>

That's interesting. I was not aware of any, at least in the residential
space. All the large deployments I know of (which presumably constitute the
vast majority of residential IPv6 access, since they're so large) hand out
at least a /64 and in most cases at least a /60. Do you have pointers to
ISPs that do this?


> For ISPs it is a business case: you want more IPs (IPv4 or IPv6), then
> pay for them.
>

They tried that in IPv4 and it didn't work, and we ended up paying the
price in increased application complexity. Here's to pigheadedly hoping we
can do better this time. :-)

Though to be fair, in IPv4 (but not in IPv6) there is real scarcity, so
it's a bit more justifiable to say that addresses need to be paid for.

--089e01229f86f1db6d04e9b5cbf4
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Sun, Oct 27, 2013 at 6:26 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><div class=3D"gmail_extra"><div class=3D"=
gmail_quote">

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div class=3D"im"><span style=3D"color:rgb(34,34,34)">IMHO=
 big nonsense. The company (amongst many others!) you work for uses=A0</spa=
n><span style=3D"color:rgb(34,34,34)">amongst others cookies to track their=
 people,</span></div>

</blockquote><div><br></div><div>Not sure we want to get into that argument=
 here, but there&#39;s a difference because as a user you have the capabili=
ty to control what cookies you accept and when you clear them (even via a b=
rowser extension that periodically nukes them, if you wish), but you can&#3=
9;t really control what address your ISP gives you.</div>

<div>=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-=
left-style:solid;padding-left:1ex"><div class=3D"im"><span style=3D"color:r=
gb(34,34,34)">There are a bunch of ISPs who give out &quot;native IPv6&quot=
;, quite a few of</span><br>

</div>
these give exactly 1 IPv6 address to their users..<br>
<br>
As long as they do not get a routed prefix and cannot get it through<br>
DHCPv6-PD or some other method, the user will have to NAT or do other<br>
tricks.<br></blockquote><div><br></div><div>That&#39;s interesting. I was n=
ot aware of any, at least in the residential space. All the large deploymen=
ts I know of (which presumably constitute the vast majority of residential =
IPv6 access, since they&#39;re so large) hand out at least a /64 and in mos=
t cases at least a /60. Do you have pointers to ISPs that do this?</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left=
-style:solid;padding-left:1ex">For ISPs it is a business case: you want mor=
e IPs (IPv4 or IPv6), then<br>


pay for them.<br></blockquote><div><br></div><div>They tried that in IPv4 a=
nd it didn&#39;t work, and we ended up paying the price in increased applic=
ation complexity. Here&#39;s to pigheadedly hoping we can do better this ti=
me. :-)</div>

<div><br></div><div>Though to be fair, in IPv4 (but not in IPv6) there is r=
eal scarcity, so it&#39;s a bit more justifiable to say that addresses need=
 to be paid for.</div></div></div></div>

--089e01229f86f1db6d04e9b5cbf4--

From jeroen@massar.ch  Sun Oct 27 03:17:10 2013
Return-Path: <jeroen@massar.ch>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18DE511E818F for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 03:17:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1rl7o1nTxTxO for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 03:17:09 -0700 (PDT)
Received: from icaras.de.unfix.org (icaras.de.unfix.org [IPv6:2a01:4f8:130:74c1:5054:ff:fec4:f7d4]) by ietfa.amsl.com (Postfix) with ESMTP id 56A1A11E8271 for <ipv6@ietf.org>; Sun, 27 Oct 2013 03:17:07 -0700 (PDT)
Received: from kami.ch.unfix.org (kami.ch.unfix.org [IPv6:2001:1620:f42:99:7256:81ff:fea5:2925]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeroen) by icaras.de.unfix.org (Postfix) with ESMTPSA id 1AC20801C2A2; Sun, 27 Oct 2013 11:16:59 +0100 (CET)
Message-ID: <526CE821.1000900@massar.ch>
Date: Sun, 27 Oct 2013 11:17:05 +0100
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com>
In-Reply-To: <CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Fernando Gont <fgont@si6networks.com>, Tim Chown <tjc@ecs.soton.ac.uk>, "<ipv6@ietf.org>" <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>, Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 27 Oct 2013 10:17:10 -0000

On 2013-10-27 10:41, Lorenzo Colitti wrote:
> On Sun, Oct 27, 2013 at 6:26 PM, Jeroen Massar <jeroen@massar.ch
> <mailto:jeroen@massar.ch>> wrote:
> 
>     IMHO big nonsense. The company (amongst many others!) you work for
>     uses amongst others cookies to track their people,
> 
> 
> Not sure we want to get into that argument here, but there's a
> difference because as a user you have the capability to control what
> cookies you accept and when you clear them (even via a browser extension
> that periodically nukes them, if you wish), but you can't really control
> what address your ISP gives you.

Cookies is just one of the many ways as per:

http://panopticlick.eff.org/

And note my comment about statistics. There is no such thing as
'privacy' on the HTTP level.

Thus stating that it is there for IPv6 in general because there are
64bits that one can randomize is nonsense too.

>     There are a bunch of ISPs who give out "native IPv6", quite a few of
>     these give exactly 1 IPv6 address to their users..
> 
>     As long as they do not get a routed prefix and cannot get it through
>     DHCPv6-PD or some other method, the user will have to NAT or do other
>     tricks.
> 
> 
> That's interesting. I was not aware of any, at least in the residential
> space. All the large deployments I know of (which presumably constitute
> the vast majority of residential IPv6 access, since they're so large)
> hand out at least a /64 and in most cases at least a /60. Do you have
> pointers to ISPs that do this?

Note that I state 'routed'.

You probably mean the ISPs who require ND-proxy to get that /64 on your
side of the link? :)

Amongst others: http://www.ipsidixit.net/2010/03/24/239/ one of many
articles on this for free.fr (the "largest IPv6 native deployment").

Liberty Global (Unity Media in Germany) is playing with DS-Lite, hence
you get 1 IPv6 address and a CGN IPv4 address (which is useless in
prime-time as those boxes cannot handle all the BitTorrent and other
heavy traffic flows).

Also for the US centric:
http://www.comcast6.net/index.php/ipv6-deployment-faq
8<----------------
With IPv6 for standalone computers, what size IPv6 prefix will I receive?
We will allocate a single IPv6 address (/128), since we know that only a
single device is connecting, with no additional need to sub-net. We plan
to continue to assess address allocation policies as we deploy,
particularly given how very new IPv6 is from an operational standpoint
globally.

When will Comcast support IPv6 for home networking?
Comcast is planning to begin pilot market deployment of IPv6 home
networking support in the near future.
------------------>8

Though that might not match reality (as I recall having heard other
stories, no facts on that at hand though) and I know at least business
folks getting a /48, that is, if they have enough leverage to get it
enabled on their link.


Oh and we are then not even talking about even the possibility of a
static prefix, typically one will rotate every 24 hours because of
'privacy' reasons and other nice annoyances to make sure people will
cough up for the business prefix...

>     For ISPs it is a business case: you want more IPs (IPv4 or IPv6), then
>     pay for them.
> 
> 
> They tried that in IPv4 and it didn't work, and we ended up paying the
> price in increased application complexity. Here's to pigheadedly hoping
> we can do better this time. :-)

Hey, I hope so too ;)

> Though to be fair, in IPv4 (but not in IPv6) there is real scarcity, so
> it's a bit more justifiable to say that addresses need to be paid for.

Partially true yes, lets not go down the spammer-rabbit-hole ;)

Greets,
 Jeroen


From v6ops@globis.net  Sun Oct 27 03:52:44 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9E1A21F9EFE for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 03:52:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jdtTVAqR2JVa for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 03:52:44 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id C05E321F9D7A for <ipv6@ietf.org>; Sun, 27 Oct 2013 03:52:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id DEFC887006F; Sun, 27 Oct 2013 11:52:42 +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 6pwATFDQrWsL; Sun, 27 Oct 2013 11:52:42 +0100 (CET)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id A0EA587006D; Sun, 27 Oct 2013 11:52:42 +0100 (CET)
Message-ID: <526CF079.7030804@globis.net>
Date: Sun, 27 Oct 2013 11:52:41 +0100
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com>
In-Reply-To: <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Fernando Gont <fgont@si6networks.com>, Tim Chown <tjc@ecs.soton.ac.uk>, "<ipv6@ietf.org>" <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>, Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 27 Oct 2013 10:52:45 -0000

Lorenzo Colitti wrote:
> On Sat, Oct 26, 2013 at 5:42 PM, Fred Baker (fred) <fred@cisco.com> wrote:
>
>>> Is this the sole reason for requiring subnets to be a /64?
>> It was the driver for the change from RFC 1884's /80 (with a 48 bit MAC in
>> the IID) to RFC 2373's /64 (with an EUI-64). I would think that any
>> argument today about the /64 would be about inertia if not the EUI-64.
>>
>
> I think the split /64 extremely useful because it provides a minimum size
> assignment that makes autoconfiguration easy, allows privacy, and gives
> users the capability to number multiple applications or multiple devices
> without having to use NAT.
>
> I have personally had more than one conversation with operators who cannot
> see why they would ever want to give a user more than one IPv6 address,
> because a) that's what they do in IPv4, and b) a /64 is a waste of space.
> Mobile operators seem particularly prone to this line of reasoning. Telling
> them that there's plenty of space to give every device a /64, or that their
> service is better if users are allowed more than a /64 for privacy reasons,
> or that it allows users to connect multiple devices, etc. has no effect.
> Saying "it's specified in the standards and some implementations might not
> work if you don't do it" has proven to be a much better argument so far.
> Often those same operators then come to appreciate the flexibility once
> they have deployed using /64 or larger and see how it makes things better
> and easier.
>
> It's true that some operators can decide to use only DHCPv6 and hand out
> /128s today, but since some platforms don't support DHCPv6, that decision
> has compatibility consequences.
>
> If we ditch the one-size-fits all subnet size and leave the subnet size up
> to the operator, it's virtually certain that we will end up with some
> deployments that hand out /128s. That makes IPv4-style NAT virtually
> inevitable, because users will want to connect more than one device
> regardless of what the operator wants them to do. Since apps have to adapt
> to the lowest-common denominator connection, there's a good chance that
> apps will have to keep IPv4-style NAT traversal mechanisms around forever.
> I think that's a fundamentally bad deal, because there's no real reason to
> employ address sharing if you have enough addresses; the side-effects of
> NAT that people seem to like (e.g., security) come from stateful inpection,
> not from the translation itself.
>
> On the other hand, if we do keep a one-size-fits-all subnet size, then I
> think /64 is the best choice, not just for backwards compatibility reasons,
> but for lots of other reasons such as because it splits the address in two
> halves that are natural machine integer sizes, provides enough space to
> protect against the birthday paradox, and so on.
>
> Cheers,
> Lorenzo
>
If I read the above, you seem to be arguing that dropping fixed /64
would be a bad thing because operators will use this as an opportunity
to limit their customers to a single IPv6 address, and yet
simultaneously you seem to be arguing that maintaing a fixed /64 is a
good thing even though it limits customers to a single subnet.

Do I understand you correctly? The logic doesn't seem very
self-consistent to me.

Me? I believe in CIDR.

-- 
Regards,
RayH


From scott.brim@gmail.com  Sun Oct 27 04:57:21 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF08611E8184 for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 04:57:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.591
X-Spam-Level: 
X-Spam-Status: No, score=-102.591 tagged_above=-999 required=5 tests=[AWL=0.008, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3p6fw+Pe419i for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 04:57:21 -0700 (PDT)
Received: from mail-ob0-x229.google.com (mail-ob0-x229.google.com [IPv6:2607:f8b0:4003:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 68A2111E8131 for <ipv6@ietf.org>; Sun, 27 Oct 2013 04:57:21 -0700 (PDT)
Received: by mail-ob0-f169.google.com with SMTP id uz6so2602713obc.14 for <ipv6@ietf.org>; Sun, 27 Oct 2013 04:57:20 -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 :cc:content-type; bh=RiB4XP9su5iM5/PZoa6O9DXk4vcDMt1Njl3oL3qPkAg=; b=giuIB/3sCQaT4N4pVgi8PP8ITis7SOJ6Nf23KvcLjvxFPaMEUyNCevhk5d60MIKjjJ 2m4MYLebSiATFz8+Dey3NP9yGS3YsGv73FzTwNfoLHFSDquVRbLSzvxrD73xuAFuq225 Ak7JTEhYf3C4+xig2abmmxjmZo0QDEWCw6A7IyZnRFUoctL/giYLGXlqjrWGrlTD4ULU xYDQZXA5jF2wW8DC+LBHYHbdUSMyMFnxU3Y0vPMX6xHvkR/CzoVv50QtYHmtLN+jDbKb JD3vcWkqUlRdOQ534yeNMjKrqn6kk95RAgP+x8j4AxDwWqQgOeS1Tdbtq19ip7aI+0cB TJ5Q==
MIME-Version: 1.0
X-Received: by 10.182.246.39 with SMTP id xt7mr10627919obc.16.1382875040614; Sun, 27 Oct 2013 04:57:20 -0700 (PDT)
Received: by 10.182.2.134 with HTTP; Sun, 27 Oct 2013 04:57:20 -0700 (PDT)
Received: by 10.182.2.134 with HTTP; Sun, 27 Oct 2013 04:57:20 -0700 (PDT)
In-Reply-To: <CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com>
Date: Sun, 27 Oct 2013 07:57:20 -0400
Message-ID: <CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com>
Subject: Re: Why /64
From: Scott Brim <scott.brim@gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: multipart/alternative; boundary=001a11c2e224908fe704e9b7afcb
Cc: Alexandru Petrescu <alexandru.petrescu@gmail.com>, "<ipv6@ietf.org>" <ipv6@ietf.org>, Tim Chown <tjc@ecs.soton.ac.uk>, "Fred Baker \(fred\)" <fred@cisco.com>, Fernando Gont <fgont@si6networks.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 27 Oct 2013 11:57:22 -0000

--001a11c2e224908fe704e9b7afcb
Content-Type: text/plain; charset=ISO-8859-1

On Oct 27, 2013 5:42 AM, "Lorenzo Colitti" <lorenzo@google.com> wrote:
>
> On Sun, Oct 27, 2013 at 6:26 PM, Jeroen Massar <jeroen@massar.ch> wrote:
>>
>> IMHO big nonsense. The company (amongst many others!) you work for
uses amongst others cookies to track their people,
>
> Not sure we want to get into that argument here, but

I _don't_ want to get into it here but I want to briefly support Lorenzo on
privacy.  Privacy through controlling tracking of an IP address is very
different in mechanism and result from higher layer end-to-end privacy.

Scott

--001a11c2e224908fe704e9b7afcb
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr"><br>
On Oct 27, 2013 5:42 AM, &quot;Lorenzo Colitti&quot; &lt;<a href=3D"mailto:=
lorenzo@google.com">lorenzo@google.com</a>&gt; wrote:<br>
&gt;<br>
&gt; On Sun, Oct 27, 2013 at 6:26 PM, Jeroen Massar &lt;<a href=3D"mailto:j=
eroen@massar.ch">jeroen@massar.ch</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; IMHO big nonsense. The company (amongst many others!) you work for=
 uses=A0amongst others cookies to track their people,<br>
&gt;<br>
&gt; Not sure we want to get into that argument here, but </p>
<p dir=3D"ltr">I _don&#39;t_ want to get into it here but I want to briefly=
 support Lorenzo on privacy.=A0 Privacy through controlling tracking of an =
IP address is very different in mechanism and result from higher layer end-=
to-end privacy.=A0 </p>

<p dir=3D"ltr">Scott </p>

--001a11c2e224908fe704e9b7afcb--

From kauer@biplane.com.au  Sun Oct 27 05:19:26 2013
Return-Path: <kauer@biplane.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5491D21F9F34 for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 05:19:26 -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=-2.599, J_CHICKENPOX_21=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e42ATB7Y7Zsy for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 05:19:25 -0700 (PDT)
Received: from ipmail06.adl2.internode.on.net (ipmail06.adl2.internode.on.net [IPv6:2001:44b8:8060:ff02:300:1:2:6]) by ietfa.amsl.com (Postfix) with ESMTP id 3563F21F9F19 for <ipv6@ietf.org>; Sun, 27 Oct 2013 05:19:22 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqQBANMDbVKWZX+7/2dsb2JhbAANTIM/TqpDlCKBMoMZAQEBBIEJCxguVxmID6RSkwiPXBaEFgOJB5AyiySIbg
Received: from eth4284.nsw.adsl.internode.on.net (HELO [192.168.1.196]) ([150.101.127.187]) by ipmail06.adl2.internode.on.net with ESMTP; 27 Oct 2013 22:49:10 +1030
Message-ID: <1382876347.3151.85.camel@karl>
Subject: Re: Why /64
From: Karl Auer <kauer@biplane.com.au>
To: ipv6@ietf.org
Date: Sun, 27 Oct 2013 23:19:07 +1100
In-Reply-To: <CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com> <CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-Mailer: Evolution 3.2.3-0ubuntu6 
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 27 Oct 2013 12:19:26 -0000

On Sun, 2013-10-27 at 07:57 -0400, Scott Brim wrote:
> I _don't_ want to get into it here but I want to briefly support Lorenzo on
> privacy.  Privacy through controlling tracking of an IP address is very
> different in mechanism and result from higher layer end-to-end privacy.

Me too.

It's easy to forget that the Internet does not consist solely of the
web. There are plenty of other things that people may not want to have
tracked via the IP address, and who knows what other protocols may yet
be developed that could benefit from the privacy extensions of IPv6?

Regards, K.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer@biplane.com.au)
http://www.biplane.com.au/kauer
http://twitter.com/kauer389

GPG fingerprint: B862 FB15 FE96 4961 BC62 1A40 6239 1208 9865 5F9A
Old fingerprint: AE1D 4868 6420 AD9A A698 5251 1699 7B78 4EEE 6017


From jeroen@massar.ch  Sun Oct 27 06:04:18 2013
Return-Path: <jeroen@massar.ch>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E08EE11E827D for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 06:04:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oAdzc3oUIk1r for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 06:04:18 -0700 (PDT)
Received: from icaras.de.unfix.org (icaras.de.unfix.org [IPv6:2a01:4f8:130:74c1:5054:ff:fec4:f7d4]) by ietfa.amsl.com (Postfix) with ESMTP id C4C2411E827C for <ipv6@ietf.org>; Sun, 27 Oct 2013 06:04:17 -0700 (PDT)
Received: from kami.ch.unfix.org (kami.ch.unfix.org [IPv6:2001:1620:f42:99:7256:81ff:fea5:2925]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeroen) by icaras.de.unfix.org (Postfix) with ESMTPSA id A8412801C2A2; Sun, 27 Oct 2013 14:04:09 +0100 (CET)
Message-ID: <526D0F47.5040803@massar.ch>
Date: Sun, 27 Oct 2013 14:04:07 +0100
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>,  Lorenzo Colitti <lorenzo@google.com>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar>	<526AA24F.6010609@gmail.com>	<526AACA5.7090604@si6networks.com>	<E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<526AC8AF.4060608@si6networks.com>	<8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com>	<CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com>	<526CDC59.4070204@massar.ch>	<CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com> <CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com>
In-Reply-To: <CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Fernando Gont <fgont@si6networks.com>, Tim Chown <tjc@ecs.soton.ac.uk>, "<ipv6@ietf.org>" <ipv6@ietf.org>, Alexandru Petrescu <alexandru.petrescu@gmail.com>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 27 Oct 2013 13:04:19 -0000

On 2013-10-27 12:57, Scott Brim wrote:
> 
> On Oct 27, 2013 5:42 AM, "Lorenzo Colitti" <lorenzo@google.com
> <mailto:lorenzo@google.com>> wrote:
>>
>> On Sun, Oct 27, 2013 at 6:26 PM, Jeroen Massar <jeroen@massar.ch
> <mailto:jeroen@massar.ch>> wrote:
>>>
>>> IMHO big nonsense. The company (amongst many others!) you work for
> uses amongst others cookies to track their people,
>>
>> Not sure we want to get into that argument here, but
> 
> I _don't_ want to get into it here but I want to briefly support Lorenzo
> on privacy.  Privacy through controlling tracking of an IP address is
> very different in mechanism and result from higher layer end-to-end
> privacy. 

It does not matter if you have 1 IPv4 address with 2000 people behind
it, or 1 /48 with 2000 people behind it.

The algorithms to de-anonimize and differentiate between the real hosts
behind them exist.

Cookies are one way to do that, complete browser profiles or other
differences in the client, be that the tcp stack level another. For
other protocols it is all much easier as they are typically already
authenticated anyway or have other bits.

As such any of these 'privacy extensions' are futile and just a lie to
the user of them that they are more "private" as for most home networks
they simply are not.

Greets,
 Jeroen


From lorenzo@google.com  Sun Oct 27 06:36:39 2013
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB8D111E817F for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 06:36:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.451
X-Spam-Level: 
X-Spam-Status: No, score=-1.451 tagged_above=-999 required=5 tests=[AWL=-0.389, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_22=0.6, NO_RELAYS=-0.001, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WiTYaBEg-ADo for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 06:36:38 -0700 (PDT)
Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com [IPv6:2607:f8b0:4001:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 2A7B221E80BC for <ipv6@ietf.org>; Sun, 27 Oct 2013 06:36:37 -0700 (PDT)
Received: by mail-ie0-f169.google.com with SMTP id ar20so9778165iec.0 for <ipv6@ietf.org>; Sun, 27 Oct 2013 06:36:35 -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=cqKzBtKqWrRBDwkjPHFJcq+pkGe9g/ODOpjX6yhfh00=; b=eYkRn6dkMKXE3+0nC/WnqC/0nDdTuxJPTF1dLTdI8Rb2HZ02RPh9k/lReR2bdafCoH v/BWo4+D0/tKTuIPVZZJBKJCye8/18uBL3Lf/3SdzgYV9ql8/EYQY1RHLOHo6YR3eDcu PmX9kMbi/U4ZLEPCZblGQrtOzID62Je4Ua6d+YYPYsMN4eMnBWjXugxXHndvUQkJniKe b0TpUQ6cmFlx66iYNoCgKfOcW7JPLlw1CYYnq5rgtmGSN7W6wwnbUZf0SNEBDdbRxts9 Ntc0aUVMNxvLOLr7ehPXZKCEGYPON7g+YSvSO7jRlq1olmeeQqAbgiAUZ2CgbQ7A6Ij5 Qb/Q==
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=cqKzBtKqWrRBDwkjPHFJcq+pkGe9g/ODOpjX6yhfh00=; b=DZoMhw/4nOzLi0ObmLY1E0RRPE9mqxnV1PDT91ohVC96/RyQsWGstbMHClWg2BWJQm vRDbw8Qln9kARsJxF1903f0MiUBXcKXfq6Ty3Ys60hzdcaO0daWk0Pa4wi3kl9v+VPHr X+iM0ttsc1yTTniPPGqVRAPpMD5BIgISshBJDkwmME6qQ7hA3bFIct6HmbrHjG1/iF0n K3tBPxdpmI8iSHUv4Mby8xdkzt6b/9ngiuspSQjUj93WJuZd6hRg3SXWfxrmn15rjbY1 oXJDkHioDbNcqNzCXaM6KSPoj3ZiTn3xmcfhbFjheiWzl3d3UjjVmfuScvnkFH1RFERA 4tLA==
X-Gm-Message-State: ALoCoQl1onyL/JCBQH44RKOcPtaNZPj4RZ0IEgG7yio0e9YhyLMIDcx98vnyC6rPZcm421tItJUizs5zWbjZEzhetWDYeY1aMhion+Qyd+fJGH/JAML6lkn6lur6LpCEtKWfj47XEGAAd/3h2sBY2pCuFVfbuy0PgazbrCXIC80CvqBqW/ywIeyZAuIH2Ig93dtnfOiR7kgg
X-Received: by 10.50.154.10 with SMTP id vk10mr5342449igb.1.1382880995197; Sun, 27 Oct 2013 06:36:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.86.106 with HTTP; Sun, 27 Oct 2013 06:36:10 -0700 (PDT)
In-Reply-To: <526CE821.1000900@massar.ch>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com> <526CE821.1000900@massar.ch>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sun, 27 Oct 2013 22:36:10 +0900
Message-ID: <CAKD1Yr138KfSo_g5mr-5r4-H8Fxrk0GUnDLy0nLHZr1z6PC_cg@mail.gmail.com>
Subject: Re: Why /64
To: Jeroen Massar <jeroen@massar.ch>
Content-Type: multipart/alternative; boundary=047d7bd755c47c7db004e9b912a6
Cc: Fernando Gont <fgont@si6networks.com>, Tim Chown <tjc@ecs.soton.ac.uk>, "<ipv6@ietf.org>" <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>, Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 27 Oct 2013 13:36:39 -0000

--047d7bd755c47c7db004e9b912a6
Content-Type: text/plain; charset=ISO-8859-1

On Sun, Oct 27, 2013 at 7:17 PM, Jeroen Massar <jeroen@massar.ch> wrote:

> Cookies is just one of the many ways as per:
>
> http://panopticlick.eff.org/


Ok, we shouldn't have gotten into this debate. I think that's worthless
(every one of tens of millions of iPhones will return the same result... ).
But sure. There are other ways to track people than via IP addresses.


> You probably mean the ISPs who require ND-proxy to get that /64 on your
> side of the link? :)
>

No, you're misinformed. I mean real DHCPv6 PD. See below.


> Amongst others: http://www.ipsidixit.net/2010/03/24/239/ one of many
> articles on this for free.fr (the "largest IPv6 native deployment").
>

Since forever Free.fr has been handing out /60 to all its customers (it's
the maximum they can hand out with 6rd using their IPv6 allocation size),
and sends an RA with a /64 by default. I believe that if you configure it
they'll send out one different prefix for each port on the box. Look for
them in your logs; I'm sure you'll still see some ff:fe in there, which
probably means autoconf.


> Liberty Global (Unity Media in Germany) is playing with DS-Lite, hence
> you get 1 IPv6 address and a CGN IPv4 address (which is useless in
> prime-time as those boxes cannot handle all the BitTorrent and other
> heavy traffic flows).
>

DS-lite is not limited to one IPv6 address. Where did you get that from? As
for DS-Lite, well, you know, there's not a lot of IPv4 left.


> http://www.comcast6.net/index.php/ipv6-deployment-faq
> 8<----------------
> With IPv6 for standalone computers, what size IPv6 prefix will I receive?
> We will allocate a single IPv6 address (/128), since we know that only a
> single device is connecting, with no additional need to sub-net. We plan
> to continue to assess address allocation policies as we deploy,
> particularly given how very new IPv6 is from an operational standpoint
> globally.
>
> When will Comcast support IPv6 for home networking?
> Comcast is planning to begin pilot market deployment of IPv6 home
> networking support in the near future.
>

That information is out of date. Comcast rolled out DHCPv6 IA_NA first, and
then (without updating the FAQ, I guess) started turning on PD (with /64s)
during 2012. Now they hand out a /60 via PD everywhere.

http://www.comcast6.net/index.php/8-ipv6-trial-news-and-information/80-ipv6-offers-many-more-ip-addresses
http://www.dslreports.com/forum/r28725662-IPv6-ALL-areas-support-60-now.

Oh and we are then not even talking about even the possibility of a
> static prefix, typically one will rotate every 24 hours because of
> 'privacy' reasons and other nice annoyances to make sure people will
> cough up for the business prefix...
>

Nope, Comcast doesn't do that - neither in IPv4 nor in IPv6. Some European
ISPs do. Where did you get your facts from?

Please check your information before presenting it as facts in this sort of
policy discussion. We really don't want to come to the wrong conclusion
because we have the wrong data.

Cheers,
Lorenzo

--047d7bd755c47c7db004e9b912a6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Sun, Oct 27, 2013 at 7:17 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><div class=3D"gmail_extra"><div class=3D"=
gmail_quote">


<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div><span style=3D"color:rgb(34,34,34)">Cookies is just o=
ne of the many ways as per:</span><br>


</div>
<br>
<a href=3D"http://panopticlick.eff.org/" target=3D"_blank">http://panopticl=
ick.eff.org/</a></blockquote><div><br></div><div>Ok, we shouldn&#39;t have =
gotten into this debate. I think that&#39;s worthless (every one of tens of=
 millions of iPhones will return the same result... ). But sure. There are =
other ways to track people than via IP addresses.</div>


<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left=
-style:solid;padding-left:1ex">You probably mean the ISPs who require ND-pr=
oxy to get that /64 on your<br>



side of the link? :)<br></blockquote><div><br></div><div>No, you&#39;re mis=
informed. I mean real DHCPv6 PD. See below.</div><div>=A0</div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1=
px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:=
1ex">


Amongst others: <a href=3D"http://www.ipsidixit.net/2010/03/24/239/" target=
=3D"_blank">http://www.ipsidixit.net/2010/03/24/239/</a> one of many<br>
articles on this for <a href=3D"http://free.fr" target=3D"_blank">free.fr</=
a> (the &quot;largest IPv6 native deployment&quot;).<br></blockquote><div><=
br></div><div>Since forever Free.fr has been handing out /60 to all its cus=
tomers (it&#39;s the maximum they can hand out with 6rd using their IPv6 al=
location size), and sends an RA with a /64 by default. I believe that if yo=
u configure it they&#39;ll send out one different prefix for each port on t=
he box. Look for them in your logs; I&#39;m sure you&#39;ll still see some =
ff:fe in there, which probably means autoconf.</div>


<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left=
-style:solid;padding-left:1ex">Liberty Global (Unity Media in Germany) is p=
laying with DS-Lite, hence<br>



you get 1 IPv6 address and a CGN IPv4 address (which is useless in<br>
prime-time as those boxes cannot handle all the BitTorrent and other<br>
heavy traffic flows).<br></blockquote><div><br></div><div>DS-lite is not li=
mited to one IPv6 address. Where did you get that from? As for DS-Lite, wel=
l, you know, there&#39;s not a lot of IPv4 left.</div><div>=A0</div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-wi=
dth:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-=
left:1ex">


<a href=3D"http://www.comcast6.net/index.php/ipv6-deployment-faq" target=3D=
"_blank">http://www.comcast6.net/index.php/ipv6-deployment-faq</a><br>
8&lt;----------------<br>
With IPv6 for standalone computers, what size IPv6 prefix will I receive?<b=
r>
We will allocate a single IPv6 address (/128), since we know that only a<br=
>
single device is connecting, with no additional need to sub-net. We plan<br=
>
to continue to assess address allocation policies as we deploy,<br>
particularly given how very new IPv6 is from an operational standpoint<br>
globally.<br>
<br>
When will Comcast support IPv6 for home networking?<br>
Comcast is planning to begin pilot market deployment of IPv6 home<br>
networking support in the near future.<br></blockquote><div><br></div><div>=
That information is out of date. Comcast rolled out DHCPv6 IA_NA first, and=
 then (without updating the FAQ, I guess) started turning on PD (with /64s)=
 during 2012. Now they hand out a /60 via PD everywhere.=A0</div>


<div><br></div><div><a href=3D"http://www.comcast6.net/index.php/8-ipv6-tri=
al-news-and-information/80-ipv6-offers-many-more-ip-addresses" target=3D"_b=
lank">http://www.comcast6.net/index.php/8-ipv6-trial-news-and-information/8=
0-ipv6-offers-many-more-ip-addresses</a></div>


<div><a href=3D"http://www.dslreports.com/forum/r28725662-IPv6-ALL-areas-su=
pport-60-now" target=3D"_blank">http://www.dslreports.com/forum/r28725662-I=
Pv6-ALL-areas-support-60-now</a>.<br></div><div><br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;bo=
rder-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">


Oh and we are then not even talking about even the possibility of a<br>
static prefix, typically one will rotate every 24 hours because of<br>
&#39;privacy&#39; reasons and other nice annoyances to make sure people wil=
l<br>
cough up for the business prefix...<br></blockquote><div><br></div><div>Nop=
e, Comcast doesn&#39;t do that - neither in IPv4 nor in IPv6. Some European=
 ISPs do. Where did you get your facts from?</div><div><br></div><div>


Please check your information before presenting it as facts in this sort of=
 policy discussion. We really don&#39;t want to come to the wrong conclusio=
n because we have the wrong data.<br></div><div><br></div><div>Cheers,</div=
>


<div>Lorenzo</div></div></div></div>

--047d7bd755c47c7db004e9b912a6--

From lorenzo@google.com  Sun Oct 27 06:39:58 2013
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D505011E817A for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 06:39:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[AWL=0.088,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P30uhsuzZvHF for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 06:39:58 -0700 (PDT)
Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id E540F21E809D for <ipv6@ietf.org>; Sun, 27 Oct 2013 06:39:57 -0700 (PDT)
Received: by mail-ie0-f181.google.com with SMTP id ar20so9255346iec.26 for <ipv6@ietf.org>; Sun, 27 Oct 2013 06:39:36 -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=X3dWBR/4knQpRCwKi1NO7y42dthMLmS7E1hdwHqpFNE=; b=EdcyQm1jjEG7VdgtPtYq4wee24xJUZSIfDdVCQ4wc6kNe3VoWisOqRU6Vm7dn3TZfz 7vnqGn01tCPOi14XiCgo/3lCWzFVGl2VRUwIia8MvG9AGcfkeD85ilZ/JWu9L9RTZ/MF MSlMEArACmvCpdkmeb3eFtXJ8ZPJKva5w9WH/pA4kDTsDsAcekWfjz3OiJiwIxnBQfZP igHH2Of/3Le+4PAi4PakLP2UuL8P3XboSNEug1sZ9QfqeRvsMPjEmWeMC4iKVODGGZTv D+DLwWHrYWmFnSaejPnrCl45ghuKFVmRJEL7Fi4/Gl5pldf2nnP9j/qZfjyvh8BnHvGd iTNg==
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=X3dWBR/4knQpRCwKi1NO7y42dthMLmS7E1hdwHqpFNE=; b=jqiZ6siD5NELZYxhPYkzjj280sUYnsbGuDkLVwWM/vl+1P0ThTBP/XDeRPMLrtdrOl VXDC5CYOO/dFRC0N4t12UFC6jFRMQlvf/aouoVUZ9/V2mwkBO2Msp9mEG3N2g0MrMfNw 9jIpjBMIV+y+Y9xM4PgkA1MqZKnY/QN8RvBkOo5T/g9Bt/9P79Ikq7ywp1cOQ90bjWf8 V49TPJjTYQO07rfgjG/A5R69G8G8aQLDImVycIluGTRlXUNLPPnFKQ/M33REwR1A7OOv s9IRiDuEfuAoCCPmT+0lomtFKm/wLzaWznL6jXPXdQFidykQDPdjv1y0KbwxyxAp9jwd tPDQ==
X-Gm-Message-State: ALoCoQksngGjBhfgvl5GoXfx2drzaGc9hoD7unXG3uN9hqgQ5BZMMqd3igVuNJqMzNhpELX+C4PlgMuEHEVV204vWh6U5ET5rjFy5meghPQ8RwvkZQ1qh3jVM8mZMbuarhPnzT1ttxd4XjJCRYz1s81vWPi2YLFiW8FBr5nBxcC9aXng/3B4x5ipQd1ZL8m3il3+IpkwvtTh
X-Received: by 10.42.84.130 with SMTP id m2mr10545969icl.16.1382881176164; Sun, 27 Oct 2013 06:39:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.86.106 with HTTP; Sun, 27 Oct 2013 06:39:14 -0700 (PDT)
In-Reply-To: <526CF079.7030804@globis.net>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CF079.7030804@globis.net>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sun, 27 Oct 2013 22:39:14 +0900
Message-ID: <CAKD1Yr21xxuiarNB71B3oDy9ob4CefnmmkCVFsTY1Pg5EFaaQw@mail.gmail.com>
Subject: Re: Re: Why /64
To: Ray Hunter <v6ops@globis.net>
Content-Type: multipart/alternative; boundary=20cf3033460f45d49d04e9b91d53
Cc: Fernando Gont <fgont@si6networks.com>, Tim Chown <tjc@ecs.soton.ac.uk>, "<ipv6@ietf.org>" <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>, Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 27 Oct 2013 13:39:59 -0000

--20cf3033460f45d49d04e9b91d53
Content-Type: text/plain; charset=ISO-8859-1

On Sun, Oct 27, 2013 at 7:52 PM, Ray Hunter <v6ops@globis.net> wrote:

> If I read the above, you seem to be arguing that dropping fixed /64
> would be a bad thing because operators will use this as an opportunity
> to limit their customers to a single IPv6 address, and yet
> simultaneously you seem to be arguing that maintaing a fixed /64 is a
> good thing even though it limits customers to a single subnet.
>
> Do I understand you correctly? The logic doesn't seem very
> self-consistent to me.
>

No, that's what I meant. I think we should keep the fixed "one subnet ==
one /64" model, and that every customer should get at more than one subnet.
The early adopters in the industry seem to be settling on /60, which is a
bit small but still quite flexible.


> Me? I believe in CIDR.
>

So do I, as long as it's larger than /64.

--20cf3033460f45d49d04e9b91d53
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Sun, Oct 27, 2013 at 7:52 PM, Ray Hunter <span dir=3D"l=
tr">&lt;<a href=3D"mailto:v6ops@globis.net" target=3D"_blank">v6ops@globis.=
net</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail=
_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style=
:solid;padding-left:1ex">

<div class=3D""><div class=3D"h5"><span style=3D"color:rgb(34,34,34)">If I =
read the above, you seem to be arguing that dropping fixed /64</span><br></=
div></div>
would be a bad thing because operators will use this as an opportunity<br>
to limit their customers to a single IPv6 address, and yet<br>
simultaneously you seem to be arguing that maintaing a fixed /64 is a<br>
good thing even though it limits customers to a single subnet.<br>
<br>
Do I understand you correctly? The logic doesn&#39;t seem very<br>
self-consistent to me.<br></blockquote><div><br></div><div>No, that&#39;s w=
hat I meant. I think we should keep the fixed &quot;one subnet =3D=3D one /=
64&quot; model, and that every customer should get at more than one subnet.=
 The early adopters in the industry seem to be settling on /60, which is a =
bit small but still quite flexible.</div>

<div>=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-=
left-style:solid;padding-left:1ex">Me? I believe in CIDR.<br></blockquote><=
div>

<br></div><div>So do I, as long as it&#39;s larger than /64.=A0</div></div>=
</div></div>

--20cf3033460f45d49d04e9b91d53--

From fernando@gont.com.ar  Sun Oct 27 07:41:37 2013
Return-Path: <fernando@gont.com.ar>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE52611E8260 for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 07:41:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LMGB2eMWfVjX for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 07:41:36 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 2C56B11E8192 for <6man@ietf.org>; Sun, 27 Oct 2013 07:41:35 -0700 (PDT)
Received: from [70.151.3.10] (helo=[192.168.118.120]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fernando@gont.com.ar>) id 1VaRX2-00046Q-3K; Sun, 27 Oct 2013 15:41:32 +0100
Message-ID: <526D1E53.5090608@gont.com.ar>
Date: Sun, 27 Oct 2013 10:08:19 -0400
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: "Fred Baker (fred)" <fred@cisco.com>,  Scott Brim <scott.brim@gmail.com>
Subject: Re: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification for draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <8C48B86A895913448548E6D15DA7553BA7A268@xmb-rcd-x09.cisco.com> <526A204D.8080209@gont.com.ar> <8C48B86A895913448548E6D15DA7553BA7BABF@xmb-rcd-x09.cisco.com> <CAPv4CP9SajtHt+JLfdFRo-mV20fSyjtNOtT-+hs5jd9BuQC09A@mail.gmail.com> <8C48B86A895913448548E6D15DA7553BA7BC27@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553BA7BC27@xmb-rcd-x09.cisco.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "6man@ietf.org" <6man@ietf.org>, "<draft-gont-6man-deprecate-eui64-based-addresses@tools.ietf.org>" <draft-gont-6man-deprecate-eui64-based-addresses@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 27 Oct 2013 14:41:37 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi, Fred,

On 10/26/2013 10:07 AM, Fred Baker (fred) wrote:
> 
>> It seems reasonable to me to document a recommendation, for the 
>> future, even if it will take 15 years for the not-best-practice 
>> to fade.  Therefore it seems reasonable to me to put in a
>> SHOULD, along with all of the reasons discussed here why the
>> installed base doesn't have to at this time.
> 
> Which is the argument for saying "should 4861 or 
> stable-privacy-addresses".

Not sure I follow: stable-privacy-addresses is expected to be used
along RFC4862..

Am I missing something?

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



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJSbR5IAAoJEJbuqe/Qdv/x0hsH/07hrBJsrS4TMnjD9zkE4uF/
7Z3iPuZdS/7nY5QIIHy1eyeDyp0+CwK6rls5PVgfZK8sgNOlUsBdo8DzeD8NBCFc
eKr+AzljqbKzIhZuHEKbeWGIEEhq5x5WA2dIdXJkhi9b7RodUpPk7aScILlKypoZ
FgZ0XLSxz5eA0I6vVP+Z7qI5sjyameHQrpI4f/VuTEcCCyAoG3iiu17s6IgBGFDZ
LRgpRvDoWt1rX34X51J8ozGL9yi+b7W16/mz4o/ycLtY1qjELvP9OHFTVwf1iI4t
dMBPrk52WnuRkXmJEus6KpBzAnSrA17+2szj6mFAkKJq/QC8NySFCDXtfrpiAcc=
=+uM5
-----END PGP SIGNATURE-----

From fgont@si6networks.com  Sun Oct 27 07:41:37 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC6F911E8240 for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 07:41:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7o3TsXRTD3TL for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 07:41:36 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 2C8F211E81D5 for <ipv6@ietf.org>; Sun, 27 Oct 2013 07:41:35 -0700 (PDT)
Received: from [70.151.3.10] (helo=[192.168.118.120]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1VaRWw-00046D-C3; Sun, 27 Oct 2013 15:41:26 +0100
Message-ID: <526D1902.7000401@si6networks.com>
Date: Sun, 27 Oct 2013 10:45:38 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com> <52697C33.7010904@gmail.com> <5269B633.8010802@si6networks.com> <5269D03A.8030809@gmail.com> <28EF616C-5765-4D3D-9593-86DE8BB538C5@ecs.soton.ac.uk> <EMEW3|6c915c4e4e63530092c3f6edabbf8a7ep9OL7r03tjc|ecs.soton.ac.uk|28EF616C-5765-4D3D-9593-86DE8BB538C5@ecs.soton.ac.uk> <526B12E2.5050503@gmail.com> <526B169A.7020208@si6networks.com> <526B203A.6040008@gmail.com>
In-Reply-To: <526B203A.6040008@gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 27 Oct 2013 14:41:37 -0000

On 10/25/2013 10:51 PM, Brian E Carpenter wrote:
>>
>> You only need such loggig feature if the IPv6/MAC mapping changes. This
>> I-D is simply about stable addresses... so such discussion is orthogonal.
>>
>> Am I missing something?
> 
> It's about operations people (and products) that currently rely on EUI-64.
> I don't think anyone's arguing that we can't move away from EUI-64 over time.

1) What's the basis for that reliance? (i.e., what for?)

2) What's the usefulness of that, if, e.g. Windows doesn't employ
Modified EUI-64?

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





From fernando@gont.com.ar  Sun Oct 27 07:41:55 2013
Return-Path: <fernando@gont.com.ar>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCAE621E80CC for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 07:41:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PhSyYYrC4cys for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 07:41:55 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 39F5D11E8192 for <ipv6@ietf.org>; Sun, 27 Oct 2013 07:41:55 -0700 (PDT)
Received: from [70.151.3.10] (helo=[192.168.118.120]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fernando@gont.com.ar>) id 1VaRXN-00047L-Lb; Sun, 27 Oct 2013 15:41:53 +0100
Message-ID: <526D24F2.7030701@gont.com.ar>
Date: Sun, 27 Oct 2013 10:36:34 -0400
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Tim Chown <tjc@ecs.soton.ac.uk>, 6man List <ipv6@ietf.org>
Subject: Re: Why /64 [was Deprecating EUI-64 Based IPv6 Addresses]
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar>	<526AA24F.6010609@gmail.com>	<526AACA5.7090604@si6networks.com>	<E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<526B0A30.9060600@gmail.com> <526B0E15.8080602@si6networks.com>	<F6264230-19EB-4FEC-910C-C86F14C28A83@ecs.soton.ac.uk> <EMEW3|d9e74aba9561d767d4403c2b6597aed6p9P8h103tjc|ecs.soton.ac.uk|F6264230-19EB-4FEC-910C-C86F14C28A83@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|d9e74aba9561d767d4403c2b6597aed6p9P8h103tjc|ecs.soton.ac.uk|F6264230-19EB-4FEC-910C-C86F14C28A83@ecs.soton.ac.uk>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 27 Oct 2013 14:41:56 -0000

On 10/26/2013 03:41 AM, Tim Chown wrote:
>> 
>> That's why I think that relaxing the /64 requirement is a whole 
>> different game. -- If anything, a first step would be to relax this
>> for hosts, and *at some point in the future*, relax it for routers
>> -- otherwise, a "legacy" host that expects a /64 might break or
>> fail to do SLAAC if an updated router where to advertise, say, a
>> /80.
>> 
>> OTOH, deprecating Modified EUI-64 is a local policy which is 
>> incrementally-deployable.
> 
> Well yes, there’s obviously a large deployed code base where /64 has
> been assumed. And changing that assumption may simply not be
> practical.

I'm not sure about whether that's practical or not.. but just wanted to
note that it's a different game.



> But… for example, some people who were concerned over the ND cache
> problem have run with /120 and DHCPv6. 

Those should call a lemon a lemon, and ask their vendors to fix their ND
implementations ;-).


> I’m not advocating that.
> Indeed the homenet arch text specifically mentions not using such
> “tricks" where the ISP only allocates one /64 to a home which
> requires multiple subnets.

So.. what do ou do in that case... IPv6 NAT?



> I’m just suggesting it would be interesting to spend a little time to
> figure out where the /64 really is “burnt in” so that, if there were
> a desire to explore proposing a /80 or /96 or whatever for a future
> SLAAC, we would have a clearer idea of what the implications would
> be, and how/if an incremental progression to variable length SLAAC
> could be facilitated.

Agreed.

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 rogerj@gmail.com  Sun Oct 27 07:50:15 2013
Return-Path: <rogerj@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46CC421F9FF3 for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 07:50:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.284
X-Spam-Level: 
X-Spam-Status: No, score=-2.284 tagged_above=-999 required=5 tests=[AWL=0.016,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lZ1K7UAIqPAc for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 07:50:14 -0700 (PDT)
Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id E87CF11E8260 for <ipv6@ietf.org>; Sun, 27 Oct 2013 07:50:10 -0700 (PDT)
Received: by mail-wg0-f45.google.com with SMTP id z12so5649041wgg.12 for <ipv6@ietf.org>; Sun, 27 Oct 2013 07:50:10 -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=x/Lw+HiMuXQnQui7kLkQthUZlHr8asaz8qni8wHwAmo=; b=BBa+vF4ZnRAYkHZ6DpsMRunKNf4Rsf5W04WQqJe4chJvs5hBUDT1A0Ml2YyqOGV2aP Yygs8LYs+oaKhNr38vzcyw6m80XIRx1YZw9aHuzwcX+uOMvJvdz0MCY2REhLBXDVvlu5 f5LeO1dFLzYQGUzxzH65wfkSGDp3BKNP+MH+atkEnIwxrcA6pIogFGPYCWy9J7WqRc3M 7jqEs0n3OsqVc4SCZXm5N6LeJiUkPMdUX+3VHfcPFluI0mKqJYVZuh+oNr3xD9kr6amK tv2H7NWaKjBt7gIn254Fr9Yig4jTSHmv9RGdeiYZRSeuaHR3drMF54NQ5VUa7CshKn7/ vh5A==
MIME-Version: 1.0
X-Received: by 10.180.149.234 with SMTP id ud10mr5507922wib.25.1382885410049;  Sun, 27 Oct 2013 07:50:10 -0700 (PDT)
Received: by 10.216.213.72 with HTTP; Sun, 27 Oct 2013 07:50:09 -0700 (PDT)
In-Reply-To: <CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com> <CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com>
Date: Sun, 27 Oct 2013 15:50:09 +0100
Message-ID: <CAKFn1SG1PC_kA-pO5Or8VyeaOzvLfpmQe0LiiYkXU_HzNqGzCQ@mail.gmail.com>
Subject: Re: Why /64
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: Scott Brim <scott.brim@gmail.com>, "<ipv6@ietf.org>" <ipv6@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 27 Oct 2013 14:50:15 -0000

On Sun, Oct 27, 2013 at 12:57 PM, Scott Brim <scott.brim@gmail.com> wrote:
>
> On Oct 27, 2013 5:42 AM, "Lorenzo Colitti" <lorenzo@google.com> wrote:
>>
>> On Sun, Oct 27, 2013 at 6:26 PM, Jeroen Massar <jeroen@massar.ch> wrote:
>>>
>>> IMHO big nonsense. The company (amongst many others!) you work for uses
>>> amongst others cookies to track their people,
>>
>> Not sure we want to get into that argument here, but
>
> I _don't_ want to get into it here but I want to briefly support Lorenzo on
> privacy.  Privacy through controlling tracking of an IP address is very
> different in mechanism and result from higher layer end-to-end privacy.

think I'll add a +1 to this one.

Privacy isn't just one single thing. That the user might lose privacy
elsewhere in the entire stack that make up Internet, that's NOT an
argument to give up /64 because we have lost privacy anyhow.

This /64 split is a good construction. Many reasons has already been
given but the three reason I can think of right now
- it split of the entire address space into two equal sized parts,
Net-prefix, and LAN-prefix
- this split is universal. It is probably one of the few thing we have
that is that clear. Let us not give it up.
- a /64 size match lots of other bit sized things

Yes you can argue any of them into death and back, but sometimes we
have to make a choice and stick with it. I'll say we stick with this
/64 LAN size.



That ISP, or whoever else, chose to give end-users a /128 do not
undermine the /64 LAN size. It is after all really upto each and every
operator to chose how they want to run their operations. All we can do
is give recommendation.





------------------------------
Roger Jorgensen      | - ROJO9-RIPE  - RJ85P-NORID
roger@jorgensen.no           | - The Future is IPv6
-------------------------------------------------------

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

From nalini.elkins@insidethestack.com  Sun Oct 27 07:59:34 2013
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 314E011E8284 for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 07:59:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.412
X-Spam-Level: 
X-Spam-Status: No, score=-2.412 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SA-A6NFL35a1 for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 07:59:26 -0700 (PDT)
Received: from nm17-vm7.access.bullet.mail.bf1.yahoo.com (nm17-vm7.access.bullet.mail.bf1.yahoo.com [216.109.115.70]) by ietfa.amsl.com (Postfix) with ESMTP id 9B0F621E80BC for <ipv6@ietf.org>; Sun, 27 Oct 2013 07:59:20 -0700 (PDT)
Received: from [66.196.81.157] by nm17.access.bullet.mail.bf1.yahoo.com with NNFMP; 27 Oct 2013 14:59:11 -0000
Received: from [66.196.81.132] by tm3.access.bullet.mail.bf1.yahoo.com with NNFMP; 27 Oct 2013 14:59:11 -0000
Received: from [127.0.0.1] by omp1008.access.mail.bf1.yahoo.com with NNFMP; 27 Oct 2013 14:59:11 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 111314.62840.bm@omp1008.access.mail.bf1.yahoo.com
Received: (qmail 35450 invoked by uid 60001); 27 Oct 2013 14:59:10 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1382885950; bh=wOKNkdars8PLDZG1U2pbwEK9JDzg+hQGDiwhUmbD9gU=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=M9GqXRiO8q9arPfEFFHASp03HBz85vQSFFvRCF6shTKjyq4uVWdB6jXMwkhXAXkgjQAKUCoiIATJqmm1mVJs3b9yIXMHITxh3Hx9J9dx9fSy/u7rF/CocW/mm+pj7z4mRTla6FCeLXyARMcrLDAkqIED8ovNXo9rxrJDgXICjOQ=
X-YMail-OSG: E3Q7NPIVM1mjLxS93qGStooceTupQQ440.tdN4CMPnzFe3I zCLYKlmGMdG1jbDG00jNE6DXuNBDOPrOzCC4ZiA077w.FwCFw3xLZ50sWFMs dSD6X1WoNwlDOy0NHkgeIK6dt3Z7ruzDuwdzCn.zqCuuqUGHtI_bao4nFVCs QDwJSXFEb_4gLOSlsAABbOHIdj7WoUTT8oMvU.a62DikDZdv09dkEegYmL8t HkSh_u0Z2wcmDF1Lu7rEbTiAKCqgq3F.WmvRFBMxwcqldGupxm01nuKH3WBG 1jCj3I1vz9mYY4FWBzgkzmAim.km4YECTpDBS9NkeWEPld4xA6OUjOs9rlO5 LuCpdUFhY0Jv9ieFmzupyOz0AgBBPpl4RJBYAcJtkE8JLY3CsBSG7er1bL9U 1Dv_TxRAQ5miJdJfpyaKUp4c.mGb.XGsNZTUPVyXKU93b9TkDEJIXv7q2sjg e3XNNz6.UddmWGS0OYLfishAECfDO9pNEmm.4Ol58jYSfF8NvMU1h0MUaQFX Zv.TSHkmynEfa6684duBuGek4lNMr3GNPgeJnGRH2.dqhviQxHXXRdOUMxNh 47h9hsyJx.oSHv97glGCT47BjSsXqerN2FJah5kbBTMwy0mFpAoqWyt5i606 AWspLK6tsLL2SYeYj_BcaBDXiJfJwdSm5Hz4CdUWXAU2oL6k.K_oYLtPI
Received: from [24.130.37.147] by web2803.biz.mail.ne1.yahoo.com via HTTP; Sun, 27 Oct 2013 07:59:10 PDT
X-Rocket-MIMEInfo: 002.001, PiA.WW91ciBwb2ludCA0IHNlZW1zIHRvIGluZGljYXRlIHRoYXQgYWxsIG5vZGVzIGluIGEgZGVzaXJlZCB0aW1lIHN5bmNocm9uaXphdGlvbiBkb21haW4gbmVlZCB0byBiZSBzeW5jaGVkIHRvIHRoZSBzYW1lIG1hc3RlciBjbG9jay7CoCBUaGlzIGhhcyBub3QgYmVlbiBteSBleHBlcmllbmNlLsKgIEFzIGxvbmcgYXMgdGhlIHJlcXVpcmVkIFN0cmF0dW0gbGV2ZWwgaXMgcmVhbGl6ZWQsIGZvciB0aGUgbGV2ZWwgPj5vZiBhY2N1cmFjeSByZXF1aXJlZCBieSB0aGUgc2l0dWF0aW9uIG9yIGFwcGxpY2F0aW8BMAEBAQE-
X-Mailer: YahooMailWebService/0.8.160.587
References: <20131017032024.5051.20799.idtracker@ietfa.amsl.com> <1381980305.36254.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com> <5263C783.1080001@globis.net> <1382396300.22968.YahooMailNeo@web2801.biz.mail.ne1.yahoo.com> <526616C4.40304@globis.net> <4FC37E442D05A748896589E468752CAA0CA88734@PWN401EA160.ent.corp.bcbsm.com> <585D21EB-BD17-40C7-9C31-67F12EC6712F@bogus.com>
Message-ID: <1382885950.30079.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com>
Date: Sun, 27 Oct 2013 07:59:10 -0700 (PDT)
From: Nalini Elkins <nalini.elkins@insidethestack.com>
Subject: Re: [v6ops] New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-04.txt
To: joel jaeggli <joelja@bogus.com>, "Ackermann, Michael" <MAckermann@bcbsm.com>
In-Reply-To: <585D21EB-BD17-40C7-9C31-67F12EC6712F@bogus.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-1551098171-557329641-1382885950=:30079"
Cc: Ray Hunter <v6ops@globis.net>, v6ops WG <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Nalini Elkins <nalini.elkins@insidethestack.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: Sun, 27 Oct 2013 14:59:34 -0000

---1551098171-557329641-1382885950=:30079
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

> >Your point 4 seems to indicate that all nodes in a desired time synchron=
ization domain need to be synched to the same master clock.=C2=A0 This has =
not been my experience.=C2=A0 As long as the required Stratum level is real=
ized, for the level >>of accuracy required by the situation or application,=
 the proper level of time synchronization is achieved.=C2=A0 Example would =
be that if one node in the NTP domain is referencing a GPS Stratum 0 and an=
other node is referencing a >>separate Stratum 0 source, the two nodes shou=
ld be Stratum 1 and within that level of accuracy.=C2=A0=C2=A0=0A=0A>stratu=
m is not an indication of either precision or accuracy it=E2=80=99s an inid=
ication of a position within the NTP heirachary.=0A=0A=0AGuys, you know, I =
wonder if this discussion of time synchronization is distracting us from th=
e point of our proposal. =C2=A0=C2=A0=0A=0AWhat we are advocating for is a =
capability for embedded diagnostics and performance for all upper layer pro=
tocols that is relatively simple to implement. =C2=A0 I am thinking more an=
d more that our PDM 2 proposal which does not require time synchronization =
is the way to go. =C2=A0 Let me say that this is my opinion only! =C2=A0 Ot=
hers on our team believe that they can indeed do time synch within their da=
ta centers and want the enhanced capabilities of PDM 1 which requires time =
synch.=0A=0ABTW, we have discussed the proposals for PDMs already with one =
end host OS vendor who, on initial look, believes it will be easy to implem=
ent and should be quite useful. =C2=A0 We are setting up more discussions w=
ith their engineering team to see if they can tell us where the pit falls i=
n our thinking might be. =C2=A0=C2=A0I hope I can get them to comment publi=
cly. =C2=A0 But, that will take a while.=0A=0AAlso, one of my guys has alre=
ady done a prototype implementation of PDM 1 going from a simple client to =
server which I can show all who are interested in Vancouver. =C2=A0=C2=A0=
=0A=C2=A0=0A=0AThanks,=0A=0ANalini Elkins=0AInside Products, Inc.=0A(831) 6=
59-8360=0Awww.insidethestack.com=0A=0A=0A=0A_______________________________=
_
---1551098171-557329641-1382885950=:30079
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:ar=
ial, helvetica, sans-serif;font-size:12pt"><div><span><span style=3D"font-f=
amily: 'times new roman', 'new york', times, serif;">&gt; &gt;Your point 4 =
seems to indicate that all nodes in a desired time synchronization domain n=
eed to be synched to the same master clock.&nbsp; This has not been my expe=
rience.&nbsp; As long as the required Stratum level is realized, for the le=
vel &gt;&gt;of accuracy required by the situation or application, the prope=
r level of time synchronization is achieved.&nbsp; Example would be that if=
 one node in the NTP domain is referencing a GPS Stratum 0 and another node=
 is referencing a &gt;&gt;separate Stratum 0 source, the two nodes should b=
e Stratum 1 and within that level of accuracy.&nbsp;&nbsp;</span><br style=
=3D"font-family: 'times new roman', 'new york', times, serif;"><br style=3D=
"font-family: 'times new roman', 'new york', times, serif;"><span
 style=3D"font-family: 'times new roman', 'new york', times, serif;">&gt;st=
ratum is not an indication of either precision or accuracy it=E2=80=99s an =
inidication of a position within the NTP heirachary.</span><br style=3D"fon=
t-family: 'times new roman', 'new york', times, serif;"></span></div><div s=
tyle=3D"color: rgb(0, 0, 0); font-size: 16px; font-family: 'times new roman=
', 'new york', times, serif; background-color: transparent; font-style: nor=
mal;"><span><span style=3D"font-family: 'times new roman', 'new york', time=
s, serif;"><br></span></span></div><div style=3D"color: rgb(0, 0, 0); font-=
size: 16px; font-family: 'times new roman', 'new york', times, serif; backg=
round-color: transparent; font-style: normal;"><span><span style=3D"font-fa=
mily: 'times new roman', 'new york', times, serif;">Guys, you know, I wonde=
r if this discussion of time synchronization is distracting us from the poi=
nt of our proposal. &nbsp;&nbsp;</span></span></div><div style=3D"color: rg=
b(0, 0, 0);
 font-size: 16px; font-family: 'times new roman', 'new york', times, serif;=
 background-color: transparent; font-style: normal;"><span><span style=3D"f=
ont-family: 'times new roman', 'new york', times, serif;"><br></span></span=
></div><div style=3D"color: rgb(0, 0, 0); font-size: 16px; font-family: 'ti=
mes new roman', 'new york', times, serif; background-color: transparent; fo=
nt-style: normal;"><span><span style=3D"font-family: 'times new roman', 'ne=
w york', times, serif;">What we are advocating for is a capability for embe=
dded diagnostics and performance for all upper layer protocols that is rela=
tively simple to implement. &nbsp; I am thinking more and more that our PDM=
 2 proposal which does not require time synchronization is the way to go. &=
nbsp; Let me say that this is my opinion only! &nbsp; Others on our team be=
lieve that they can indeed do time synch within their data centers and want=
 the enhanced capabilities of PDM 1 which requires time
 synch.</span></span></div><div style=3D"color: rgb(0, 0, 0); font-size: 16=
px; font-family: 'times new roman', 'new york', times, serif; background-co=
lor: transparent; font-style: normal;"><span><span style=3D"font-family: 't=
imes new roman', 'new york', times, serif;"><br></span></span></div><div st=
yle=3D"color: rgb(0, 0, 0); font-size: 16px; font-family: 'times new roman'=
, 'new york', times, serif; background-color: transparent; font-style: norm=
al;"><span><span style=3D"font-family: 'times new roman', 'new york', times=
, serif;">BTW, w</span></span><span style=3D"background-color: transparent;=
">e have discussed the proposals for PDMs already with one end host OS vend=
or who, on initial look, believes it will be easy to implement and should b=
e quite useful. &nbsp; We are setting up more discussions with their engine=
ering team to see if they can tell us where the pit falls in our thinking m=
ight be. &nbsp;&nbsp;</span><span style=3D"background-color: transparent;">=
I
 hope I can get them to comment publicly. &nbsp; But, that will take a whil=
e.</span></div><div style=3D"color: rgb(0, 0, 0); font-size: 16px; font-fam=
ily: 'times new roman', 'new york', times, serif; background-color: transpa=
rent; font-style: normal;"><span style=3D"background-color: transparent;"><=
br></span></div><div style=3D"color: rgb(0, 0, 0); font-size: 16px; font-fa=
mily: 'times new roman', 'new york', times, serif; background-color: transp=
arent; font-style: normal;"><span style=3D"background-color: transparent;">=
Also, one of my guys has already done a prototype implementation of PDM 1 g=
oing from a simple client to server which I can show all who are interested=
 in Vancouver. &nbsp;&nbsp;</span></div><div style=3D"color: rgb(0, 0, 0); =
font-size: 16px; font-family: 'times new roman', 'new york', times, serif; =
background-color: transparent; font-style: normal;"><span style=3D"font-fam=
ily: arial, helvetica, sans-serif; font-size:
 12pt;">&nbsp;</span><br></div><div>Thanks,</div><div><br></div><div>Nalini=
 Elkins<br>Inside Products, Inc.<br>(831) 659-8360<br>www.insidethestack.co=
m<br></div><br>  <div style=3D"font-family: arial, helvetica, sans-serif; f=
ont-size: 12pt;"> <div style=3D"font-family: 'times new roman', 'new york',=
 times, serif; font-size: 12pt;"> <div dir=3D"ltr"> <hr size=3D"1">  </div>=
<div class=3D"y_msg_container">&nbsp;</div> </div> </div>  </div></body></h=
tml>
---1551098171-557329641-1382885950=:30079--

From rogerj@gmail.com  Sun Oct 27 07:59:57 2013
Return-Path: <rogerj@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4ED2221E80C9 for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 07:59:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.286
X-Spam-Level: 
X-Spam-Status: No, score=-2.286 tagged_above=-999 required=5 tests=[AWL=0.014,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7czWGVK6TWfN for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 07:59:35 -0700 (PDT)
Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com [IPv6:2a00:1450:400c:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id 1573921E80CE for <6man@ietf.org>; Sun, 27 Oct 2013 07:59:20 -0700 (PDT)
Received: by mail-wg0-f54.google.com with SMTP id c11so5625139wgh.33 for <6man@ietf.org>; Sun, 27 Oct 2013 07:59:19 -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 :cc:content-type; bh=z0zbtc+WQlpyHz/pHSUnGyOt49PCaeOq1gdaf96ZNco=; b=hb2LW7k5eZs4qJUggrhmmN79AT+ebatJuL44rSJHuYr0Sat84i1fFJsCYhdSlEcsmN T6tOnxi5GVy3zOsTKziETLSjaNv5knvKSI6CT3CbLSnF+1HFwG319RwzfqwonbhMid2q dA4KL/KVd7DHen9wwUQC5Dbed0ITqBESio6GgxBI1G4I5WRM6wxFk1/jwiZIthvvxtaO ffDK2FqBjBVxP/NHEoCf6hudcAWfF08OeZW6PaWARWoh1tVBtNWyz/QiZ6ShZfr1by6+ jaeNuHp34zFboAho7NOXTA2jZ1gvnftcssfYqIh6I6kRY6thfFyr/jCim4GUZoydFyCa pO/w==
MIME-Version: 1.0
X-Received: by 10.194.9.100 with SMTP id y4mr10353988wja.22.1382885959604; Sun, 27 Oct 2013 07:59:19 -0700 (PDT)
Received: by 10.216.213.72 with HTTP; Sun, 27 Oct 2013 07:59:19 -0700 (PDT)
In-Reply-To: <52695DDE.70909@gont.com.ar>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar>
Date: Sun, 27 Oct 2013 15:59:19 +0100
Message-ID: <CAKFn1SEeXOASgFUny4qB6mjzDy=M2CJ9mrpkswzKnh9JNzCv-A@mail.gmail.com>
Subject: Re: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification for draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: Fernando Gont <fernando@gont.com.ar>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "6man@ietf.org" <6man@ietf.org>, draft-gont-6man-deprecate-eui64-based-addresses@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 27 Oct 2013 14:59:57 -0000

On Thu, Oct 24, 2013 at 7:50 PM, Fernando Gont <fernando@gont.com.ar> wrote:
> Folks,
>
> We have posted a new I-D entitled "Deprecating EUI-64 Based IPv6
> Addresses"
> (http://www.ietf.org/internet-drafts/draft-gont-6man-deprecate-eui64-based-addresses-00.txt).
>
> It's a spin-off of the work we've been doing on IPv6 addressing
> secuity/privacy considerations
> (draft-ietf-6man-ipv6-address-generation-privacy and
> draft-ietf-6man-stable-privacy-addresses), and the idea had already been
> discussed among several folks mstly off-list and at IETF meeting corridors.
>
> Any comments will be appreciated.

I've read through the other threads and I still have this one question
- why bother?

I see several reasons to not recommend or require eui64 based
addresses, but that is all.
I see no real reason to deprecate it really, the affected userbase and
implementation are way too big to go to that step.
It is probably one of the cases that people will stop using it if we
let them have the options of not using it, so I say - let time do the
job of deprecating it.



-- 

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

From ayourtch@gmail.com  Fri Oct 25 15:40:13 2013
Return-Path: <ayourtch@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05A7411E819C for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 15:40:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p9+hyRXANOJ4 for <ipv6@ietfa.amsl.com>; Fri, 25 Oct 2013 15:40:06 -0700 (PDT)
Received: from mail-qe0-x22f.google.com (mail-qe0-x22f.google.com [IPv6:2607:f8b0:400d:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 5133021F8411 for <ipv6@ietf.org>; Fri, 25 Oct 2013 15:40:04 -0700 (PDT)
Received: by mail-qe0-f47.google.com with SMTP id b4so2739919qen.20 for <ipv6@ietf.org>; Fri, 25 Oct 2013 15:39:41 -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 :cc:content-type; bh=UfNIAU7rUsIeETLelXdLEbfvRYAfx50uNGJ6tXt71Rg=; b=RX5L60EsxlLqItRNqvyzZgzMS2KBxlVcnvMyQ0xb4CluXfRR4Ufq21kXWsPctjTC+l sK7yhQvdTG3shCzbO0+rMx/4h2xXIZ+ZRbEicw2BNwWnME7MF1og0uHuetGyo1zrwRB6 qqng9Zw3jID5s4HxdaQvT3zNbCgbNLaKPRIPEX5gFpP2SVUyYfWDSkrGqV+bcnsRdh6X Mnf4CRTDTvwN5+qYErs5KgnMSmgGGyj/7sEip/FGXSSSHyPctK2g2AxeUWD4vakgbC6v yo/XHTvRO6vpJI0iUN67OuY2r5TMcv3rhSepXM0khopTLVFrwJ0ogKuBaNsO2301e0+L mURg==
MIME-Version: 1.0
X-Received: by 10.224.12.207 with SMTP id y15mr14619199qay.101.1382740780946;  Fri, 25 Oct 2013 15:39:40 -0700 (PDT)
Received: by 10.96.12.199 with HTTP; Fri, 25 Oct 2013 15:39:40 -0700 (PDT)
In-Reply-To: <008501ced1cf$2fab1620$8f014260$@rozanak.com>
References: <014301cece8a$2b780e20$82682a60$@rozanak.com> <CAPi140PStSx+HDM9rpgVjPed3OFD=gpsXkOdH2HiC7mf350f+Q@mail.gmail.com> <008501ced1cf$2fab1620$8f014260$@rozanak.com>
Date: Sat, 26 Oct 2013 00:39:40 +0200
Message-ID: <CAPi140N-rxv1QaBwiJ=Egp=1162ttWg=iOuFWsCrEOD_YcAwSQ@mail.gmail.com>
Subject: Re: ra privacy: an improvement to privacy extension plus source code
From: Andrew Yourtchenko <ayourtch@gmail.com>
To: Hosnieh Rafiee <ietf@rozanak.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Sun, 27 Oct 2013 08:16:46 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Oct 2013 22:40:13 -0000

Hi Hosnieh,

On 10/26/13, Hosnieh Rafiee <ietf@rozanak.com> wrote:
> Hi Andrew,
> Thanks a lot for taking time to review this
> http://tools.ietf.org/html/draft-rafiee-6man-ra-privacy .
>
>> "- RFC 4941 specifies the use of EUI-64 to generate the public address
>>    of node
>> "
>>
>> I would not agree with this. 4941 refers to 4862 for generating the
>> public
>> address, which in turn suggests to use "interface identifier"
>> when creating a global address, and does not mandate EUI-64 as the only
>> mechanism (as evidenced in some implementations, namely, Windows). The
>> 4291, on the other hand, does talk about EUI-64 *format* but it also
>> specifically mentions the MAC addresses are not necessary to be used. So,
>> IMHO this is not a problem.
>
> I call this the problem because when you have both temporary addresses and
> public/permanent addresses that is generated based on EUI-64 or
> EUI-48(MAC),
> your public address will allow the attackers to track your node.

http://www.ietf.org/id/draft-gont-6man-deprecate-eui64-based-addresses-00.txt
: short and to the point.

>
>>
>> Anyway if the nodes want to use the stable public addresses that are
>> scan-
>> resistant, there is a draft by Fernando Gont which solves this problem.
> I'd
>> rather see you contribute to that one if that solution is not good enough
> you
>> think, rather than having yet another fork.
>
> I guess you missed the point again. That draft generates a stable IID which
> means that the node will have the same IID whenever it is fixed in a same
> network. IPv6 addresses are the public addresses so the node use this
> address to access websites or other data through the internet and this
> address soon will be known to all websites or resources on that this user
> use it. If as a mistake this user also check a resources which belongs to
> an
> attacker. The attacker will have his IP address and this IP never changes
> until the router prefix changes. This actually will not happen at least in
> the short time or it can be permanent.
> So, this allows the attacker to access the information of this user.
> This is why I like privacy extension approach more. Because it also changes
> the IID within the same subnet but in ra-privacy, I explained that if the
> node wants to have this public addresses it should not generate it based on
> EUI-64 or MAC and might change it based on Stable addresses that, at least,
> we can decrease the chance of exposing hardware information.
> The new draft recently sent  "deprecated addresses" actually contains most
> part of information which this draft was addressed and addressing.
>
>

Please re-read the
https://datatracker.ietf.org/doc/draft-ietf-6man-stable-privacy-addresses/?include_text=1.
It solves this problem imho as well.

I like the privacy, but I severely dislike the pain and additional
cost that the frivolous usage of it inflicts on the real-world network
administrators of the large networks.

Read e.g. the http://www.gossamer-threads.com/lists/nsp/ipv6/47882 for
more info.

>
>>    - If the node is changing the physical link, it may keep the IID
>>    already used on the link it is leaving, to form an IPv6 address on
>>    the new link using SLAAC.
>> "
>>
>> This is a problem I agree is a problem, which has been fixed in some
>> implementations; and arguably in the other implementations a bug should
>> be
>> filed "If the prefix changes, the node MUST NOT reuse the already used
>> temporary IID". But, maybe to fix this bug, an update to
>> 4941 could be useful.
>
> You say this fixed in implementation. My question is why we have standards?
> If implementers wants to implement something in whatever way they like,
> then
> I guess we cannot communicate via internet anymore as it would be ruled by
> incompatible systems and we will back to 19 century.
> I am open to suggestions and improve it.

I am saying the node maintaining IID on link change is the only valid
point in this draft in my opinion, no need to argue it :-)

Also I am saying that picking the IID is a node-local decision which
does not affect the communication, and it's not as dramatic as
portrayed above.

IETF is about rough consensus and running code - so if you have
running code and you get rough consensus on this draft being a
positive thing - my opinion does not really count, nor should it - I
was simply stating my reasons for thinking the way I am thinking.

We do not have to agree on everything. I am glad that you found some
of my comments useful.

--a

>
>
>> Fernando's draft also specifies that IID of the "stable addresses"
>> needs to be different on different prefixes, so this problem only applies
> to
>> temporary addresses.
>
> That is true. Ra-privacy has no recommendation about public addresses
> except
> not to use the hardware information or EUI-64 RFC. The recommendation in
> this draft is about temporary addresses and a few explanation of the
> current
> problem with Privacy Extension.
>
>
>>
>> I read the 4941 and I think it is flexible enough allow oneself to both
> shoot
>> oneself in the foot and to make a sane implementation. So I am not sure
> this
>> is a valid problem to solve.
>
> I just noticed some ambiguous words in this RFC. It does not effect on the
> proper implementation but will effect on new implementation of this RFC or
> any bad implementation of this RFC.
>
>> "
>>    - This document also clarifies the use of other algorithm and compare
>>    it with CGA and DHCPv6 when there is no stable storage available. So
>>    that the node may be able to make use of a greatly randomized IID
>>    because, according to section 3.2.2 of RFC 4941, there is nothing to
>>    force the use of RFC 4086.
>> "
>>
>> We had tons of the discussions about the algorithm. I maintain that it
> boils
>> down to:
>
>> "On each link change, take 64 bits of random data and put it into IID.
>> Ensure the random data is good quality".
>>
>> There is a significant body of work on generating good random numbers and
> I
>> do not see this draft contributing anything new to it, in this regard.
>>
>> So, as I support only 1 portion of the draft out of 4, in general I am
> still
>> opposed to it.
>>
>
> Spending time on implementation was only for showing how ra-privacy works
> in
> compare with Privacy extension and how good it can generates random number
> with this suggested algorithm. Test it please and then say it wasn't any
> contribution for generating a good random number.
> Again I am open to good suggestions if you have any.
>
> Thank you,
> -----------smile----------
> Hosnieh
> . success is a journey, not a destination..
> You cannot change your destination overnight, but you can change your
> direction ... Focus on the journey
>
>
>
>

From alvarezp@alvarezp.ods.org  Sun Oct 27 08:53:36 2013
Return-Path: <alvarezp@alvarezp.ods.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0C1811E8170 for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 08:53:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z4vtwyi20o6b for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 08:53:31 -0700 (PDT)
Received: from sobre.alvarezp.com (sobre.alvarezp.com [173.230.155.94]) by ietfa.amsl.com (Postfix) with ESMTP id 3287C11E828D for <ipv6@ietf.org>; Sun, 27 Oct 2013 08:53:27 -0700 (PDT)
Received: from [192.168.2.208] (189.220.45.207.cable.dyn.cableonline.com.mx [189.220.45.207]) by sobre.alvarezp.com (Postfix) with ESMTPSA id A3655613D; Sun, 27 Oct 2013 11:53:25 -0400 (EDT)
Message-ID: <526D3706.5070409@alvarezp.ods.org>
Date: Sun, 27 Oct 2013 08:53:42 -0700
From: Octavio Alvarez <alvarezp@alvarezp.ods.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130821 Icedove/17.0.8
MIME-Version: 1.0
To: Jeroen Massar <jeroen@massar.ch>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com>	<526AACA5.7090604@si6networks.com>	<E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<526AC8AF.4060608@si6networks.com>	<8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch>
In-Reply-To: <526CDC59.4070204@massar.ch>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Alexandru Petrescu <alexandru.petrescu@gmail.com>, "<ipv6@ietf.org>" <ipv6@ietf.org>, Tim Chown <tjc@ecs.soton.ac.uk>, "Fred Baker \(fred\)" <fred@cisco.com>, Fernando Gont <fgont@si6networks.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 27 Oct 2013 15:53:36 -0000

On 10/27/2013 02:26 AM, Jeroen Massar wrote:
>> allows privacy,
> 
> IMHO big nonsense. The company (amongst many others!) you work for uses
> amongst others cookies to track their people, and if they really bother
> could even use natural language structure, search query types, and other
> behavior for breaking this 'privacy'. Also note that even if the last
> 64bits are random, your company should be more than able to say "oh,
> there are typically X users in there, it likely is Y"...

Then why deprecate EUI-64?


From alvarezp@alvarezp.ods.org  Sun Oct 27 08:57:09 2013
Return-Path: <alvarezp@alvarezp.ods.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3F3821E80D5 for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 08:57:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zajgfiCeC5CK for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 08:57:01 -0700 (PDT)
Received: from sobre.alvarezp.com (sobre.alvarezp.com [173.230.155.94]) by ietfa.amsl.com (Postfix) with ESMTP id 3CEE111E828F for <ipv6@ietf.org>; Sun, 27 Oct 2013 08:56:57 -0700 (PDT)
Received: from [192.168.2.208] (189.220.45.207.cable.dyn.cableonline.com.mx [189.220.45.207]) by sobre.alvarezp.com (Postfix) with ESMTPSA id 21CD3613D; Sun, 27 Oct 2013 11:56:57 -0400 (EDT)
Message-ID: <526D37DB.3020105@alvarezp.ods.org>
Date: Sun, 27 Oct 2013 08:57:15 -0700
From: Octavio Alvarez <alvarezp@alvarezp.ods.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130821 Icedove/17.0.8
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification for draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <138388CE-99F3-4F14-A17B-2D8CB2D55EFA@steffann.nl> <015A331F-8894-4A43-B3E8-E77DE7312595@tzi.org>
In-Reply-To: <015A331F-8894-4A43-B3E8-E77DE7312595@tzi.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Cc: "ipv6@ietf.org 6man-wg" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 27 Oct 2013 15:57:09 -0000

On 10/26/2013 02:40 AM, Carsten Bormann wrote:
> On 25 Oct 2013, at 19:09, Sander Steffann <sander@steffann.nl> wrote:
> 
>> make the specs a bit more flexible
> 
> Flexibility is overrated.
> 
> If you make it easier for a site to live with a /64 by making it easier to split that into /80 networks, the next thing you’ll notice that sites start to be allocated /80s.

... and proposals to allow up to /64s in the global routing table.



From alvarezp@alvarezp.ods.org  Sun Oct 27 09:03:16 2013
Return-Path: <alvarezp@alvarezp.ods.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FB5221E80D0 for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 09:03:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ndkdhaMkhPSt for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 09:03:15 -0700 (PDT)
Received: from sobre.alvarezp.com (sobre.alvarezp.com [IPv6:2600:3c01::f03c:91ff:fe96:8fec]) by ietfa.amsl.com (Postfix) with ESMTP id 2850A21E80E3 for <ipv6@ietf.org>; Sun, 27 Oct 2013 09:03:14 -0700 (PDT)
Received: from [192.168.2.208] (189.220.45.207.cable.dyn.cableonline.com.mx [189.220.45.207]) by sobre.alvarezp.com (Postfix) with ESMTPSA id E666A613D; Sun, 27 Oct 2013 12:03:13 -0400 (EDT)
Message-ID: <526D3953.40102@alvarezp.ods.org>
Date: Sun, 27 Oct 2013 09:03:31 -0700
From: Octavio Alvarez <alvarezp@alvarezp.ods.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130821 Icedove/17.0.8
MIME-Version: 1.0
To: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Why /64 [was Re: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification for draft-gont-6man-deprecate-eui64-based-addresses-00.txt)]
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Fernando Gont <fgont@si6networks.com>, Alexandru Petrescu <alexandru.petrescu@gmail.com>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 27 Oct 2013 16:03:16 -0000

On 10/25/2013 12:30 PM, Tim Chown wrote:

>> Let's keep this thread on-topic. ;-)
> 
> Well, you're proposing deprecating EUI-64, so there is no longer any reason to be constrained to /64.... so your replacement should consider the possibility of it being used with longer subnet prefixes at some point in the future?

http://etherealmind.com/allocating-64-wasteful-ipv6-not/

It quotes RFC 5375.



From jeroen@massar.ch  Sun Oct 27 09:10:21 2013
Return-Path: <jeroen@massar.ch>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 247F311E8182 for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 09:10:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.143
X-Spam-Level: 
X-Spam-Status: No, score=-2.143 tagged_above=-999 required=5 tests=[AWL=-0.458, BAYES_00=-2.599, J_CHICKENPOX_22=0.6, NO_RELAYS=-0.001, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1VnaJ-cczFMb for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 09:10:13 -0700 (PDT)
Received: from icaras.de.unfix.org (icaras.de.unfix.org [IPv6:2a01:4f8:130:74c1:5054:ff:fec4:f7d4]) by ietfa.amsl.com (Postfix) with ESMTP id 2CE0D11E8293 for <ipv6@ietf.org>; Sun, 27 Oct 2013 09:10:10 -0700 (PDT)
Received: from kami.ch.unfix.org (kami.ch.unfix.org [IPv6:2001:1620:f42:99:7256:81ff:fea5:2925]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeroen) by icaras.de.unfix.org (Postfix) with ESMTPSA id 56F7E801C2A2; Sun, 27 Oct 2013 17:10:03 +0100 (CET)
Message-ID: <526D3AE2.2020300@massar.ch>
Date: Sun, 27 Oct 2013 17:10:10 +0100
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com> <526CE821.1000900@massar.ch> <CAKD1Yr138KfSo_g5mr-5r4-H8Fxrk0GUnDLy0nLHZr1z6PC_cg@mail.gmail.com>
In-Reply-To: <CAKD1Yr138KfSo_g5mr-5r4-H8Fxrk0GUnDLy0nLHZr1z6PC_cg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 27 Oct 2013 16:10:21 -0000

TLDR: /64 on a link is great, keep it; /48 or /56 standardized per site
is great for renumbering (at least the plan); IPv6 "privacy address" is
not really private anyway, thus bad to list as a reason for keeping /64.


On 2013-10-27 14:36, Lorenzo Colitti wrote:
> On Sun, Oct 27, 2013 at 7:17 PM, Jeroen Massar <jeroen@massar.ch
> <mailto:jeroen@massar.ch>> wrote:
> 
>     Cookies is just one of the many ways as per:
> 
>     http://panopticlick.eff.org/
> 
> 
> Ok, we shouldn't have gotten into this debate. I think that's worthless

The point that I am trying to make, but the one you do not want to hear,
is that "IPv6 privacy" does not exist, hence stating that it is a 'good
thing for having a /64 or /48' is just stating a muyth similar to
stating that "IPv6 is more secure than IPv4 as it has IPSEC" and other
such myths.

Thus, I'll nicely ask to stop making statements like that as they are
not true, and never have been. (though they look like it, and as
everybody keeps echoing them they sound like it, they are not)



If you want proper privacy then use Tor or similar systems.
(and lots of people debate if those keep you truly private...)

I'll give another few comments on your statements below, just to show
how easily they are debunked and thus how false they are.


That all said, /64's are great IMHO.

Though if there is a significant reason why people think the address
space is too small and they need to get rid of the 'barrier', then write
up a proper draft, spell out your reasoning and we can discuss that.

>From my POV there is enough space, there are just ISPs who are cutting
people short in how much they want to give out as they are stuck in
IPv4-think, which is logical in a way when they have dealt with a lot of
problems address squeeze or problems getting more space from a RIR. The
solution to these folks is education, not changes to a proper architecture.

Don't forget that one of the primary reasons for doing /48 at every site
was that it allows "easier" renumbering (at least one can keep the same
address plan ;)

As for networks that want to use shorter-than /64, they can. DHCPv6
allows this scenario. The IETF though should never be recommending any
of that and neither should the RIRs, who should actually IMHO enforce
that LIRs give out proper address space to users and not force users to
a single /128 when the ISP has more than enough space and can easily go
to the RIR to get more when they need it (though if an ISP has to return
for more they made a mistake in their initial allocation if it was only
made a few years ago...).

Greets,
 Jeroen

--

> (every one of tens of millions of iPhones will return the same result...
> ). But sure. There are other ways to track people than via IP addresses.

Just tested with my iPad2, which is just another IOS device:

"Your browser fingerprint appears to be unique amongst the 3.535.368
tested so far"

the primary reason apparently:
- User Agent, which included the exact User-Agent string
  not everybody is running IOS 7.0.3 yet = 18.95bits, 1/505052.57
- Browser Plugin Detail = 17.29 bits, 1/160698.55
  Not everybody has Bria and other Apps that allow IOS to accept
  certain media types.

Panopticlick wins again. That is HTTP indeed, but HTTP is what these
devices are being used for, not IP level so much. And if you make one
lousy connection outbound over HTTP that identifies you then that IP
address has compromised you. Unless (but that is hard to see) IOS cycles
the IPv6 address for every app; with very few apps doing IPv6 though
that is hard to test easily.

Also Google/Bing/Yahoo or whatever search engine you are allowed to use
for IDFA for some extra work there to make it possible to track you.
Though they claim you are anonymous, they track an identity which can be
extremely easily linked to a person with help of .

Next to that some apps just for 'fun' insert your mac address or other
identifying information into their requests.

Note that iPhones are predominantly HTTP users and thus have all the
problems and tracking features that come along with it. If you are all
behind a NAT it gets tricker, but nobody cares about IP level tracking,
the applications take care of that; people love logging in to social
networks.

Those 10m iphones also do not live behind the same IP address, or even
/48; though it is likely in a IPv6-environment that there will be a few
thousand in a single /48 indeed, that is, if the operator choses to
deploy them that way. It is often enough seen to deploy behind a
transparent proxy.

Still, statistics allow one to discern between them.

>     You probably mean the ISPs who require ND-proxy to get that /64 on your
>     side of the link? :)
> 
> 
> No, you're misinformed. I mean real DHCPv6 PD. See below.

I've not seen DHCPv6 PD live in action at any of these ISPs; I have seen
lots of people do NDproxy tricks though.

>     Amongst others: http://www.ipsidixit.net/2010/03/24/239/ one of many
>     articles on this for free.fr <http://free.fr> (the "largest IPv6
>     native deployment").
> 
> 
> Since forever Free.fr has been handing out /60 to all its customers

Hence why the above linked article exists and many other similar ones.

> (it's the maximum they can hand out with 6rd using their IPv6 allocation
> size), and sends an RA with a /64 by default. I believe that if you
> configure it they'll send out one different prefix for each port on the
> box. Look for them in your logs; I'm sure you'll still see some ff:fe in
> there, which probably means autoconf.




>     Liberty Global (Unity Media in Germany) is playing with DS-Lite, hence
>     you get 1 IPv6 address and a CGN IPv4 address (which is useless in
>     prime-time as those boxes cannot handle all the BitTorrent and other
>     heavy traffic flows).
> 
> 
> DS-lite is not limited to one IPv6 address. Where did you get that from?

While the protocol and the tools might not be limited to that, this is
how it is being deployed.

IPv6 (this whole thread :) is not limited to a single /128 either, but
this is how it is being deployed in the wide by various ISPs (cheap
hosters are a primary example, but there are also consumer ISPs, eg
Liberty Global mentioned above) who do.

> As for DS-Lite, well, you know, there's not a lot of IPv4 left.

There indeed is not; in this specific example they converted people who
had proper IPv4 connectivity to DSLITE and the former IPv4 addresses are
now used for the hosting offering of the ISP. The pain is thus being
diverted a bit.

> Nope, Comcast doesn't do that - neither in IPv4 nor in IPv6. Some
> European ISPs do. Where did you get your facts from?

I didn't say that Comcast did, note that I pointed out for them the
helpdesk article which describes, apparently stale, details about their
deployment.

> Please check your information before presenting it as facts in this sort
> of policy discussion. We really don't want to come to the wrong
> conclusion because we have the wrong data.

I fully agree, see above about your iphones statement where you provide
no facts but all statements.

Note that I am pointing out documentation that is available. That these
authoritative sources are out of date not much I can do about.

Greets,
 Jeroen


From lorenzo@google.com  Sun Oct 27 11:06:42 2013
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B240311E81B1 for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 11:06:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[AWL=0.080,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JD6SBvShZERy for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 11:06:39 -0700 (PDT)
Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com [IPv6:2607:f8b0:4001:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 16CBC11E80E7 for <ipv6@ietf.org>; Sun, 27 Oct 2013 11:06:37 -0700 (PDT)
Received: by mail-ie0-f169.google.com with SMTP id ar20so10093826iec.28 for <ipv6@ietf.org>; Sun, 27 Oct 2013 11:06:36 -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=Psx1ek1TUuIJdQCkcbh1XlgMAtZtoBvC4WxJWxSq9kw=; b=MGXQX6ja9AOMc98ajYUUyozunMwHnxq44FudUcK0kklbhMiujxfrH5WvlVxoYCWBxs kQxYmgf/Ngh3dIjqTkFO8Mt5mi526us+aP2A9LwloekUP2bCin8zpz+909imsYa9P/C+ CQe1yOm9Kl5Q60kgokdrl30Tt/3oafXHH3M+7+e0VaZYRaDy/JsgPrBa3xb7aJk4ioOr f5qNss2KZXzaAUVwG1FM8HI58W4n9RUcmBVD5bGTruwHwhi45/JwtgFA+EDKDVoxXyDg FFntSRG5OT7wVbQULS7FTKuP3l2L1RpYeOO60t7Wshhe1v8ZRHWr07d17rjAqImaJJKO Z7GQ==
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=Psx1ek1TUuIJdQCkcbh1XlgMAtZtoBvC4WxJWxSq9kw=; b=M3xaIbFV/uvHP4poHQ07kmTZl8W8MIIfHgcOjgT87pPvZmB+203TYdFk/4GAlzxD32 /V8ACdlMOj3PWdZ6pAPb3tavjlkL6DtEgzgoG94e3fVwZBn5i+1fq+RbkWzwdW7Zb/tN L3lGru8Fae3/jDyg0IMz2DMuqLzfGi8+oHvXDKtGZqC+53Yf6x6yTwUGCjv9AiiMYFYq Cc6kFIGOhjs7Av2bIbOy7zfdviTU9cq5E8+/ns2dlVVDF2Wk8Reu+Hr3FQVx+9YF3Ld5 gSK1mWB9B2OgF/b8MHDJJ1fe189xh57yG9FXx6CWYmdFhOA5Qa73B6SCc9ueWteMTYQT S/kw==
X-Gm-Message-State: ALoCoQmd20Tz2oXllgcaCidHUGweqFj+tYe9PqsnQJ5B4jBxamFurdRvAcpi2RNoGGh5SwMjfNRX8I2ZpCJzQN0LeH7wgsCVbl5n99OguUPkSNo1hLkdE5eFVqsIgVI9sJ4lNSjQGjH83ahLTIGO1/ab2voiBj2x9LA8qowZvS68yn/uR/4nNTrj+A0LrdmuRABD2EzYqoQN
X-Received: by 10.50.22.101 with SMTP id c5mr5893523igf.17.1382897196428; Sun, 27 Oct 2013 11:06:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.86.106 with HTTP; Sun, 27 Oct 2013 11:06:16 -0700 (PDT)
In-Reply-To: <526D3AE2.2020300@massar.ch>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com> <526CE821.1000900@massar.ch> <CAKD1Yr138KfSo_g5mr-5r4-H8Fxrk0GUnDLy0nLHZr1z6PC_cg@mail.gmail.com> <526D3AE2.2020300@massar.ch>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 28 Oct 2013 03:06:16 +0900
Message-ID: <CAKD1Yr1DnHrkXmYhGc-mSg4W94=-=DLizm0iR18hPCa=yw3Pdw@mail.gmail.com>
Subject: Re: Why /64
To: Jeroen Massar <jeroen@massar.ch>
Content-Type: multipart/alternative; boundary=047d7b10c9cb27a5df04e9bcd857
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 27 Oct 2013 18:06:42 -0000

--047d7b10c9cb27a5df04e9bcd857
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Oct 28, 2013 at 1:10 AM, Jeroen Massar <jeroen@massar.ch> wrote:

> The point that I am trying to make, but the one you do not want to hear,
> is that "IPv6 privacy" does not exist


Perhaps, but let's not argue that on this thread, which is about subnet
sizes.


> >     Amongst others: http://www.ipsidixit.net/2010/03/24/239/ one of many
> >     articles on this for free.fr <http://free.fr> (the "largest IPv6
> >     native deployment").
> >
> >
> > Since forever Free.fr has been handing out /60 to all its customers
>
> Hence why the above linked article exists and many other similar ones.
>

The article exists because the writer wanted to put a firewall between the
ISP router and the other machines. You can do that with DHCPv6 PD but not
with native routing (just like you can't do that in IPv4 without NAT). It
doesn't support the assertion that free.fr assigns single IPv6 addresses to
their users.

For free.fr docs on this:

http://ripe58.ripe.net/content/presentations/ipv6-free.pdf (addressing
plan, mentions /60 per user)
http://aide.ma-freebox.fr/ipv6.html (look at the screenshots, they even
allow you to statically route some of your /64s to nexthops you specify)


> IPv6 (this whole thread :) is not limited to a single /128 either, but
> this is how it is being deployed in the wide by various ISPs (cheap
> hosters are a primary example, but there are also consumer ISPs, eg
> Liberty Global mentioned above) who do.
>

Where did you get the information that unitymedia only provide a single
/128? http://www.unitymediakabelbwforum.de/viewtopic.php?f=53&t=23981 and
http://www.youtube.com/watch?v=K0hT1PpfxxQ suggests the CPE gets a /57.


> Note that I am pointing out documentation that is available. That these
> authoritative sources are out of date not much I can do about.
>

Of course you can't do anything about out-of-date documentation, but please
do a little more research before making confident statements based on said
out-of-date documentation. People might believe you, and they'd be wrong.

Specifically, I think the "quite a few [ISPs] give exactly 1 IPv6 address
to their users" statement is not true in the case of mainstream residential
ISPs - I think they all provide at least a /64, and more usually at least a
/60.

--047d7b10c9cb27a5df04e9bcd857
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Mon, Oct 28, 2013 at 1:10 AM, 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><div class=3D"gmail_extra"><div class=3D"=
gmail_quote">

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">The point that I am trying to make, but the one you do not=
 want to hear,<br>


is that &quot;IPv6 privacy&quot; does not exist</blockquote><div><br></div>=
<div>Perhaps, but let&#39;s not argue that on this thread, which is about s=
ubnet sizes.</div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,20=
4,204);border-left-style:solid;padding-left:1ex">


<div class=3D"im">&gt; =A0 =A0 Amongst others: <a href=3D"http://www.ipsidi=
xit.net/2010/03/24/239/" target=3D"_blank">http://www.ipsidixit.net/2010/03=
/24/239/</a> one of many<br>
</div>&gt; =A0 =A0 articles on this for <a href=3D"http://free.fr" target=
=3D"_blank">free.fr</a> &lt;<a href=3D"http://free.fr" target=3D"_blank">ht=
tp://free.fr</a>&gt; (the &quot;largest IPv6<br>
<div class=3D"im">&gt; =A0 =A0 native deployment&quot;).<br>
&gt;<br>
&gt;<br>
&gt; Since forever Free.fr has been handing out /60 to all its customers<br=
>
<br>
</div>Hence why the above linked article exists and many other similar ones=
.<br></blockquote><div><br></div><div>The article exists because the writer=
 wanted to put a firewall between the ISP router and the other machines. Yo=
u can do that with DHCPv6 PD but not with native routing (just like you can=
&#39;t do that in IPv4 without NAT). It doesn&#39;t support the assertion t=
hat <a href=3D"http://free.fr">free.fr</a> assigns single IPv6 addresses to=
 their users.</div>

<div><br></div><div>For <a href=3D"http://free.fr">free.fr</a> docs on this=
:</div><div><br></div><div><a href=3D"http://ripe58.ripe.net/content/presen=
tations/ipv6-free.pdf">http://ripe58.ripe.net/content/presentations/ipv6-fr=
ee.pdf</a> (addressing plan, mentions /60 per user)<br>

</div><div><a href=3D"http://aide.ma-freebox.fr/ipv6.html">http://aide.ma-f=
reebox.fr/ipv6.html</a> (look at the screenshots, they even allow you to st=
atically route some of your /64s to nexthops you specify)<br></div><div>
=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
<div class=3D"im"><span style=3D"color:rgb(34,34,34)">IPv6 (this whole thre=
ad :) is not limited to a single /128 either, but</span><br></div>
this is how it is being deployed in the wide by various ISPs (cheap<br>
hosters are a primary example, but there are also consumer ISPs, eg<br>
Liberty Global mentioned above) who do.<br></blockquote><div><br></div><div=
>Where did you get the information that unitymedia only provide a single /1=
28?=A0<a href=3D"http://www.unitymediakabelbwforum.de/viewtopic.php?f=3D53&=
amp;t=3D23981">http://www.unitymediakabelbwforum.de/viewtopic.php?f=3D53&am=
p;t=3D23981</a> and <a href=3D"http://www.youtube.com/watch?v=3DK0hT1PpfxxQ=
">http://www.youtube.com/watch?v=3DK0hT1PpfxxQ</a> suggests the CPE gets a =
/57.</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left=
-style:solid;padding-left:1ex">
<div class=3D"im"><span style=3D"color:rgb(34,34,34)">Note that I am pointi=
ng out documentation that is available. That these</span><br></div>
authoritative sources are out of date not much I can do about.<br></blockqu=
ote><div><br></div><div>Of course you can&#39;t do anything about out-of-da=
te documentation, but please do a little more research before making confid=
ent statements based on said out-of-date documentation. People might believ=
e you, and they&#39;d be wrong.</div>

<div><br></div><div>Specifically, I think the &quot;quite a few [ISPs] give=
 exactly 1 IPv6 address to their users&quot; statement is not true in the c=
ase of mainstream residential ISPs - I think they all provide at least a /6=
4, and more usually at least a /60.</div>

</div></div></div>

--047d7b10c9cb27a5df04e9bcd857--

From trejrco@gmail.com  Sun Oct 27 12:04:31 2013
Return-Path: <trejrco@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D72011E81BE for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 12:04:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YxxEFSeev0ky for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 12:04:29 -0700 (PDT)
Received: from mail-ve0-x233.google.com (mail-ve0-x233.google.com [IPv6:2607:f8b0:400c:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 294F111E81B1 for <ipv6@ietf.org>; Sun, 27 Oct 2013 12:04:26 -0700 (PDT)
Received: by mail-ve0-f179.google.com with SMTP id cz12so4315310veb.24 for <ipv6@ietf.org>; Sun, 27 Oct 2013 12:04:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=R0VgW1IEU/ib8vqLiNGirZ8LBtbcP4axTMarCysPPIQ=; b=fA73B18ndBNdqBK0NOGOatJdevl4lnJQFMrw0oNkEVrSLIvzsqu2DejeGUrr3EB6KV AQ/Xm+fMD4hJSljm6FKb39WGMw714fr8p+G9FHnjyrgUlM4CrKWaDH5pQxPZpFKUPsQs 8tk91CwtR85jyqRBFOMbHC9Dlvn8nmME1AT2LpjcHg9HoDIvSHtTHuay4FislNQcPWtX qaWNErdpR4Qd90vMQog6dw1zsw8RQw6F68SXNz+HuctSufeZivxL9Qegwtmsz4fg66mR iRqexhIkkR+Fn3U8JWJ7cvOCAMCidBttfrlGqv95QH3yOknvwzMurEg53PS5J8YC5fve UmcA==
X-Received: by 10.52.164.102 with SMTP id yp6mr9326376vdb.14.1382900665017; Sun, 27 Oct 2013 12:04:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.173.6 with HTTP; Sun, 27 Oct 2013 12:04:04 -0700 (PDT)
In-Reply-To: <526D0F47.5040803@massar.ch>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com> <CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com> <526D0F47.5040803@massar.ch>
From: TJ <trejrco@gmail.com>
Date: Sun, 27 Oct 2013 15:04:04 -0400
Message-ID: <CALOgxGaoB_u+br5bpyVu-A0w8vD=QjYkrzaPqYrrhtPK=z6BEw@mail.gmail.com>
Subject: Re: Why /64
To: "<ipv6@ietf.org>" <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c2c1eae5efe304e9bda6b0
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: trejrco@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: Sun, 27 Oct 2013 19:04:31 -0000

--001a11c2c1eae5efe304e9bda6b0
Content-Type: text/plain; charset=ISO-8859-1

>
> >>> IMHO big nonsense. The company (amongst many others!) you work for
> > uses amongst others cookies to track their people,
> >>
> >> Not sure we want to get into that argument here, but
> >
> > I _don't_ want to get into it here but I want to briefly support Lorenzo
> > on privacy.  Privacy through controlling tracking of an IP address is
> > very different in mechanism and result from higher layer end-to-end
> > privacy.
>

First off, ++1 to Lorenzo on all counts (and Scott, Karl).



> It does not matter if you have 1 IPv4 address with 2000 people behind
> it, or 1 /48 with 2000 people behind it.
>
> The algorithms to de-anonimize and differentiate between the real hosts
> behind them exist.
>
> Cookies are one way to do that, complete browser profiles or other
> differences in the client, be that the tcp stack level another. For
> other protocols it is all much easier as they are typically already
> authenticated anyway or have other bits.
>
>

Having said that, FWIW - I partially disagree with Jeron here - it does
matter.  A user can have browser extensions, multiple browsers (or mutliple
VMs with different OSes) and have a fairly good level of privacy if so
desires - as long as the underlying L3 provisioned does not prevent it.  Is
may not be exactly mainstream / commonplace, but not uncommon enough to
ignore (IMHO) either.


/TJ

--001a11c2c1eae5efe304e9bda6b0
Content-Type: text/html; charset=ISO-8859-1
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:0px 0px 0px 0.8ex;border-left=
-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;paddi=
ng-left:1ex">

<div class=3D"im">&gt;&gt;&gt; IMHO big nonsense. The company (amongst many=
 others!) you work for<br>
&gt; uses amongst others cookies to track their people,<br>
&gt;&gt;<br>
&gt;&gt; Not sure we want to get into that argument here, but<br>
&gt;<br>
&gt; I _don&#39;t_ want to get into it here but I want to briefly support L=
orenzo<br>
&gt; on privacy. =A0Privacy through controlling tracking of an IP address i=
s<br>
&gt; very different in mechanism and result from higher layer end-to-end<br=
>
&gt; privacy.<br></div></blockquote><div><br></div><div>First off, ++1 to L=
orenzo on all counts (and Scott, Karl).</div><div><br></div><div>=A0</div><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;pa=
dding-left:1ex">

<div class=3D"im"><span style=3D"color:rgb(34,34,34)">It does not matter if=
 you have 1 IPv4 address with 2000 people behind</span><br></div>
it, or 1 /48 with 2000 people behind it.<br>
<br>
The algorithms to de-anonimize and differentiate between the real hosts<br>
behind them exist.<br>
<br>
Cookies are one way to do that, complete browser profiles or other<br>
differences in the client, be that the tcp stack level another. For<br>
other protocols it is all much easier as they are typically already<br>
authenticated anyway or have other bits.<br>
<br></blockquote><div><br></div><div><br></div><div>Having said that, FWIW =
- I partially disagree with Jeron here - it does matter. =A0A user can have=
 browser extensions, multiple browsers (or mutliple VMs with different OSes=
) and have a fairly good level of privacy if so desires - as long as the un=
derlying L3 provisioned does not prevent it. =A0Is may not be exactly mains=
tream / commonplace, but not uncommon enough to ignore (IMHO) either.</div>

<div><br></div><div><br></div><div>/TJ</div></div></div></div>

--001a11c2c1eae5efe304e9bda6b0--

From brian.e.carpenter@gmail.com  Sun Oct 27 12:22:36 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DD1311E829E for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 12:22:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.526
X-Spam-Level: 
X-Spam-Status: No, score=-102.526 tagged_above=-999 required=5 tests=[AWL=0.073, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c8RNA5dtW+uc for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 12:22:35 -0700 (PDT)
Received: from mail-pd0-x22e.google.com (mail-pd0-x22e.google.com [IPv6:2607:f8b0:400e:c02::22e]) by ietfa.amsl.com (Postfix) with ESMTP id CE39C11E80E9 for <ipv6@ietf.org>; Sun, 27 Oct 2013 12:22:35 -0700 (PDT)
Received: by mail-pd0-f174.google.com with SMTP id z10so1460878pdj.33 for <ipv6@ietf.org>; Sun, 27 Oct 2013 12:22:35 -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=kPfai1v0GcunDdCRPeKPPc2toMOOyZaPgC7oQpvEN4U=; b=Pp5exfg4TYoqjNzIK0H5speI0mfxxdqXVSzECpmT7AYMBE/3dg31u6KJBOdi0UF0rS 6PbhXb9fbd3u/wne9Dp/bfmGbi3c9eorOCFIFHjNWkCpznWHWzVj+/OlcrUw/UQRa9CB UW+VOJfoqqgt31fDC8XnQgP74w2Ou3HqDZzDbgdZF9mtv3CtpGSF8xObCCMejKtpo3vm qk6MPdAgut8lEKEqnmzxK01RCyvDmNmc5tNeUhAccbSQILGYl+uzy7VMyjcHpA4eYJUL Kull0Bwa1hzjFQwkkbgrqiK1MqutHYNOs8Q2b/5MUMA6tIi1bCPQdqNMD1v2AKdSzUUx ZRkA==
X-Received: by 10.68.212.37 with SMTP id nh5mr17845279pbc.16.1382901755623; Sun, 27 Oct 2013 12:22:35 -0700 (PDT)
Received: from [192.168.178.20] (161.201.69.111.dynamic.snap.net.nz. [111.69.201.161]) by mx.google.com with ESMTPSA id y9sm29472281pas.10.2013.10.27.12.22.33 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 27 Oct 2013 12:22:34 -0700 (PDT)
Message-ID: <526D67F3.6020109@gmail.com>
Date: Mon, 28 Oct 2013 08:22:27 +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-gont-6man-deprecate-eui64-based-addresses-00.txt
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com> <52697C33.7010904@gmail.com> <5269B633.8010802@si6networks.com> <5269D03A.8030809@gmail.com> <28EF616C-5765-4D3D-9593-86DE8BB538C5@ecs.soton.ac.uk> <EMEW3|6c915c4e4e63530092c3f6edabbf8a7ep9OL7r03tjc|ecs.soton.ac.uk|28EF616C-5765-4D3D-9593-86DE8BB538C5@ecs.soton.ac.uk> <526B12E2.5050503@gmail.com> <526B169A.7020208@si6networks.com> <526B203A.6040008@gmail.com> <526D1902.7000401@si6networks.com>
In-Reply-To: <526D1902.7000401@si6networks.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 27 Oct 2013 19:22:36 -0000

On 28/10/2013 02:45, Fernando Gont wrote:
> On 10/25/2013 10:51 PM, Brian E Carpenter wrote:
>>> You only need such loggig feature if the IPv6/MAC mapping changes. This
>>> I-D is simply about stable addresses... so such discussion is orthogonal.
>>>
>>> Am I missing something?
>> It's about operations people (and products) that currently rely on EUI-64.
>> I don't think anyone's arguing that we can't move away from EUI-64 over time.
> 
> 1) What's the basis for that reliance? (i.e., what for?)

Identifying hosts (well, NICs) without needing the ND cache.

> 
> 2) What's the usefulness of that, if, e.g. Windows doesn't employ
> Modified EUI-64?

None. I'm rather shocked that MS decided to unilaterally dump the
requirement in RFC 4291. (I assume that there's a a 'netsh int ipv6'
command to reinstate EUI-64; if not, it's even more shocking.)

As it happens, draft-ietf-6man-ug-04 removes that requirement, and
that's the right thing to do. But if a site wants to operate
that way, it isn't the IETF's business (or Microsoft's) to stop
them.

   Brian


From markzzzsmith@yahoo.com.au  Sun Oct 27 13:43:51 2013
Return-Path: <markzzzsmith@yahoo.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E17C911E82B0 for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 13:43:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.855
X-Spam-Level: 
X-Spam-Status: No, score=-1.855 tagged_above=-999 required=5 tests=[AWL=0.244,  BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KLzxRW7JNGRA for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 13:43:47 -0700 (PDT)
Received: from nm23-vm1.bullet.mail.bf1.yahoo.com (nm23-vm1.bullet.mail.bf1.yahoo.com [98.139.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 2C88E11E8178 for <ipv6@ietf.org>; Sun, 27 Oct 2013 13:43:47 -0700 (PDT)
Received: from [98.139.214.32] by nm23.bullet.mail.bf1.yahoo.com with NNFMP; 27 Oct 2013 20:43:46 -0000
Received: from [98.139.212.239] by tm15.bullet.mail.bf1.yahoo.com with NNFMP; 27 Oct 2013 20:43:46 -0000
Received: from [127.0.0.1] by omp1048.mail.bf1.yahoo.com with NNFMP; 27 Oct 2013 20:43:46 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 616915.95921.bm@omp1048.mail.bf1.yahoo.com
Received: (qmail 79051 invoked by uid 60001); 27 Oct 2013 20:43:46 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s1024; t=1382906626; bh=F5NykLRECg9hvxgsKIOGjn97mIky4fofv2LupzPJVwA=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=uXS/7Y/GCUQP8DhpyefQHnahm43Iqp1r4KjvmBdxmoQV+3m0GoiIFEEZvYzIId5As9IBS+Zy/dp1U+ZgKhXOF0kPHhng+7ve1YbkzR/obfLJXhlIxArjpYm10543Z1rJCo2navgzV+gn+rQSe5W+KLKUa646Qvvlf5vbFoOSv80=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.au; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=1+Hyu/Q0/M98LGIUBes0MzR2b6z03Hsf7mry5mphzO5KgA2O06FyEu/2YQBg/TYinTRuFi02nm287MFO/46atoY+nQWEmzvJksvQhw0LZXs20tF99rp6FClU9BtzKETZpxlhObIjbphTFyn4GcTPOaYnCrrY6jzQfta56vyYKfA=;
X-YMail-OSG: 7KO7YTsVM1nkdyMhz7i0R0ntYK1.IG4WNDULUjws_e5MNM4 vaLi1BO07KmcIcCX8UjtLr3IiW0Ml7bwL1yNmjxGO1bU5AX4cVU6cnsopwhO r9ze.JIapcRqyXnRAPOyZ0FHfAY9PSoUY18bIXHO.I7qvhW1l4FSjscq.SVb EgupXUNmOy958Rl_MkV6jvuphrB6y.oDi4B8OThcafJHXvtJ7OfQNKor8Ddk 9pcwj68ZyTH63aE3IIRaXFYy0_lR391vSBrDDW5hbYM7MJF87hwdyhyHV.F0 iIxrIYh489SZcmvMirHXTRSsNnxSfdauz5yx2z86UmUUpMCK0oDnyZf24Pwo sWs2s5M_K0ZaWUdYLSOB.kPsoaDJG7pEJM1vwskTNGEkdCX5hu_SNRL0lmD4 nZH0kqirvqlwu9NN5DDtr5bYmQiCB9kQG4OlPHMt.8_R9D0piVcNC27djhlq uLfbsEUrFlnxS5V721z2Yc2kSi13vkJZQJ298nCGu6W5AwB1DrAfdy3vB8z2 IufL4KTLyJj93QpsrJV_5AI_Ml4Fv8kK591ytrBC11Nh5FC0kHhJGqh9B9Ji rnZ.wiNSDYgnaJWNdwE.GsypAghvdsHHFXLxbelMChvsF4pkBpRmaT67r9Yj 4TAUEbpmasQEuTDFghjUuSrCMmNkX82pTPbC9YCETR49dE49aWvzLrn_Lztm AZUhSTz4-
Received: from [150.101.221.237] by web142501.mail.bf1.yahoo.com via HTTP; Sun, 27 Oct 2013 13:43:45 PDT
X-Rocket-MIMEInfo: 002.001, CgoKCjxzbmlwPgo.Cj5TcGVjaWZpY2FsbHksIEkgdGhpbmsgdGhlICJxdWl0ZSBhIGZldyBbSVNQc10gZ2l2ZSBleGFjdGx5IDEgSVB2NiBhZGRyZXNzIHRvIHRoZWlyIHVzZXJzIiBzdGF0ZW1lbnQgaXMgbm90IHRydWUgaW4gdGhlIGNhc2Ugb2YgbWFpbnN0cmVhbSByZXNpZGVudGlhbCBJU1BzIC0gSSB0aGluayB0aGV5IGFsbCBwcm92aWRlIGF0IGxlYXN0IGEgLzY0LCBhbmQgbW9yZSB1c3VhbGx5IGF0IGxlYXN0IGEgLzYwLgo.CgpEdXJpbmcgdGhlaXIgSVB2NiB0cmlhbCwgSW50ZXJub2RlIGdhdmUgb3UBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.160.587
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com>	<526AACA5.7090604@si6networks.com>	<E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<526AC8AF.4060608@si6networks.com>	<8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com>	<CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com>	<526CDC59.4070204@massar.ch>	<CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com>	<526CE821.1000900@massar.ch>	<CAKD1Yr138KfSo_g5mr-5r4-H8Fxrk0GUnDLy0nLHZr1z6PC_cg@mail.gmail.com>	<526D3AE2.2020300@massar.ch> <CAKD1Yr1DnHrkXmYhGc-mSg4W94=-=DLizm0iR18hPCa=yw3Pdw@mail.gmail.com>
Message-ID: <1382906625.63973.YahooMailNeo@web142501.mail.bf1.yahoo.com>
Date: Sun, 27 Oct 2013 13:43:45 -0700 (PDT)
From: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
Subject: Re: Why /64
To: Lorenzo Colitti <lorenzo@google.com>, Jeroen Massar <jeroen@massar.ch>
In-Reply-To: <CAKD1Yr1DnHrkXmYhGc-mSg4W94=-=DLizm0iR18hPCa=yw3Pdw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 27 Oct 2013 20:43:52 -0000

=0A=0A=0A=0A<snip>=0A>=0A>Specifically, I think the "quite a few [ISPs] giv=
e exactly 1 IPv6 address to their users" statement is not true in the case =
of mainstream residential ISPs - I think they all provide at least a /64, a=
nd more usually at least a /60.=0A>=0A=0ADuring their IPv6 trial, Internode=
 gave out /60s. When they deployed production residential broadband IPv6 in=
 2011 (which I worked on), the provided a dynamic /64 to the CPE via SLAAC =
(which allows direct connection of a PC as an alternative to using a CPE), =
and a static /56 via DHCPv6-PD. They fairly recently said they now have 10%=
 of their customers using IPv6, as they've been enabling it by default on a=
ll new customer connections and providing IPv6 enabled CPE with it. Going b=
y the published customer numbers, 10% is in the order of 16 000 to 18 000 s=
ervices with native IPv6 connectivity.=0A=0Ahttp://www.internode.on.net/new=
s/2013/06/309.php=0A=0A=0A=0A>---------------------------------------------=
-----------------------=0A>IETF IPv6 working group mailing list=0A>ipv6@iet=
f.org=0A>Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv=
6=0A>--------------------------------------------------------------------=
=0A>=0A>=0A>

From fred@cisco.com  Sun Oct 27 14:21:03 2013
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A93CD11E8156 for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 14:21:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.384
X-Spam-Level: 
X-Spam-Status: No, score=-110.384 tagged_above=-999 required=5 tests=[AWL=0.215, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NaZQaZN6sSqW for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 14:20:58 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 4D10C11E810C for <6man@ietf.org>; Sun, 27 Oct 2013 14:20:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1718; q=dns/txt; s=iport; t=1382908858; x=1384118458; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=W7jCgHalqDzDlkgPr8rbHpqWcSjAXKKt0sj94vSbjrs=; b=YlOBsrZsUb3pwNVRiH3U2yTo9exTnytbGqeL685frkiWvw8UrcFeSM1d uEc6eutFCWFkTwIFDaTyJRCcq4hBPU4Xf3wD2LuYeDu3uvOmIjoA0LF5i F7pSChEhNEI4yeslJGGDxunGUKw2Yzpr+yE0bKUo34qp4UjtNp/UV5MZ6 0=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAIGDbVKtJV2a/2dsb2JhbABZgwc4VL5egRwWdIIlAQEBAwF3AgULAgEIGAoZCzIlAgQOBQgGh3MGuAyOHIEIMQeDH4ENA5AtgTCHXJBYgWiBPoFxOQ
X-IronPort-AV: E=Sophos;i="4.93,581,1378857600";  d="asc'?scan'208";a="277353097"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-4.cisco.com with ESMTP; 27 Oct 2013 21:20:58 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r9RLKvt7019522 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 27 Oct 2013 21:20:57 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.23]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.02.0318.004; Sun, 27 Oct 2013 16:20:57 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Fernando Gont <fernando@gont.com.ar>
Subject: Re: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification for draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
Thread-Topic: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification for draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
Thread-Index: AQHO0yKkkOnsvbpp00GRW3tGlxVjfJoJYmSA
Date: Sun, 27 Oct 2013 21:20:56 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553BA7DCB5@xmb-rcd-x09.cisco.com>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <8C48B86A895913448548E6D15DA7553BA7A268@xmb-rcd-x09.cisco.com> <526A204D.8080209@gont.com.ar> <8C48B86A895913448548E6D15DA7553BA7BABF@xmb-rcd-x09.cisco.com> <CAPv4CP9SajtHt+JLfdFRo-mV20fSyjtNOtT-+hs5jd9BuQC09A@mail.gmail.com> <8C48B86A895913448548E6D15DA7553BA7BC27@xmb-rcd-x09.cisco.com> <526D1E53.5090608@gont.com.ar>
In-Reply-To: <526D1E53.5090608@gont.com.ar>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.61.200.22]
Content-Type: multipart/signed; boundary="Apple-Mail=_DC90F6C6-840F-43CC-ADBA-4F1A0FA5297B"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "6man@ietf.org" <6man@ietf.org>, "<draft-gont-6man-deprecate-eui64-based-addresses@tools.ietf.org>" <draft-gont-6man-deprecate-eui64-based-addresses@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 27 Oct 2013 21:21:03 -0000

--Apple-Mail=_DC90F6C6-840F-43CC-ADBA-4F1A0FA5297B
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=iso-8859-1


On Oct 27, 2013, at 3:08 PM, Fernando Gont <fernando@gont.com.ar>
 wrote:

> Signed PGP part
> Hi, Fred,
> 
> On 10/26/2013 10:07 AM, Fred Baker (fred) wrote:
> >
> >> It seems reasonable to me to document a recommendation, for the
> >> future, even if it will take 15 years for the not-best-practice
> >> to fade.  Therefore it seems reasonable to me to put in a
> >> SHOULD, along with all of the reasons discussed here why the
> >> installed base doesn't have to at this time.
> >
> > Which is the argument for saying "should 4861 or
> > stable-privacy-addresses".
> 
> Not sure I follow: stable-privacy-addresses is expected to be used
> along RFC4862..

Sorry, yes. Off-by-one error.

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

------------------------------------------------------
8 issues in virtual infrastructure
http://dcrocker.net/#fallacies


--Apple-Mail=_DC90F6C6-840F-43CC-ADBA-4F1A0FA5297B
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 - http://gpgtools.org

iD8DBQFSbYO3bjEdbHIsm0MRAmLwAKDJxVhOPVTz5Pq0Xj9J3FchMVm7bgCgjbhD
Qm+/qrcnuNjqPThF+zT+1bg=
=qAXj
-----END PGP SIGNATURE-----

--Apple-Mail=_DC90F6C6-840F-43CC-ADBA-4F1A0FA5297B--

From Carl.Wuyts@technicolor.com  Sun Oct 27 23:54:30 2013
Return-Path: <Carl.Wuyts@technicolor.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1496D11E8119 for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 23:54:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zg7QqbrqtY0M for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 23:54:25 -0700 (PDT)
Received: from na3sys009aog136.obsmtp.com (na3sys009aog136.obsmtp.com [74.125.149.85]) by ietfa.amsl.com (Postfix) with ESMTP id 9FE1A21F9F62 for <ipv6@ietf.org>; Sun, 27 Oct 2013 23:54:22 -0700 (PDT)
Received: from MOPESEDGE01.eu.thmulti.com ([129.35.174.203]) (using TLSv1) by na3sys009aob136.postini.com ([74.125.148.12]) with SMTP ID DSNKUm4KGSAX4R7qFpA4PN4LVD7lCLu07X99@postini.com; Sun, 27 Oct 2013 23:54:24 PDT
Received: from MOPESMAILHC03.eu.thmulti.com (141.11.100.132) by mail3.technicolor.com (141.11.253.22) with Microsoft SMTP Server (TLS) id 8.3.298.1; Mon, 28 Oct 2013 07:53:47 +0100
Received: from MOPESMBX01.eu.thmulti.com ([169.254.1.71]) by MOPESMAILHC03.eu.thmulti.com ([141.11.100.132]) with mapi; Mon, 28 Oct 2013 07:53:48 +0100
From: Wuyts Carl <Carl.Wuyts@technicolor.com>
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>, Lorenzo Colitti <lorenzo@google.com>, Jeroen Massar <jeroen@massar.ch>
Date: Mon, 28 Oct 2013 07:53:47 +0100
Subject: RE: Why /64
Thread-Topic: Why /64
Thread-Index: Ac7TVUR5DcG2PEmATt+9ENyW2Rfp9gAVDn0w
Message-ID: <3135C2851EB6764BACEF35D8B495596806FAC25C59@MOPESMBX01.eu.thmulti.com>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar>	<526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com> <526CE821.1000900@massar.ch> <CAKD1Yr138KfSo_g5mr-5r4-H8Fxrk0GUnDLy0nLHZr1z6PC_cg@mail.gmail.com> <526D3AE2.2020300@massar.ch> <CAKD1Yr1DnHrkXmYhGc-mSg4W94=-=DLizm0iR18hPCa=yw3Pdw@mail.gmail.com> <1382906625.63973.YahooMailNeo@web142501.mail.bf1.yahoo.com>
In-Reply-To: <1382906625.63973.YahooMailNeo@web142501.mail.bf1.yahoo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 06:54:30 -0000

FWIW.
I'm working for the #1CPE vendor, managed CPEs that is, and I can confirm t=
hat majority of our customers ( ISP's/Telco's) is handing out a /60 or /56.=
  It's very rare, although they exist, to only see /64s handed out to the (=
residential) CPE.
Some do add ia_na to it to number the WAN interface, it's an exception to s=
ee slaac on wan to number wan intf these days @ our customers, although it =
is being used.

WRT privacy etc
Some of our customers re-apply the IPv4 approach on handing out IPv6 pds, i=
.e. with IPv4, they renewed the public IPv4 address every XX hours and re-a=
pply this to ia_pd.  Whether or not this is/was for economics rather than p=
rivacy purposes (more charged for static IPv4 @ some customers, but these b=
eing more business than residential customers) is another question of cours=
e.

Regs
Carl

-----Original Message-----
From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of Mar=
k ZZZ Smith
Sent: zondag 27 oktober 2013 21:44
To: Lorenzo Colitti; Jeroen Massar
Cc: <ipv6@ietf.org>
Subject: Re: Why /64





<snip>
>
>Specifically, I think the "quite a few [ISPs] give exactly 1 IPv6 address =
to their users" statement is not true in the case of mainstream residential=
 ISPs - I think they all provide at least a /64, and more usually at least =
a /60.
>

During their IPv6 trial, Internode gave out /60s. When they deployed produc=
tion residential broadband IPv6 in 2011 (which I worked on), the provided a=
 dynamic /64 to the CPE via SLAAC (which allows direct connection of a PC a=
s an alternative to using a CPE), and a static /56 via DHCPv6-PD. They fair=
ly recently said they now have 10% of their customers using IPv6, as they'v=
e been enabling it by default on all new customer connections and providing=
 IPv6 enabled CPE with it. Going by the published customer numbers, 10% is =
in the order of 16 000 to 18 000 services with native IPv6 connectivity.

http://www.internode.on.net/news/2013/06/309.php



>--------------------------------------------------------------------
>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 jeroen@massar.ch  Mon Oct 28 01:25:33 2013
Return-Path: <jeroen@massar.ch>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75E1111E822F for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 01:25:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.485
X-Spam-Level: 
X-Spam-Status: No, score=-4.485 tagged_above=-999 required=5 tests=[AWL=2.114,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G7lM6djSTKwQ for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 01:25:05 -0700 (PDT)
Received: from icaras.de.unfix.org (icaras.de.unfix.org [78.47.209.234]) by ietfa.amsl.com (Postfix) with ESMTP id 62D7911E821E for <ipv6@ietf.org>; Mon, 28 Oct 2013 01:25:02 -0700 (PDT)
Received: from kami.ch.unfix.org (kami.ch.unfix.org [IPv6:2001:1620:f42:99:7256:81ff:fea5:2925]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeroen) by icaras.de.unfix.org (Postfix) with ESMTPSA id 0D528801C2A2; Mon, 28 Oct 2013 09:24:54 +0100 (CET)
Message-ID: <526E1F5A.2070901@massar.ch>
Date: Mon, 28 Oct 2013 09:24:58 +0100
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar
MIME-Version: 1.0
To: Octavio Alvarez <alvarezp@alvarezp.ods.org>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com>	<526AACA5.7090604@si6networks.com>	<E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<526AC8AF.4060608@si6networks.com>	<8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org>
In-Reply-To: <526D3706.5070409@alvarezp.ods.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 08:25:33 -0000

On 2013-10-27 16:53, Octavio Alvarez wrote:
> On 10/27/2013 02:26 AM, Jeroen Massar wrote:
>>> allows privacy,
>>
>> IMHO big nonsense. The company (amongst many others!) you work for uses
>> amongst others cookies to track their people, and if they really bother
>> could even use natural language structure, search query types, and other
>> behavior for breaking this 'privacy'. Also note that even if the last
>> 64bits are random, your company should be more than able to say "oh,
>> there are typically X users in there, it likely is Y"...
> 
> Then why deprecate EUI-64?

I did not state anything like that. I have only raised concern about
stating that "IPv6 privacy addresses" are a real thing.

I am pro /64 per link and a /48 for Enterprise and at least /56 for
Home-user sites. (/60 is too tiny and not flexible enough)

Greets,
 Jeroen


From Carl.Wuyts@technicolor.com  Mon Oct 28 01:30:55 2013
Return-Path: <Carl.Wuyts@technicolor.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D02DB11E822E for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 01:30:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.499
X-Spam-Level: 
X-Spam-Status: No, score=-6.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OS-38MCZtWGK for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 01:30:50 -0700 (PDT)
Received: from na3sys009aog113.obsmtp.com (na3sys009aog113.obsmtp.com [74.125.149.209]) by ietfa.amsl.com (Postfix) with ESMTP id 3D05411E822D for <ipv6@ietf.org>; Mon, 28 Oct 2013 01:30:34 -0700 (PDT)
Received: from MOPESEDGE01.eu.thmulti.com ([129.35.174.203]) (using TLSv1) by na3sys009aob113.postini.com ([74.125.148.12]) with SMTP ID DSNKUm4goZWMrCQ5MgjSQYNClPDbKtfop0AK@postini.com; Mon, 28 Oct 2013 01:30:39 PDT
Received: from MOPESMAILHC02.eu.thmulti.com (141.11.100.29) by mail3.technicolor.com (141.11.253.22) with Microsoft SMTP Server (TLS) id 8.3.298.1; Mon, 28 Oct 2013 09:28:05 +0100
Received: from MOPESMBX01.eu.thmulti.com ([169.254.1.71]) by MOPESMAILHC02.eu.thmulti.com ([141.11.100.29]) with mapi; Mon, 28 Oct 2013 09:28:05 +0100
From: Wuyts Carl <Carl.Wuyts@technicolor.com>
To: Jeroen Massar <jeroen@massar.ch>, Octavio Alvarez <alvarezp@alvarezp.ods.org>
Date: Mon, 28 Oct 2013 09:28:03 +0100
Subject: RE: Why /64
Thread-Topic: Why /64
Thread-Index: Ac7Tt1g3Lo1LesjSRUqunVFAFSxg5QAABgIQ
Message-ID: <3135C2851EB6764BACEF35D8B495596806FAC25D4E@MOPESMBX01.eu.thmulti.com>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar>	<526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org> <526E1F5A.2070901@massar.ch>
In-Reply-To: <526E1F5A.2070901@massar.ch>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 08:30:56 -0000

+1 for the /64 on the link and /48 for enterprise,=20

but "at least" a /56 for home (with /60 too tiny) ??
Can you elaborate on why you would need more than 4 bits subnets @ home?

-----Original Message-----
From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of Jer=
oen Massar
Sent: maandag 28 oktober 2013 9:25
To: Octavio Alvarez
Cc: <ipv6@ietf.org>
Subject: Re: Why /64

On 2013-10-27 16:53, Octavio Alvarez wrote:
> On 10/27/2013 02:26 AM, Jeroen Massar wrote:
>>> allows privacy,
>>
>> IMHO big nonsense. The company (amongst many others!) you work for=20
>> uses amongst others cookies to track their people, and if they really=20
>> bother could even use natural language structure, search query types,=20
>> and other behavior for breaking this 'privacy'. Also note that even=20
>> if the last 64bits are random, your company should be more than able=20
>> to say "oh, there are typically X users in there, it likely is Y"...
>=20
> Then why deprecate EUI-64?

I did not state anything like that. I have only raised concern about statin=
g that "IPv6 privacy addresses" are a real thing.

I am pro /64 per link and a /48 for Enterprise and at least /56 for Home-us=
er sites. (/60 is too tiny and not flexible enough)

Greets,
 Jeroen

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

From jeroen@massar.ch  Mon Oct 28 01:35:24 2013
Return-Path: <jeroen@massar.ch>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73FEA11E822A for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 01:35:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.908
X-Spam-Level: 
X-Spam-Status: No, score=-4.908 tagged_above=-999 required=5 tests=[AWL=1.691,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qzDwg7YWPzw4 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 01:35:19 -0700 (PDT)
Received: from icaras.de.unfix.org (icaras.de.unfix.org [78.47.209.234]) by ietfa.amsl.com (Postfix) with ESMTP id 9E4E011E8141 for <ipv6@ietf.org>; Mon, 28 Oct 2013 01:35:17 -0700 (PDT)
Received: from kami.ch.unfix.org (kami.ch.unfix.org [IPv6:2001:1620:f42:99:7256:81ff:fea5:2925]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeroen) by icaras.de.unfix.org (Postfix) with ESMTPSA id 2DF49801C2A2; Mon, 28 Oct 2013 09:35:10 +0100 (CET)
Message-ID: <526E21C5.9080707@massar.ch>
Date: Mon, 28 Oct 2013 09:35:17 +0100
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar
MIME-Version: 1.0
To: trejrco@gmail.com, "<ipv6@ietf.org>" <ipv6@ietf.org>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com>	<526AACA5.7090604@si6networks.com>	<E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<526AC8AF.4060608@si6networks.com>	<8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com>	<CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com>	<526CDC59.4070204@massar.ch>	<CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com>	<CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com>	<526D0F47.5040803@massar.ch> <CALOgxGaoB_u+br5bpyVu-A0w8vD=QjYkrzaPqYrrhtPK=z6BEw@mail.gmail.com>
In-Reply-To: <CALOgxGaoB_u+br5bpyVu-A0w8vD=QjYkrzaPqYrrhtPK=z6BEw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 08:35:24 -0000

On 2013-10-27 20:04, TJ wrote:
>     >>> IMHO big nonsense. The company (amongst many others!) you work for
>     > uses amongst others cookies to track their people,
>     >>
>     >> Not sure we want to get into that argument here, but
>     >
>     > I _don't_ want to get into it here but I want to briefly support
>     Lorenzo
>     > on privacy.  Privacy through controlling tracking of an IP address is
>     > very different in mechanism and result from higher layer end-to-end
>     > privacy.
> 
> 
> First off, ++1 to Lorenzo on all counts (and Scott, Karl).

You can +1 without facts or any backing details, but the fun thing is,
it is no difference at all: privacy addresses do not make you "private"
in any way or form.


The only thing higher levels gives the adversary is a easier detection
and correlation. But unless you have exactly the same packet signature
and you are hitting the same sites as other people in your /64 or /48
you are unique.

Please note that a IPv6 Privacy Address is for a period of time, not per
application (at least I have not seen an OS do that yet, it could, but
they do not).

As such, when your HTTP browser goes to a site, that IP address is
identified as you; then anything else goes to another site, and voila,
they know that that connection is also related to you. Then your privacy
time window expires, you connect to that second site again, which is not
HTTP, but as you have been there just a bit ago, there is a high chance
that that is still you.

>     It does not matter if you have 1 IPv4 address with 2000 people behind
>     it, or 1 /48 with 2000 people behind it.
> 
>     The algorithms to de-anonimize and differentiate between the real hosts
>     behind them exist.
> 
>     Cookies are one way to do that, complete browser profiles or other
>     differences in the client, be that the tcp stack level another. For
>     other protocols it is all much easier as they are typically already
>     authenticated anyway or have other bits.
> 
> 
> 
> Having said that, FWIW - I partially disagree with Jeron here - it does
> matter.

With what exact part do you disagree and what part does matter?


> A user can have browser extensions, multiple browsers (or
> mutliple VMs with different OSes) and have a fairly good level of
> privacy if so desires - as long as the underlying L3 provisioned does
> not prevent it.  Is may not be exactly mainstream / commonplace, but not
> uncommon enough to ignore (IMHO) either.

Even though that would give you separate addresses and would initially
give that user separate identities that are being tracked, that user is
still coming out of the same /64 or /48.

Thus on the IP level indeed it initially looks like multiple users. But
as various organizations are pretty good at estimating amount of users
in a location, they can easily guess that it is the same person anyway.


I'll state again: if you want privacy use a mixnet, eg Tor.
(and even then you are exposing all your random bits, thus beware what
protocols and tools you use)

Greets,
 Jeroen


From roland.bless@kit.edu  Mon Oct 28 01:36:51 2013
Return-Path: <roland.bless@kit.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9F5311E822E for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 01:36:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.319
X-Spam-Level: 
X-Spam-Status: No, score=-6.319 tagged_above=-999 required=5 tests=[AWL=-0.070, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4taIuaYnq6jI for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 01:36:44 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) by ietfa.amsl.com (Postfix) with ESMTP id A4CBC11E8146 for <ipv6@ietf.org>; Mon, 28 Oct 2013 01:36:41 -0700 (PDT)
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5]) by iramx2.ira.uni-karlsruhe.de with esmtps port 25  id 1VaiJI-0000ZM-Uv; Mon, 28 Oct 2013 09:36:30 +0100
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=vorta.tm.kit.edu) by irams1.ira.uni-karlsruhe.de with esmtp port 25  id 1VaiJS-0003us-9n; Mon, 28 Oct 2013 09:36:38 +0100
Received: from [IPv6:::1] (ip6-localhost [IPv6:::1]) by vorta.tm.kit.edu (Postfix) with ESMTPS id 2C735A8067F; Mon, 28 Oct 2013 09:36:37 +0100 (CET)
Message-ID: <526E2214.1060800@kit.edu>
Date: Mon, 28 Oct 2013 09:36:36 +0100
From: "Bless, Roland (TM)" <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Tim Chown <tjc@ecs.soton.ac.uk>, 6man List <ipv6@ietf.org>
Subject: Re: Why /64 [was Deprecating EUI-64 Based IPv6 Addresses]
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar>	<526AA24F.6010609@gmail.com>	<526AACA5.7090604@si6networks.com>	<E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<526B0A30.9060600@gmail.com> <526B0E15.8080602@si6networks.com>	<F6264230-19EB-4FEC-910C-C86F14C28A83@ecs.soton.ac.uk> <EMEW3|d9e74aba9561d767d4403c2b6597aed6p9P8h103tjc|ecs.soton.ac.uk|F6264230-19EB-4FEC-910C-C86F14C28A83@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|d9e74aba9561d767d4403c2b6597aed6p9P8h103tjc|ecs.soton.ac.uk|F6264230-19EB-4FEC-910C-C86F14C28A83@ecs.soton.ac.uk>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-ATIS-AV: ClamAV (irams1.ira.uni-karlsruhe.de)
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1382949390.
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 08:36:51 -0000

Hi,

On 26.10.2013 09:41, Tim Chown wrote:
>> OTOH, deprecating Modified EUI-64 is a local policy which is 
>> incrementally-deployable.
> 
> Well yes, there’s obviously a large deployed code base where /64 has
> been assumed. And changing that assumption may simply not be
> practical.
> 
> But… for example, some people who were concerned over the ND cache
> problem have run with /120 and DHCPv6. I’m not advocating that.
> Indeed the homenet arch text specifically mentions not using such
> “tricks" where the ISP only allocates one /64 to a home which
> requires multiple subnets.
> 
> I’m just suggesting it would be interesting to spend a little time to
> figure out where the /64 really is “burnt in” so that, if there were
> a desire to explore proposing a /80 or /96 or whatever for a future
> SLAAC, we would have a clearer idea of what the implications would
> be, and how/if an incremental progression to variable length SLAAC
> could be facilitated.

+1

Regards,
 Roland


From jeroen@massar.ch  Mon Oct 28 01:46:09 2013
Return-Path: <jeroen@massar.ch>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E5B911E823F for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 01:46:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 019Pejus7eIe for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 01:46:07 -0700 (PDT)
Received: from icaras.de.unfix.org (icaras.de.unfix.org [IPv6:2a01:4f8:130:74c1:5054:ff:fec4:f7d4]) by ietfa.amsl.com (Postfix) with ESMTP id C63D211E8237 for <ipv6@ietf.org>; Mon, 28 Oct 2013 01:46:04 -0700 (PDT)
Received: from kami.ch.unfix.org (kami.ch.unfix.org [IPv6:2001:1620:f42:99:7256:81ff:fea5:2925]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeroen) by icaras.de.unfix.org (Postfix) with ESMTPSA id 06BE8801C2A2; Mon, 28 Oct 2013 09:45:56 +0100 (CET)
Message-ID: <526E244B.1030103@massar.ch>
Date: Mon, 28 Oct 2013 09:46:03 +0100
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar
MIME-Version: 1.0
To: Wuyts Carl <Carl.Wuyts@technicolor.com>,  Octavio Alvarez <alvarezp@alvarezp.ods.org>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar>	<526AA24F.6010609@gmail.com>	<526AACA5.7090604@si6networks.com>	<E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<526AC8AF.4060608@si6networks.com>	<8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com>	<CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com>	<526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org> <526E1F5A.2070901@massar.ch> <3135C2851EB6764BACEF35D8B495596806FAC25D4E@MOPESMBX01.eu.thmulti.com>
In-Reply-To: <3135C2851EB6764BACEF35D8B495596806FAC25D4E@MOPESMBX01.eu.thmulti.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 08:46:09 -0000

On 2013-10-28 09:28, Wuyts Carl wrote:
> +1 for the /64 on the link and /48 for enterprise, 
> 
> but "at least" a /56 for home (with /60 too tiny) ??
> Can you elaborate on why you would need more than 4 bits subnets @ home?

Because I am one of the examples where I have, at home, already have
more than 16 VLANs at home.

But I might be special, I can only assume several other people here have
similar large home networks. I have so many VLANs as I like things in
separate networks, many do not even get Internet connectivity but they
are globally addressable. Note that things go very quickly when you have
things like IPv6 connected lightbulbs; though these are in a VLAN per
room so that I can send a multicast message to that VLAN and turn them
all on/off etc in one go.

The original point of the /48 was that nobody should have to bother
thinking about bits as there is enough space.

Clearly some ISPs see some scaling issues inside their network and thus
think that /56's solve that. Hence why ARIN at first then changed that
limit.

One routing slot though is still one routing slot, not more, thus if it
is a /56 or a /48 should not matter.

I am quite fine with a /56 for home users, it definitely works for me
and thus should for really everybody else in a home network.

But enterprises/companies should per default get a /48 per site so that
it is always the same and they can at least number-plan wise renumber
easily.

Hence the /64 link (autoconfig is great), /56 for enter home and /48 for
companies.

Greets,
 Jeroen


PS: one problem with the 'you get a /48' etc is that some ISPs steal the
first /64 for the uplink, some others do not. Hence why if one is doing
a network plan skip the first /64 as it will save some pain if you ever
switch. (Though it would just mean changing one VLAN to other bits).


From jeroen@massar.ch  Mon Oct 28 01:49:26 2013
Return-Path: <jeroen@massar.ch>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB76E21F9D05 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 01:49:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.04
X-Spam-Level: 
X-Spam-Status: No, score=-5.04 tagged_above=-999 required=5 tests=[AWL=1.259,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u51VIGC+TeSC for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 01:49:20 -0700 (PDT)
Received: from icaras.de.unfix.org (icaras.de.unfix.org [78.47.209.234]) by ietfa.amsl.com (Postfix) with ESMTP id A4A3E11E8230 for <ipv6@ietf.org>; Mon, 28 Oct 2013 01:49:19 -0700 (PDT)
Received: from kami.ch.unfix.org (kami.ch.unfix.org [IPv6:2001:1620:f42:99:7256:81ff:fea5:2925]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeroen) by icaras.de.unfix.org (Postfix) with ESMTPSA id 02CD6801C2A2; Mon, 28 Oct 2013 09:49:11 +0100 (CET)
Message-ID: <526E250E.5050607@massar.ch>
Date: Mon, 28 Oct 2013 09:49:18 +0100
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>,  Scott Brim <scott.brim@gmail.com>, "<ipv6@ietf.org>" <ipv6@ietf.org>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com>	<526AACA5.7090604@si6networks.com>	<E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<526AC8AF.4060608@si6networks.com>	<8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com>	<CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com>	<526CDC59.4070204@massar.ch>	<CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com>	<CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com> <CAKFn1SG1PC_kA-pO5Or8VyeaOzvLfpmQe0LiiYkXU_HzNqGzCQ@mail.gmail.com>
In-Reply-To: <CAKFn1SG1PC_kA-pO5Or8VyeaOzvLfpmQe0LiiYkXU_HzNqGzCQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 08:49:26 -0000

On 2013-10-27 15:50, Roger Jørgensen wrote:
[..]
> Privacy isn't just one single thing. That the user might lose privacy
> elsewhere in the entire stack that make up Internet, that's NOT an
> argument to give up /64 because we have lost privacy anyhow.

I am NOT arguing that a /64 should go the way of the dodo.
I am only stating that this "IPv6 Privacy Address" thing is a myth.

> This /64 split is a good construction.

I fully agree, but IPv6 Privacy Addresses is not one of them.

Greets,
 Jeroen


From lorenzo@google.com  Mon Oct 28 01:50:55 2013
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2994E11E8237 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 01:50:55 -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=[AWL=0.077, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p1WhW7TD+vjP for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 01:50:54 -0700 (PDT)
Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com [IPv6:2607:f8b0:4001:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 95F9A11E8243 for <ipv6@ietf.org>; Mon, 28 Oct 2013 01:50:47 -0700 (PDT)
Received: by mail-ie0-f169.google.com with SMTP id ar20so10777282iec.14 for <ipv6@ietf.org>; Mon, 28 Oct 2013 01:50:46 -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=zBjtxgDoynOCP97/H1bRg29Y8vQc0/ydl1fJNbbAMBk=; b=hrhwh+BFX1CIsuT9Ghd9yYPk/u66SOcHOGQh87zWQL25iYp3KcbDvF47xLPGw7UOi9 p1f7ERzHXeUE+92flMbPgf3Yl3nEr5GOIWKVTT0QAZobjB5ERHuw+kdf+2TMHRo8ROe5 L6Z/Tz66IYHsLA5g9ZxW9OxTFtxwHDeCXg7fuXOjiJnnitLbQEihFa4GZPQsEDxEX3IW JGofKdCvdAwDz65E9GffSbSqlu/DI4SGGYjwerrLdrDFlIaARUotWeYqEY5dFQR73DIa hWM9XpSy+DaSuX7VWgsAXqYx5R+pMUThxGqYGkSK7wCNGbVrDrrXcQL9nX/snRjEkWt/ dbnA==
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=zBjtxgDoynOCP97/H1bRg29Y8vQc0/ydl1fJNbbAMBk=; b=S2O0rjiX5xanMEO3PJ7Ck8EdumiwrWr/XJxXzJsznBsIJ08NMPOr8GCnOH/s79Vuyn cRlF3IzRdqVfY21fX1ZLmA8FoGPWlX+E+fRtaW5ptt5O3vYJetw8hWrWnOadHYgaM7W/ hFX6eejq5jjOPWgeZlri+yE/9KS4A9CCPUGcsVZvDUaNvW5oy6qz9GG2XePpvZRhQhEb xAk+nurQOnn/W24XLC4oEEN1f+BOEbBhr54nKUpA27EAte2eXgHzndmdKkGr52C2n8V8 p5thRHekOO+tz/VMC2qM5ZSupCMO19vS5Vrd6b02yqbwgz4JopwU3rgF5ZK5wXHMuM5V 5KtA==
X-Gm-Message-State: ALoCoQniytYl/Y/KdFHqkH1MBLUO/a4gwBgidtQgimdDf0TSMqIyD9zpUwWpZcd279noEZRK+p4F2FgrM0H06MgkCDs3iDUGqcvZ6S7Yrbe+cPcJVhWpSwlRMTl8XzYcF3R7u73PWX8gufo6d8w87D8S78kqPBH5cYb4YT6UODnwpmNAmbx11I7QCSrOlv/zsgzAUVzgZ4MS
X-Received: by 10.50.114.168 with SMTP id jh8mr7625555igb.6.1382950246502; Mon, 28 Oct 2013 01:50:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.86.106 with HTTP; Mon, 28 Oct 2013 01:50:26 -0700 (PDT)
In-Reply-To: <526E250E.5050607@massar.ch>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com> <CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com> <CAKFn1SG1PC_kA-pO5Or8VyeaOzvLfpmQe0LiiYkXU_HzNqGzCQ@mail.gmail.com> <526E250E.5050607@massar.ch>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 28 Oct 2013 17:50:26 +0900
Message-ID: <CAKD1Yr1evbMf1pD4yBrZyvF2XLXGOre3bHDB0gOZTLme7vnh2A@mail.gmail.com>
Subject: Re: Why /64
To: Jeroen Massar <jeroen@massar.ch>
Content-Type: multipart/alternative; boundary=089e01229f862f757604e9c93274
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 08:50:55 -0000

--089e01229f862f757604e9c93274
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Oct 28, 2013 at 5:49 PM, Jeroen Massar <jeroen@massar.ch> wrote:

> I am NOT arguing that a /64 should go the way of the dodo.
> I am only stating that this "IPv6 Privacy Address" thing is a myth.
>

Can you do so on another thread, please? This thread is about /64.

--089e01229f862f757604e9c93274
Content-Type: text/html; charset=ISO-8859-1

<div dir="ltr">On Mon, Oct 28, 2013 at 5:49 PM, Jeroen Massar <span dir="ltr">&lt;<a href="mailto:jeroen@massar.ch" target="_blank">jeroen@massar.ch</a>&gt;</span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I am NOT arguing that a /64 should go the way of the dodo.<br>
I am only stating that this &quot;IPv6 Privacy Address&quot; thing is a myth.<br></blockquote><div><br></div><div>Can you do so on another thread, please? This thread is about /64.</div></div></div></div>

--089e01229f862f757604e9c93274--

From jeroen@massar.ch  Mon Oct 28 01:55:52 2013
Return-Path: <jeroen@massar.ch>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9463611E8244 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 01:55:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.37
X-Spam-Level: 
X-Spam-Status: No, score=-5.37 tagged_above=-999 required=5 tests=[AWL=1.229,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FtuNEAoSg7O7 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 01:55:47 -0700 (PDT)
Received: from icaras.de.unfix.org (icaras.de.unfix.org [78.47.209.234]) by ietfa.amsl.com (Postfix) with ESMTP id 722B311E823D for <ipv6@ietf.org>; Mon, 28 Oct 2013 01:55:29 -0700 (PDT)
Received: from kami.ch.unfix.org (kami.ch.unfix.org [IPv6:2001:1620:f42:99:7256:81ff:fea5:2925]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeroen) by icaras.de.unfix.org (Postfix) with ESMTPSA id 108F3801C2A2; Mon, 28 Oct 2013 09:55:21 +0100 (CET)
Message-ID: <526E267E.2070705@massar.ch>
Date: Mon, 28 Oct 2013 09:55:26 +0100
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com> <CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com> <CAKFn1SG1PC_kA-pO5Or8VyeaOzvLfpmQe0LiiYkXU_HzNqGzCQ@mail.gmail.com> <526E250E.5050607@massar.ch> <CAKD1Yr1evbMf1pD4yBrZyvF2XLXGOre3bHDB0gOZTLme7vnh2A@mail.gmail.com>
In-Reply-To: <CAKD1Yr1evbMf1pD4yBrZyvF2XLXGOre3bHDB0gOZTLme7vnh2A@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 08:55:53 -0000

On 2013-10-28 09:50, Lorenzo Colitti wrote:
> On Mon, Oct 28, 2013 at 5:49 PM, Jeroen Massar <jeroen@massar.ch
> <mailto:jeroen@massar.ch>> wrote:
> 
>     I am NOT arguing that a /64 should go the way of the dodo.
>     I am only stating that this "IPv6 Privacy Address" thing is a myth.
> 
> 
> Can you do so on another thread, please? This thread is about /64.

You do realize that YOU made that point right?

>From your message on 27 Oct 2013 17:55:00 +0900:
http://www.ietf.org/mail-archive/web/ipv6/current/msg19238.html

> I think the split /64 extremely useful because it provides a minimum
> size assignment that makes autoconfiguration easy, allows privacy,
> and gives users the capability to number multiple applications or
> multiple devices without having to use NAT.

As you wrote that, I noted that "allows privacy" is a myth.

You brought this point up, I argued against that single point (and
nothing else btw).

If you do not want to discuss it, then you should not have mentioned it
and you should not be arguing against it, simple.

Greets,
 Jeroen


From lorenzo@google.com  Mon Oct 28 01:57:40 2013
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59E7F11E821E for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 01:57:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level: 
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[AWL=0.074,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SYtldNu74a5y for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 01:57:39 -0700 (PDT)
Received: from mail-ie0-x233.google.com (mail-ie0-x233.google.com [IPv6:2607:f8b0:4001:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id 8383811E823D for <ipv6@ietf.org>; Mon, 28 Oct 2013 01:57:39 -0700 (PDT)
Received: by mail-ie0-f179.google.com with SMTP id aq17so11059798iec.10 for <ipv6@ietf.org>; Mon, 28 Oct 2013 01:57:38 -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=MRvABk7LnAM7tSOHQqZZtYDzMr4meR8dmo7aKvrIZKk=; b=ecsggCfDQTEngeHOxDzfrc/EpCAhqBzrf3qWrUzPQdCJlgSkcnTWbGIYgrFtmbdJHA /Owx0fEz1ql0aey5FLUzANo3z1eyBde6DK9tT9CdQSTanKLP9rrF2x86D+bHvaSjpK2r sKCK6qoRq77JVjyE8VG2beoUrmMuQrUUFr/frwYaLut3vedVT/iMNSJHEBFCRW6WAVE9 DRnYqS7yziqGEcZKtFvS68SCvPOEtqqO1N4O21vNZdyvJUDEdL07BYdqhsFv2a2Zxtim yfkr8s07078mOb+0mVRngbqtqWPq4AhJ2njP4tjdI3zIyYH+rx7wpQQTVMpfnXbuynC/ bHKQ==
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=MRvABk7LnAM7tSOHQqZZtYDzMr4meR8dmo7aKvrIZKk=; b=cimm9fcjeGLuDTl1ZsXqnTmT5VPd0T0QWjn5XCOfeWEXujFKepKX3+9nYFPdDIEWG0 GohNfTcQfOyRXgqr+knxh3zkO7RYfCy03/BptPfhB+uusLOEYSImIHQKHOBcNFZE4293 gSee2YR8njJqG+kV0UUE2imjd0d2VGVK5sJHNZZXt9qmToRqGNuyPOQ9/TpiiMUS1gax MCoc8UkSOdvLLw1QE4xWihr4v9RQibCfUrINn9rg2o7HdsxTy2lz81/P+XzSr58Zvo4h ehiLqacrKS+uBZWW72h+669bzuq6kKz+5qbHrDhgJJDKtFrlFI5P1rIEWL4dkHE8WU+C Ep8g==
X-Gm-Message-State: ALoCoQkYb+IjPkzES65YbvM2zpYs41XyaL1ZBTMvvar1+GL8BgnK+TcgqW/RGwnPZ0b7yV4PcaW4KcNDrAMiKh3UgWOE2oTtI9mSrpNK8vMC0VmiabRBJOJWJrlrb/yJW/dVtymfZgyF80p0GO1N7TW44r0eFQM+V5Agm6/QbdyODWXsy7CCf9GG4F0ATQoVvoYCJo8SJuNU
X-Received: by 10.50.153.50 with SMTP id vd18mr7642334igb.6.1382950658755; Mon, 28 Oct 2013 01:57:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.86.106 with HTTP; Mon, 28 Oct 2013 01:57:18 -0700 (PDT)
In-Reply-To: <526E267E.2070705@massar.ch>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com> <CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com> <CAKFn1SG1PC_kA-pO5Or8VyeaOzvLfpmQe0LiiYkXU_HzNqGzCQ@mail.gmail.com> <526E250E.5050607@massar.ch> <CAKD1Yr1evbMf1pD4yBrZyvF2XLXGOre3bHDB0gOZTLme7vnh2A@mail.gmail.com> <526E267E.2070705@massar.ch>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 28 Oct 2013 17:57:18 +0900
Message-ID: <CAKD1Yr1K+4H+Gq9dWK-tVJu_3_pw+q7Q1owGz69eg6jy--XN5A@mail.gmail.com>
Subject: Re: Why /64
To: Jeroen Massar <jeroen@massar.ch>
Content-Type: multipart/alternative; boundary=089e013a009ec2143c04e9c94a59
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 08:57:40 -0000

--089e013a009ec2143c04e9c94a59
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Oct 28, 2013 at 5:55 PM, Jeroen Massar <jeroen@massar.ch> wrote:

> >     I am NOT arguing that a /64 should go the way of the dodo.
> >     I am only stating that this "IPv6 Privacy Address" thing is a myth.
> >
> >
> > Can you do so on another thread, please? This thread is about /64.
>
> You do realize that YOU made that point right?
>

Yes, and I withdrew it. I withdraw it again. Please let's not talk about it
on this thread any more.

--089e013a009ec2143c04e9c94a59
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Mon, Oct 28, 2013 at 5:55 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><div class=3D"gmail_extra"><div class=3D"=
gmail_quote">


<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div>&gt; =A0 =A0 I am NOT arguing that a /6=
4 should go the way of the dodo.<br></div><div>
&gt; =A0 =A0 I am only stating that this &quot;IPv6 Privacy Address&quot; t=
hing is a myth.<br>
&gt;<br>
&gt;<br>
&gt; Can you do so on another thread, please? This thread is about /64.<br>
<br>
</div>You do realize that YOU made that point right?<br></blockquote><div><=
br>Yes, and I withdrew it. I withdraw it again. Please let&#39;s not talk a=
bout it on this thread any more.</div></div></div></div>

--089e013a009ec2143c04e9c94a59--

From Carl.Wuyts@technicolor.com  Mon Oct 28 01:59:19 2013
Return-Path: <Carl.Wuyts@technicolor.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27BFC11E8241 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 01:59:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Level: 
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FhR8Bwmsiyx8 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 01:59:11 -0700 (PDT)
Received: from na3sys009aog130.obsmtp.com (na3sys009aog130.obsmtp.com [74.125.149.143]) by ietfa.amsl.com (Postfix) with ESMTP id 22D8F21F9E28 for <ipv6@ietf.org>; Mon, 28 Oct 2013 01:59:01 -0700 (PDT)
Received: from MOPESEDGE01.eu.thmulti.com ([129.35.174.203]) (using TLSv1) by na3sys009aob130.postini.com ([74.125.148.12]) with SMTP ID DSNKUm4nRv/tx0LziBJxomDNVG7W7fyONVaW@postini.com; Mon, 28 Oct 2013 01:59:10 PDT
Received: from MOPESMAILHC03.eu.thmulti.com (141.11.100.132) by mail3.technicolor.com (141.11.253.22) with Microsoft SMTP Server (TLS) id 8.3.298.1; Mon, 28 Oct 2013 09:54:01 +0100
Received: from MOPESMBX01.eu.thmulti.com ([169.254.1.71]) by MOPESMAILHC03.eu.thmulti.com ([141.11.100.132]) with mapi; Mon, 28 Oct 2013 09:54:02 +0100
From: Wuyts Carl <Carl.Wuyts@technicolor.com>
To: Jeroen Massar <jeroen@massar.ch>, Octavio Alvarez <alvarezp@alvarezp.ods.org>
Date: Mon, 28 Oct 2013 09:53:59 +0100
Subject: RE: Why /64
Thread-Topic: Why /64
Thread-Index: Ac7Tuiah1UlvtIjlTkqIFlJXFV1BpAAAJV/Q
Message-ID: <3135C2851EB6764BACEF35D8B495596806FAC25DCA@MOPESMBX01.eu.thmulti.com>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar>	<526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org> <526E1F5A.2070901@massar.ch> <3135C2851EB6764BACEF35D8B495596806FAC25D4E@MOPESMBX01.eu.thmulti.com> <526E244B.1030103@massar.ch>
In-Reply-To: <526E244B.1030103@massar.ch>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 08:59:19 -0000

Ok, thx for the update.
I don't think that you're the "default/avg" user here :-), hence I don't be=
lieve they will use your setup as an example to set for a specific ia_pd pr=
efix length.
I agree there's plenty of space, but lots of ISPs claim people said the sam=
e in IPv4 era, hence are cautious to set it "too big".

Anyway, I must say to see lots of /56s, so looks ok in lots of occasion, bu=
t for sure no global consensus / approach on this, I see anything between 6=
4 and /48 for the home being used today.

Regs
Carl
-----Original Message-----
From: Jeroen Massar [mailto:jeroen@massar.ch]=20
Sent: maandag 28 oktober 2013 9:46
To: Wuyts Carl; Octavio Alvarez
Cc: <ipv6@ietf.org>
Subject: Re: Why /64

On 2013-10-28 09:28, Wuyts Carl wrote:
> +1 for the /64 on the link and /48 for enterprise,
>=20
> but "at least" a /56 for home (with /60 too tiny) ??
> Can you elaborate on why you would need more than 4 bits subnets @ home?

Because I am one of the examples where I have, at home, already have more t=
han 16 VLANs at home.

But I might be special, I can only assume several other people here have si=
milar large home networks. I have so many VLANs as I like things in separat=
e networks, many do not even get Internet connectivity but they are globall=
y addressable. Note that things go very quickly when you have things like I=
Pv6 connected lightbulbs; though these are in a VLAN per room so that I can=
 send a multicast message to that VLAN and turn them all on/off etc in one =
go.

The original point of the /48 was that nobody should have to bother thinkin=
g about bits as there is enough space.

Clearly some ISPs see some scaling issues inside their network and thus thi=
nk that /56's solve that. Hence why ARIN at first then changed that limit.

One routing slot though is still one routing slot, not more, thus if it is =
a /56 or a /48 should not matter.

I am quite fine with a /56 for home users, it definitely works for me and t=
hus should for really everybody else in a home network.

But enterprises/companies should per default get a /48 per site so that it =
is always the same and they can at least number-plan wise renumber easily.

Hence the /64 link (autoconfig is great), /56 for enter home and /48 for co=
mpanies.

Greets,
 Jeroen


PS: one problem with the 'you get a /48' etc is that some ISPs steal the fi=
rst /64 for the uplink, some others do not. Hence why if one is doing a net=
work plan skip the first /64 as it will save some pain if you ever switch. =
(Though it would just mean changing one VLAN to other bits).


From jeroen@massar.ch  Mon Oct 28 02:11:30 2013
Return-Path: <jeroen@massar.ch>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3488121F9FF3 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 02:11:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.523
X-Spam-Level: 
X-Spam-Status: No, score=-5.523 tagged_above=-999 required=5 tests=[AWL=1.076,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uNVwkSElasud for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 02:11:22 -0700 (PDT)
Received: from icaras.de.unfix.org (icaras.de.unfix.org [78.47.209.234]) by ietfa.amsl.com (Postfix) with ESMTP id 03F7B21F9D5E for <ipv6@ietf.org>; Mon, 28 Oct 2013 02:11:13 -0700 (PDT)
Received: from kami.ch.unfix.org (kami.ch.unfix.org [IPv6:2001:1620:f42:99:7256:81ff:fea5:2925]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeroen) by icaras.de.unfix.org (Postfix) with ESMTPSA id 35DAA801C2A2; Mon, 28 Oct 2013 10:11:05 +0100 (CET)
Message-ID: <526E2A2E.7030206@massar.ch>
Date: Mon, 28 Oct 2013 10:11:10 +0100
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar
MIME-Version: 1.0
To: Wuyts Carl <Carl.Wuyts@technicolor.com>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar>	<526AA24F.6010609@gmail.com>	<526AACA5.7090604@si6networks.com>	<E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<526AC8AF.4060608@si6networks.com>	<8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com>	<CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com>	<526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org> <526E1F5A.2070901@massar.ch> <3135C2851EB6764BACEF35D8B495596806FAC25D4E@MOPESMBX01.eu.thmulti.com> <526E244B.1030103@massar.ch> <3135C2851EB6764BACEF35D8B495596806FAC25DCA@MOPESMBX01.eu.thmulti.com>
In-Reply-To: <3135C2851EB6764BACEF35D8B495596806FAC25DCA@MOPESMBX01.eu.thmulti.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 09:11:30 -0000

On 2013-10-28 09:53, Wuyts Carl wrote:
> Ok, thx for the update. I don't think that you're the "default/avg"
> user here :-), hence I don't believe they will use your setup as an
> example to set for a specific ia_pd prefix length. I agree there's
> plenty of space, but lots of ISPs claim people said the same in IPv4
> era, hence are cautious to set it "too big".

We can't teach people to learn math nor can we teach them to think of
routing slots and the fact that aggregation makes things so much easier.

We also cannot teach people who are in the networking business and who
request the prefix they get from their RIR to request a large enough
block, and then are 'we are running out of space' or funnier, make
comments about other ISPs getting large blocks as they did fill in the
paperwork. The allocation lists show clearly that several ISPs have
upgraded their prefixes to much larger sizes than the default /32 over
time though; thus hopefully this happens before there becomes a need to
do multiple disjunct /32s per ISP, though several have already gone for
that model to 'cover the world' or 'being able to deaggregate per
continent'.

Like in IPv4 there are also already several ISPs again who are limiting
the amount of time that a IPv6 delegation is routed to a single user,
and they cycle it on regular basis; hence the user not receiving a
static prefix and thus having to renumber all the time and thus it being
quite annoying.

These primarily are all business decisions though, little the IETF can
do about unfortunately. There is enough documentation out there, the
people in charge will go their own way without heeding the advice of
their fellow networkers...

> Anyway, I must say to see lots of /56s, so looks ok in lots of
> occasion, but for sure no global consensus / approach on this, I see
> anything between 64 and /48 for the home being used today.

In the ARIN region ISPs are supposed to do at minimum /56, as this is in
the allocation guidelines. Similar allocation guidelines exist for the
other RIRs.

Unfortunately there is no 'forced' requirement from the RIR and ISPs
thus end up picking whatever they deem good for them.

Greets,
 Jeroen

From jeroen@massar.ch  Mon Oct 28 02:11:56 2013
Return-Path: <jeroen@massar.ch>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 887C111E8248 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 02:11:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CB+Y2cAzXB+x for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 02:11:54 -0700 (PDT)
Received: from icaras.de.unfix.org (icaras.de.unfix.org [IPv6:2a01:4f8:130:74c1:5054:ff:fec4:f7d4]) by ietfa.amsl.com (Postfix) with ESMTP id BE37911E816F for <ipv6@ietf.org>; Mon, 28 Oct 2013 02:11:52 -0700 (PDT)
Received: from kami.ch.unfix.org (kami.ch.unfix.org [IPv6:2001:1620:f42:99:7256:81ff:fea5:2925]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeroen) by icaras.de.unfix.org (Postfix) with ESMTPSA id 2359D801C2A2; Mon, 28 Oct 2013 10:11:45 +0100 (CET)
Message-ID: <526E2A56.7070503@massar.ch>
Date: Mon, 28 Oct 2013 10:11:50 +0100
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com> <CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com> <CAKFn1SG1PC_kA-pO5Or8VyeaOzvLfpmQe0LiiYkXU_HzNqGzCQ@mail.gmail.com> <526E250E.5050607@massar.ch> <CAKD1Yr1evbMf1pD4yBrZyvF2XLXGOre3bHDB0gOZTLme7vnh2A@mail.gmail.com> <526E267E.2070705@massar.ch> <CAKD1Yr1K+4H+Gq9dWK-tVJu_3_pw+q7Q1owGz69eg6jy--XN5A@mail.gmail.com>
In-Reply-To: <CAKD1Yr1K+4H+Gq9dWK-tVJu_3_pw+q7Q1owGz69eg6jy--XN5A@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 09:11:56 -0000

On 2013-10-28 09:57, Lorenzo Colitti wrote:
> On Mon, Oct 28, 2013 at 5:55 PM, Jeroen Massar <jeroen@massar.ch
> <mailto:jeroen@massar.ch>> wrote:
> 
>     >     I am NOT arguing that a /64 should go the way of the dodo.
>     >     I am only stating that this "IPv6 Privacy Address" thing is a
>     myth.
>     >
>     >
>     > Can you do so on another thread, please? This thread is about /64.
> 
>     You do realize that YOU made that point right?
> 
> 
> Yes, and I withdrew it. I withdraw it again. Please let's not talk about
> it on this thread any more.

Can you please provide a link to the message in the archives where you
did? As I clearly did not see it.

Greets,
 Jeroen


From lorenzo@google.com  Mon Oct 28 02:23:12 2013
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EBAF11E824D for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 02:23:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level: 
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[AWL=0.071,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MDMRsm5CMShC for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 02:23:00 -0700 (PDT)
Received: from mail-ie0-x22b.google.com (mail-ie0-x22b.google.com [IPv6:2607:f8b0:4001:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 76F7511E8251 for <ipv6@ietf.org>; Mon, 28 Oct 2013 02:22:44 -0700 (PDT)
Received: by mail-ie0-f171.google.com with SMTP id tp5so11110346ieb.30 for <ipv6@ietf.org>; Mon, 28 Oct 2013 02:22:42 -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=Yr7URtXRN3fUBWWdLSfWskPRXXLVVRzxhWErENajFjo=; b=N9XOwCWL9Uh9yaVIO+zz5jZt3tazdiefI9IbGGtTdzZfpj7lK5Ry6GBeJVr2ciuDpy q3sdqb+WjQxMkVws0M6IOh+giAXnq8D4KFmU/yhH+x+gOtonj8sBEL9XyUeF9n8hv8BD JlUdk8GJQd2tNnZX0zJd7Oa/jyMzRkoCGMXk78qMsqdTnZolweNn3YVwyNVRD8NvZOg5 JxHNOJaWD001IkRmxkHItRQi1GPbUZ+QUf4JGEf1jN6ocxDeXr2/vgbY5FPJAg4MGPDs ATYpvzqg3QBL5xWJ2WrbUg6p54S0sXqWQ0rQL7QnVtFYski/87Hc7z5CRDMpMBO4/K9h 1Xjw==
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=Yr7URtXRN3fUBWWdLSfWskPRXXLVVRzxhWErENajFjo=; b=JX8lwtIOIgT3lUjutBHfI3C/X9n0oYQeqAwIBdAacFRnLJY9o0spLH892s0+XW5mk/ 01S4gMv814d6h/1ABHIQv0lXMbQuRz3BJp9ALE0yuGD7YPFydN/KbJUpVH5BBSqTEsGQ fqsD5Wa+yhRzoH1cCKWX2CvSt8c5+lINCfv2Ds1vSZ218wBhX7fkuHqfXN3UDuCjBO+0 Y2yPTA7lRUYGy/vUQTxAO93c3yT8APx2/Klmw23icbUGSd8F6zAKOEPJ8kLUNIeIYbsd RZGIX9eAx9LQIXbAkiNIrlpBk0Qfw0afXM32zhxiWKRInIp49UbpO2t4Xc0xn1sYzs6C r45A==
X-Gm-Message-State: ALoCoQmq7EfqR/i2vrug3LLM+xwa0Iu+KdFr43IQHOH91smsRaYQ5jcgDM7zHLZDvSUhnS7P0qxLYegc+3iy7kxuhXugNBgoTOklygfmZwPLV3zlqM1FSUvQbAwAgRvbyMh8cJ+M3Y9V3PBZqAcm4xzYyFn3x/1FJskhu3fqaRHkzymCcawZzObjr2FQSU216OXL/3+XVLIk
X-Received: by 10.42.30.143 with SMTP id v15mr12602656icc.24.1382952162512; Mon, 28 Oct 2013 02:22:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.86.106 with HTTP; Mon, 28 Oct 2013 02:22:22 -0700 (PDT)
In-Reply-To: <526E2A56.7070503@massar.ch>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com> <CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com> <CAKFn1SG1PC_kA-pO5Or8VyeaOzvLfpmQe0LiiYkXU_HzNqGzCQ@mail.gmail.com> <526E250E.5050607@massar.ch> <CAKD1Yr1evbMf1pD4yBrZyvF2XLXGOre3bHDB0gOZTLme7vnh2A@mail.gmail.com> <526E267E.2070705@massar.ch> <CAKD1Yr1K+4H+Gq9dWK-tVJu_3_pw+q7Q1owGz69eg6jy--XN5A@mail.gmail.com> <526E2A56.7070503@massar.ch>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 28 Oct 2013 18:22:22 +0900
Message-ID: <CAKD1Yr3quaLS8zmDuf301MHL_y+uLQg0UfAEU+Kk-hwfv0oqtw@mail.gmail.com>
Subject: Re: Why /64
To: Jeroen Massar <jeroen@massar.ch>
Content-Type: multipart/alternative; boundary=20cf301d3e7a63d54904e9c9a490
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 09:23:14 -0000

--20cf301d3e7a63d54904e9c9a490
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Oct 28, 2013 at 6:11 PM, Jeroen Massar <jeroen@massar.ch> wrote:

> > Yes, and I withdrew it. I withdraw it again. Please let's not talk about
>  > it on this thread any more.
>
> Can you please provide a link to the message in the archives where you
> did? As I clearly did not see it.
>

http://www.ietf.org/mail-archive/web/ipv6/current/msg19246.html : "sure.
There are other ways to track people than via IP addresses."

If you want to continue that discussion, please do so on a separate thread.

--20cf301d3e7a63d54904e9c9a490
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Mon, Oct 28, 2013 at 6:11 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><div class=3D"gmail_extra"><div class=3D"=
gmail_quote">

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div class=3D"im">&gt; Yes, and I withdrew it. I withdraw =
it again. Please let&#39;s not talk about<br>

</div><div class=3D"im">
&gt; it on this thread any more.<br>
<br>
</div>Can you please provide a link to the message in the archives where yo=
u<br>
did? As I clearly did not see it.<br></blockquote><div><br></div><div><a hr=
ef=3D"http://www.ietf.org/mail-archive/web/ipv6/current/msg19246.html">http=
://www.ietf.org/mail-archive/web/ipv6/current/msg19246.html</a> : &quot;sur=
e. There are other ways to track people than via IP addresses.&quot;<br>

</div><div><br></div><div>If you want to continue that discussion, please d=
o so on a separate thread.</div></div></div></div>

--20cf301d3e7a63d54904e9c9a490--

From sander@steffann.nl  Mon Oct 28 02:23:28 2013
Return-Path: <sander@steffann.nl>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF3A711E8254 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 02:23:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v-7KsOaOYHHh for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 02:23:23 -0700 (PDT)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:9e0:803::6]) by ietfa.amsl.com (Postfix) with ESMTP id B6CD911E8248 for <ipv6@ietf.org>; Mon, 28 Oct 2013 02:23:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id 16C5D16; Mon, 28 Oct 2013 10:22:58 +0100 (CET)
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 10024) with ESMTP id vk4QvtImm7FX; Mon, 28 Oct 2013 10:22:55 +0100 (CET)
Received: from macpro.10ww.steffann.nl (macpro.10ww.steffann.nl [37.77.56.75]) by mail.sintact.nl (Postfix) with ESMTPSA id 95F4524; Mon, 28 Oct 2013 10:22:53 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Subject: Re: Why /64
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <3135C2851EB6764BACEF35D8B495596806FAC25D4E@MOPESMBX01.eu.thmulti.com>
Date: Mon, 28 Oct 2013 10:22:53 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <1E6580AB-7010-4E45-8903-6126E82A9772@steffann.nl>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar>	<526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org> <526E1F5A.2070901@massar.ch> <3135C2851EB6764BACEF35D8B495596806FAC25D4E@MOPESMBX01.eu.thmulti.com>
To: Wuyts Carl <Carl.Wuyts@technicolor.com>
X-Mailer: Apple Mail (2.1816)
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 09:23:30 -0000

Hi Carl,

> +1 for the /64 on the link and /48 for enterprise,=20
>=20
> but "at least" a /56 for home (with /60 too tiny) ??
> Can you elaborate on why you would need more than 4 bits subnets @ =
home?

Today 4 bits can be enough for simple cases with i.e. a home network, a =
guest network and maybe a home-office network. But IPv6 is meant to last =
for some time, and in the (near) future it is not that difficult to see =
networks for lighting and sensors (i.e. 6lowPAN) being added to that. =
And I'm not being very creative right now ;-)  Besides: home users often =
don't understand the different between a wireless router and an access =
point, so they tend to daisy-chain them. In IPv4 this would cause =
multiple layers of NAT, in IPv6 you need more subnets.

PS: Look at DT's plans, they are giving multiple /56s to each home. One =
for best-effort internet access, one for voice, one for streaming =
audio/video, etc. See =
https://ripe67.ripe.net/presentations/131-ripe2-2.pdf. I'm not saying =
this is the way everybody should deploy IPv6, but it is an example of =
using IPv6 address space in a different way.

Cheers,
Sander


From jeroen@massar.ch  Mon Oct 28 02:27:47 2013
Return-Path: <jeroen@massar.ch>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0035A11E816F for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 02:27:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WQ9wgUsL+Vql for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 02:27:45 -0700 (PDT)
Received: from icaras.de.unfix.org (icaras.de.unfix.org [IPv6:2a01:4f8:130:74c1:5054:ff:fec4:f7d4]) by ietfa.amsl.com (Postfix) with ESMTP id 1FF4111E823A for <ipv6@ietf.org>; Mon, 28 Oct 2013 02:27:43 -0700 (PDT)
Received: from kami.ch.unfix.org (kami.ch.unfix.org [IPv6:2001:1620:f42:99:7256:81ff:fea5:2925]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeroen) by icaras.de.unfix.org (Postfix) with ESMTPSA id 952F2801C2A2; Mon, 28 Oct 2013 10:27:35 +0100 (CET)
Message-ID: <526E2E0C.904@massar.ch>
Date: Mon, 28 Oct 2013 10:27:40 +0100
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com> <CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com> <CAKFn1SG1PC_kA-pO5Or8VyeaOzvLfpmQe0LiiYkXU_HzNqGzCQ@mail.gmail.com> <526E250E.5050607@massar.ch> <CAKD1Yr1evbMf1pD4yBrZyvF2XLXGOre3bHDB0gOZTLme7vnh2A@mail.gmail.com> <526E267E.2070705@massar.ch> <CAKD1Yr1K+4H+Gq9dWK-tVJu_3_pw+q7Q1owGz69eg6jy--XN5A@mail.gmail.com> <526E2A56.7070503@massar.ch> <CAKD1Yr3quaLS8zmDuf301MHL_y+uLQg0UfAEU+Kk-hwfv0oqtw@mail.gmail.com>
In-Reply-To: <CAKD1Yr3quaLS8zmDuf301MHL_y+uLQg0UfAEU+Kk-hwfv0oqtw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 09:27:47 -0000

On 2013-10-28 10:22, Lorenzo Colitti wrote:
> On Mon, Oct 28, 2013 at 6:11 PM, Jeroen Massar <jeroen@massar.ch
> <mailto:jeroen@massar.ch>> wrote:
> 
>     > Yes, and I withdrew it. I withdraw it again. Please let's not talk
>     about
>     > it on this thread any more.
> 
>     Can you please provide a link to the message in the archives where you
>     did? As I clearly did not see it.
> 
> 
> http://www.ietf.org/mail-archive/web/ipv6/current/msg19246.html : "sure.
> There are other ways to track people than via IP addresses."

Which shows that you totally missed the point with that statement, and
you surely did not 'withdrew' your point.

See my other messages: IPv6 Privacy addresses are a myth, they do not
work. You can track people even when you just see IP addresses and
ignore the upper layers. The upper layers just make it easier.

Greets,
 Jeroen


From lorenzo@google.com  Mon Oct 28 02:44:01 2013
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C667021F994A for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 02:44:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[AWL=0.068,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iEteUlVbyEwi for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 02:44:01 -0700 (PDT)
Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id E3DC511E8243 for <ipv6@ietf.org>; Mon, 28 Oct 2013 02:43:09 -0700 (PDT)
Received: by mail-ie0-f181.google.com with SMTP id ar20so11068825iec.12 for <ipv6@ietf.org>; Mon, 28 Oct 2013 02:43: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=lQSN7SW+YUn9JUjoPBlDGg/OVrg07N+MNUBQh8Uzcb4=; b=kBus1DN3trM5GN++ZxPrqguEsJPC20E5yJtBZE0sudgG5HteV/tR76PkDy2rAuZ/6f +6dpMZt5YIFbsAPO4GbXbPRa3s9q1i4qo9wx5MWsO94uzJ17zSmiWP+3CU6KUCsQgbhq IvrUref7MWGyFnfXN/NVFJxGxHxuZqalSxUWRJXffQ5O5bQDgEppnNf7O0J0KF001a/F Z+s2FdEf0B19n1yU5PkIbiIK/dZuWFdrbcwELsjp6w/N56aMZCcOaw9/EbJw2pVhsYCO qN9dFNaZ49LG4P04UErUtDLBFVEzKXgmoepSnIIW/YqYWv2hLuc7CZsVt0Xu6mFZDFwP rezg==
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=lQSN7SW+YUn9JUjoPBlDGg/OVrg07N+MNUBQh8Uzcb4=; b=h1/C6PugPxCcsHyD7ej6YTDyMSOEhLiUA9ruGohM2bPZ9H9dqf658qGXJXLIU7EZa8 cobp7CZzlhB+6KXknXWJzhe/VyscEHfjbPsdGv5SxiKfIPMMz02NWa/sYjmaQ1OhYmec VXqQ16ZGTpZ3+b1AD3Jy99cRlGSPiDXg22ibMU/kG+/xDOsbfjN9jf55PESO1srBgBwG DXvr++vZ9kLmxedDEpsl2ehVCN7xOce/OJyXCYLpEEUtQ5aOYw2U9lsND0tRLizt5aN+ rp6RV1vQq1qguklhvVEy3NEMiJwK7/Usn+DE/Uz8ovrKmofKMFStZ4sDYk/Yvoe+a2k6 2Gwg==
X-Gm-Message-State: ALoCoQlIoutcXILEPdNx9KYKiArfQTkT9efBg1T1Aav3PIFTpSyl6OWoLDxqAW3gPcUAq4/quJynoi5ha90cXdCxrQTRu+KBWVSwzz3Dni1BLfhsklsBuWA5cCyjc4Hre6MSLBQ2sfXEFMXQhoiaeIm58RHCb0Wuj5SVD2RtB9O0z2e3L2D8zKKsFwppWxF9NdUTdft0PQN1
X-Received: by 10.50.22.101 with SMTP id c5mr7812228igf.17.1382953388644; Mon, 28 Oct 2013 02:43:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.86.106 with HTTP; Mon, 28 Oct 2013 02:42:47 -0700 (PDT)
In-Reply-To: <526E2E0C.904@massar.ch>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com> <CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com> <CAKFn1SG1PC_kA-pO5Or8VyeaOzvLfpmQe0LiiYkXU_HzNqGzCQ@mail.gmail.com> <526E250E.5050607@massar.ch> <CAKD1Yr1evbMf1pD4yBrZyvF2XLXGOre3bHDB0gOZTLme7vnh2A@mail.gmail.com> <526E267E.2070705@massar.ch> <CAKD1Yr1K+4H+Gq9dWK-tVJu_3_pw+q7Q1owGz69eg6jy--XN5A@mail.gmail.com> <526E2A56.7070503@massar.ch> <CAKD1Yr3quaLS8zmDuf301MHL_y+uLQg0UfAEU+Kk-hwfv0oqtw@mail.gmail.com> <526E2E0C.904@massar.ch>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 28 Oct 2013 18:42:47 +0900
Message-ID: <CAKD1Yr1eSy_DtOmhcH1pYtKeLZi6cHYeDu9MQP8avSZqpHka1g@mail.gmail.com>
Subject: Re: Why /64
To: Jeroen Massar <jeroen@massar.ch>
Content-Type: multipart/alternative; boundary=047d7b10c9cb78dcf804e9c9edb9
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 09:44:02 -0000

--047d7b10c9cb78dcf804e9c9edb9
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Oct 28, 2013 at 6:27 PM, Jeroen Massar <jeroen@massar.ch> wrote:

> See my other messages: IPv6 Privacy addresses are a myth, they do not
>  work. You can track people even when you just see IP addresses and
> ignore the upper layers. The upper layers just make it easier.
>

If you want to discuss this further, please take it to a separate thread.

--047d7b10c9cb78dcf804e9c9edb9
Content-Type: text/html; charset=ISO-8859-1

<div dir="ltr">On Mon, Oct 28, 2013 at 6:27 PM, Jeroen Massar <span dir="ltr">&lt;<a href="mailto:jeroen@massar.ch" target="_blank">jeroen@massar.ch</a>&gt;</span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><span style="color:rgb(34,34,34)">See my other messages: IPv6 Privacy addresses are a myth, they do not</span><br>

</div>
work. You can track people even when you just see IP addresses and<br>
ignore the upper layers. The upper layers just make it easier.<br></blockquote><div><br></div><div>If you want to discuss this further, please take it to a separate thread.</div></div></div></div>

--047d7b10c9cb78dcf804e9c9edb9--

From Carl.Wuyts@technicolor.com  Mon Oct 28 02:44:08 2013
Return-Path: <Carl.Wuyts@technicolor.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CD1321F9D12 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 02:44:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.539
X-Spam-Level: 
X-Spam-Status: No, score=-6.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cKqUz1dehXc6 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 02:44:01 -0700 (PDT)
Received: from na3sys009aog126.obsmtp.com (na3sys009aog126.obsmtp.com [74.125.149.155]) by ietfa.amsl.com (Postfix) with ESMTP id 1D41521F9F84 for <ipv6@ietf.org>; Mon, 28 Oct 2013 02:42:59 -0700 (PDT)
Received: from MOPESEDGE01.eu.thmulti.com ([129.35.174.203]) (using TLSv1) by na3sys009aob126.postini.com ([74.125.148.12]) with SMTP ID DSNKUm4xojDL99t2vGgnoObiyYlFo133XEUW@postini.com; Mon, 28 Oct 2013 02:43:12 PDT
Received: from MOPESMAILHC01.eu.thmulti.com (141.11.100.25) by mail3.technicolor.com (141.11.253.22) with Microsoft SMTP Server (TLS) id 8.3.298.1; Mon, 28 Oct 2013 10:38:32 +0100
Received: from MOPESMBX01.eu.thmulti.com ([169.254.1.71]) by MOPESMAILHC01.eu.thmulti.com ([141.11.100.25]) with mapi; Mon, 28 Oct 2013 10:38:33 +0100
From: Wuyts Carl <Carl.Wuyts@technicolor.com>
To: Sander Steffann <sander@steffann.nl>
Date: Mon, 28 Oct 2013 10:38:31 +0100
Subject: RE: Why /64
Thread-Topic: Why /64
Thread-Index: Ac7Tv1dWghI7+5IHT4uKKWRoRRDQxQAAThJA
Message-ID: <3135C2851EB6764BACEF35D8B495596806FAC25ECF@MOPESMBX01.eu.thmulti.com>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar>	<526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org> <526E1F5A.2070901@massar.ch> <3135C2851EB6764BACEF35D8B495596806FAC25D4E@MOPESMBX01.eu.thmulti.com> <1E6580AB-7010-4E45-8903-6126E82A9772@steffann.nl>
In-Reply-To: <1E6580AB-7010-4E45-8903-6126E82A9772@steffann.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 09:44:08 -0000

Hi Sander,

Don't worry, I agree upon your statements wrt size of prefix, and always re=
commend our customers a /56 (or bigger), and this is for residential CPE, s=
o I'm not really talking about "home-office" networks.
Reality today however says that the majority of users today is using a sing=
le /64 which I believe makes the ISP think on the size of the ia_pd to be u=
sed, hence they might select something smaller, also to get more value in t=
he future for using bigger ones (for more advanced users), so it's sort of =
a trade-off I believe.

Nevertheless, /64, the topic of these mails, on links should be kept imho, =
so not start tweaking them smaller just because some ISPs only handout some=
 smaller ia_pd.  Arin guidelines seems to be in place for /56, should not b=
e a bad idea to have this being used globally, but might not be that easy t=
o enforce.

Regs
Carl

-----Original Message-----
From: Sander Steffann [mailto:sander@steffann.nl]=20
Sent: maandag 28 oktober 2013 10:23
To: Wuyts Carl
Cc: Jeroen Massar; Octavio Alvarez; <ipv6@ietf.org>
Subject: Re: Why /64

Hi Carl,

> +1 for the /64 on the link and /48 for enterprise,=20
>=20
> but "at least" a /56 for home (with /60 too tiny) ??
> Can you elaborate on why you would need more than 4 bits subnets @ home?

Today 4 bits can be enough for simple cases with i.e. a home network, a gue=
st network and maybe a home-office network. But IPv6 is meant to last for s=
ome time, and in the (near) future it is not that difficult to see networks=
 for lighting and sensors (i.e. 6lowPAN) being added to that. And I'm not b=
eing very creative right now ;-)  Besides: home users often don't understan=
d the different between a wireless router and an access point, so they tend=
 to daisy-chain them. In IPv4 this would cause multiple layers of NAT, in I=
Pv6 you need more subnets.

PS: Look at DT's plans, they are giving multiple /56s to each home. One for=
 best-effort internet access, one for voice, one for streaming audio/video,=
 etc. See https://ripe67.ripe.net/presentations/131-ripe2-2.pdf. I'm not sa=
ying this is the way everybody should deploy IPv6, but it is an example of =
using IPv6 address space in a different way.

Cheers,
Sander


From jeroen@massar.ch  Mon Oct 28 02:47:20 2013
Return-Path: <jeroen@massar.ch>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CEAB21F9CE8 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 02:47:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6KCMlXrMpkK1 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 02:47:17 -0700 (PDT)
Received: from icaras.de.unfix.org (icaras.de.unfix.org [IPv6:2a01:4f8:130:74c1:5054:ff:fec4:f7d4]) by ietfa.amsl.com (Postfix) with ESMTP id AF40921F9DBA for <ipv6@ietf.org>; Mon, 28 Oct 2013 02:47:02 -0700 (PDT)
Received: from kami.ch.unfix.org (kami.ch.unfix.org [IPv6:2001:1620:f42:99:7256:81ff:fea5:2925]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeroen) by icaras.de.unfix.org (Postfix) with ESMTPSA id A1FD3801C2A2; Mon, 28 Oct 2013 10:46:54 +0100 (CET)
Message-ID: <526E3294.1040604@massar.ch>
Date: Mon, 28 Oct 2013 10:47:00 +0100
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com> <CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com> <CAKFn1SG1PC_kA-pO5Or8VyeaOzvLfpmQe0LiiYkXU_HzNqGzCQ@mail.gmail.com> <526E250E.5050607@massar.ch> <CAKD1Yr1evbMf1pD4yBrZyvF2XLXGOre3bHDB0gOZTLme7vnh2A@mail.gmail.com> <526E267E.2070705@massar.ch> <CAKD1Yr1K+4H+Gq9dWK-tVJu_3_pw+q7Q1owGz69eg6jy--XN5A@mail.gmail.com> <526E2A56.7070503@massar.ch> <CAKD1Yr3quaLS8zmDuf301MHL_y+uLQg0UfAEU+Kk-hwfv0oqtw@mail.gmail.com> <526E2E0C.904@massar.ch> <CAKD1Yr1eSy_DtOmhcH1pYtKeLZi6cHYeDu9MQP8avSZqpHka1g@mail.gmail.com>
In-Reply-To: <CAKD1Yr1eSy_DtOmhcH1pYtKeLZi6cHYeDu9MQP8avSZqpHka1g@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 09:47:20 -0000

On 2013-10-28 10:42, Lorenzo Colitti wrote:
> On Mon, Oct 28, 2013 at 6:27 PM, Jeroen Massar <jeroen@massar.ch
> <mailto:jeroen@massar.ch>> wrote:
> 
>     See my other messages: IPv6 Privacy addresses are a myth, they do not
>     work. You can track people even when you just see IP addresses and
>     ignore the upper layers. The upper layers just make it easier.
> 
> 
> If you want to discuss this further, please take it to a separate thread.

As I quoted a few messages before you are the one who put it in this thread.

What you are asking is to just forget about it, as you clearly do not
want to accept my point though, I'll do just that, I've made my point
clear enough.

Greets,
 Jeroen


From sander@steffann.nl  Mon Oct 28 02:57:37 2013
Return-Path: <sander@steffann.nl>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B93111E815A for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 02:57:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TYS3OQx9oKHg for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 02:57:33 -0700 (PDT)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:9e0:803::6]) by ietfa.amsl.com (Postfix) with ESMTP id 1709911E8158 for <ipv6@ietf.org>; Mon, 28 Oct 2013 02:57:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id D3A6524; Mon, 28 Oct 2013 10:57:14 +0100 (CET)
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 10024) with ESMTP id eNezMcm0k9Sj; Mon, 28 Oct 2013 10:57:12 +0100 (CET)
Received: from macpro.10ww.steffann.nl (macpro.10ww.steffann.nl [37.77.56.75]) by mail.sintact.nl (Postfix) with ESMTPSA id 902FB16; Mon, 28 Oct 2013 10:57:12 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Subject: Re: Why /64
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <3135C2851EB6764BACEF35D8B495596806FAC25ECF@MOPESMBX01.eu.thmulti.com>
Date: Mon, 28 Oct 2013 10:57:12 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <7DE758C2-CD72-444B-B321-4CEB2066F06D@steffann.nl>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar>	<526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org> <526E1F5A.2070901@massar.ch> <3135C2851EB6764BACEF35D8B495596806FAC25D4E@MOPESMBX01.eu.thmulti.com> <1E6580AB-7010-4E45-8903-6126E82A9772@steffann.nl> <3135C2851EB6764BACEF35D8B495596806FAC25ECF@MOPESMBX01.eu.thmulti.com>
To: Wuyts Carl <Carl.Wuyts@technicolor.com>
X-Mailer: Apple Mail (2.1816)
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 09:57:39 -0000

Hi Carl,

> Don't worry, I agree upon your statements wrt size of prefix, and =
always recommend our customers a /56 (or bigger), and this is for =
residential CPE, so I'm not really talking about "home-office" networks.

Don't underestimate how many people work from home one or two days a =
week :-)

> Reality today however says that the majority of users today is using a =
single /64 which I believe makes the ISP think on the size of the ia_pd =
to be used, hence they might select something smaller, also to get more =
value in the future for using bigger ones (for more advanced users), so =
it's sort of a trade-off I believe.

They can get as many IPv6 addresses as they need (even if giving each =
customer a /48) from the RIPE NCC, so the only reason to do this is to =
promote more expensive subscriptions. This saddens me, but I guess they =
will learn when users start complaining...

> Nevertheless, /64, the topic of these mails, on links should be kept =
imho, so not start tweaking them smaller just because some ISPs only =
handout some smaller ia_pd.  Arin guidelines seems to be in place for =
/56, should not be a bad idea to have this being used globally, but =
might not be that easy to enforce.

Ack!
Sander


From alexandru.petrescu@gmail.com  Mon Oct 28 03:33:05 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE1A421E8093 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 03:33:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.271
X-Spam-Level: 
X-Spam-Status: No, score=-10.271 tagged_above=-999 required=5 tests=[AWL=-0.022, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YA0M-INRaXcH for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 03:32:56 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) by ietfa.amsl.com (Postfix) with ESMTP id 4E10411E8147 for <ipv6@ietf.org>; Mon, 28 Oct 2013 03:32:49 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r9SAWmCx011128 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 28 Oct 2013 11:32:48 +0100
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r9SAWmeX006229; Mon, 28 Oct 2013 11:32:48 +0100 (envelope-from alexandru.petrescu@gmail.com)
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 r9SAWilp009591; Mon, 28 Oct 2013 11:32:48 +0100
Message-ID: <526E3D4D.1060103@gmail.com>
Date: Mon, 28 Oct 2013 11:32:45 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Fernando Gont <fgont@si6networks.com>, ipv6@ietf.org
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com>	<52697C33.7010904@gmail.com> <526AA1A3.2020009@gmail.com> <526AAC0F.8020906@si6networks.com>
In-Reply-To: <526AAC0F.8020906@si6networks.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 10:33:05 -0000

Le 25/10/2013 19:36, Fernando Gont a écrit :
> On 10/25/2013 01:51 PM, Alexandru Petrescu wrote:
>>
>> Not only operationally it may prove difficult to upgrade everything
>> from RFC2464, but all the IPv6-over-foo specs of future deployment
>> may need to accept it as well.
>
> Huh?
>
> Can you elaborate how this affects deployment?

If this spec draft-gont-6man-deprecate-eui64-based-addresses says that
IIDs derived from hardware identifiers are forbidden, and other specs
say that they are mandatory, then there may be a problem.

> Are you suggesting that we ignore well-known problems?

No.

> Are you suggesting that we stick to a feature that allows simple
> location tracking?

Location tracking, as well as other similar characteristics, are bad
when looked at from a prism, and are good when looked at from somewhere
else.

> Or.. maybe you're fine with people deploying IPv6 NAT and that kind
> of middle-box to mitigate this sort of thing?

Yes and no.

IPv6 NAT and NPT are there to be used, and are needed.

No, in that they are needed because more than just its indirect privacy
features.  They are needed also because DHCPv6-PD is not deployed by
cellular operators, and also because SLAAC over Ethernet works with
prefixes length smaller or equal 64.

If you make IIDs which are independent of the hardware ID you'd still
need to make cellular operators deploy DHCPv6-PD and make SLAAC/Ethernet
with longer than 64 prefixes.  Otherwise IPv6 NAT and NPT are still needed.

> An old-timer (who preferred to remain anonymous) just sent me this
> off-list:

Ok.

Alex



From alexandru.petrescu@gmail.com  Mon Oct 28 03:33:48 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD87E21E8093 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 03:33:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.27
X-Spam-Level: 
X-Spam-Status: No, score=-11.27 tagged_above=-999 required=5 tests=[AWL=0.979,  BAYES_00=-2.599, GB_I_INVITATION=-2, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w607M0yChPNy for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 03:33:42 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) by ietfa.amsl.com (Postfix) with ESMTP id AF75A21E8090 for <ipv6@ietf.org>; Mon, 28 Oct 2013 03:33:36 -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 r9SAXVFv030908 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 28 Oct 2013 11:33:31 +0100
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r9SAXVGt006583; Mon, 28 Oct 2013 11:33:31 +0100 (envelope-from alexandru.petrescu@gmail.com)
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 r9SAXVPi010103; Mon, 28 Oct 2013 11:33:31 +0100
Message-ID: <526E3D7B.9030801@gmail.com>
Date: Mon, 28 Oct 2013 11:33:31 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Fernando Gont <fgont@si6networks.com>, ipv6@ietf.org
Subject: Re: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification for draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com>
In-Reply-To: <526AACA5.7090604@si6networks.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 10:33:48 -0000

Le 25/10/2013 19:38, Fernando Gont a écrit :
> On 10/25/2013 01:54 PM, Alexandru Petrescu wrote:
>> If we're again at deprecating things one aspect that I'd really like
>> removed is this 64bit border for SLAAC over Ethernet.
>>
>> One should be able to do SLAAC over Ethernet (and all its backward
>> compatible IEEE links) with Interface Identifiers optionally  shorter
>> than 64bit.
>
> If there's something else that needs to be fixed, then please:
>
> 1) Write an I-D that analyzes the problem, and proposes a workaround, and,

Thanks for the invitation.  Sounds like a good idea to write a problem 
statement about it.  I wouldn't put solutions in the same draft though.

Alex


>
> 2) start a new thread. :-)
>
> Let's keep this thread on-topic. ;-)
>
> Cheers,
>



From kitamura@da.jp.nec.com  Mon Oct 28 03:51:47 2013
Return-Path: <kitamura@da.jp.nec.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F8A811E8174 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 03:51:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.79
X-Spam-Level: 
X-Spam-Status: No, score=-3.79 tagged_above=-999 required=5 tests=[AWL=-0.300,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_53=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FBDjVwZJAEcO for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 03:51:42 -0700 (PDT)
Received: from tyo201.gate.nec.co.jp (TYO201.gate.nec.co.jp [202.32.8.193]) by ietfa.amsl.com (Postfix) with ESMTP id 8238D11E8163 for <ipv6@ietf.org>; Mon, 28 Oct 2013 03:51:38 -0700 (PDT)
Received: from mailgate3.nec.co.jp ([10.7.69.160]) by tyo201.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id r9SApaVS003260;  Mon, 28 Oct 2013 19:51:36 +0900 (JST)
Received: from mailsv.nec.co.jp (imss63.nec.co.jp [10.7.69.158]) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) with ESMTP id r9SApZS02436; Mon, 28 Oct 2013 19:51:35 +0900 (JST)
Received: from mail01b.kamome.nec.co.jp (mail01b.kamome.nec.co.jp [10.25.43.2]) by mailsv.nec.co.jp (8.13.8/8.13.4) with ESMTP id r9SApZBh029147; Mon, 28 Oct 2013 19:51:35 +0900 (JST)
Received: from bpxc99gp.gisp.nec.co.jp ([10.38.151.134] [10.38.151.134]) by mail01b.kamome.nec.co.jp with ESMTP id BT-MMP-200205; Mon, 28 Oct 2013 19:43:07 +0900
Received: from BPXM02GP.gisp.nec.co.jp ([169.254.1.234]) by BPXC06GP.gisp.nec.co.jp ([10.38.151.134]) with mapi id 14.02.0328.011; Mon, 28 Oct 2013 19:43:06 +0900
From: Hiroshi Kitamura <kitamura@da.jp.nec.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: I-D Action: draft-kitamura-ipv6-zoneid-free-01.txt
Thread-Topic: I-D Action: draft-kitamura-ipv6-zoneid-free-01.txt
Thread-Index: Ac7Tym/uXA4zz6CvRyC3ZWnt3R412w==
Date: Mon, 28 Oct 2013 10:43:06 +0000
Message-ID: <8392F9BAC6AD5F47920216A6D7853F7E1D581938@BPXM02GP.gisp.nec.co.jp>
Accept-Language: ja-JP, en-US
Content-Language: ja-JP
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.56.48.28]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: Hiroshi Kitamura <kitamura@da.jp.nec.com>, "Ata, Shingo \(ata@info.eng.osaka-cu.ac.jp\)" <ata@info.eng.osaka-cu.ac.jp>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 10:51:47 -0000

RGVhciBCcmlhbiwNCg0KVGhhbmsgeW91IGZvciB5b3VyIG1haWxzIHdoaWNoIHlvdSBzZW50IHRv
IG1lLg0KTGV0IG1lIGFuc3dlciB5b3VyIG1haWxzIGhlcmUgKGlwdjZAaWV0Zi5vcmcpLCBwbGVh
c2UuDQoNCj4gPiBIaSwNCj4gPg0KPiA+IENhbiB5b3UgZXhwbGFpbiBhIHJlYWwgdXNlIGNhc2Ug
d2hlcmUgYW4gb3JkaW5hcnkgdXNlciBuZWVkcyB0byBjaG9vc2UNCj4gPiBhIFpvbmUgSUQ/IChP
bmUgaW1wb3J0YW50IGFzcGVjdCBvZiB0aGUgSE9NRU5FVCBXRyBpcyB0byBlbnN1cmUgdGhhdA0K
PiA+IHRoZXJlIGlzIGEgbG9jYWwgbmFtZSBzZXJ2aWNlLCB3aGljaCBpcyB2ZXJ5IGltcG9ydGFu
dCBmb3Igb3JkaW5hcnkNCj4gPiB1c2Vycy4pDQo+ID4NCg0KSW4gbXkgSS1EOg0KICAzLjEuIFdo
eSB3ZSBuZWVkIFpvbmUtSUQ/IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAgNg0KICAzLjIuIFdoaWNoIGFjdHVhbCBwcm9jZXNzIHJlcXVpcmVzIFpvbmUtSUQgaW5mb3Jt
YXRpb24/IC4gLiAuIC4gLiAgNg0KICAzLjQuIEhvdyBab25lLUlEIGluZm8uIGRlYWx0IHdpdGgg
aW4gdGhlIGN1cnJlbnQgaW1wbGVtZW50YXRpb25zLiAgNw0KDQogZGVzY3JpYmVzIHJlYWwgdXNl
IGNhc2VzIGFuZCBkZXRhaWxzIG9mIHdoYXQgaGFwcGVucy4NCg0KT24gY3VycmVudCBVbml4L0xp
bnV4IGltcGxlbWVudGF0aW9uOg0KIEZvbGxvd2luZ3MgdHlwZXMgb2YgY29tbWFuZHMgKHdpdGhv
dXQgIiU8Wm9uZS1JRD4iKSB3b3VsZCBOT1Qgd29yay4NCiANCiAgICAgID4gcGluZzYgPExpbmst
TG9jYWxfQWRkcmVzc19BPg0KICAgICAgPiBwaW5nNiA8TGluay1Mb2NhbF9BZGRyZXNzX0I+DQoN
CiAgICAgID4gc3NoICAgPExpbmstTG9jYWxfQWRkcmVzc19BPg0KICAgICAgPiBzc2ggICA8TGlu
ay1Mb2NhbF9BZGRyZXNzX0I+DQoNCiBBYm92ZSBjb21tYW5kcyBzdG9wIHdpdGggZXJyb3IuDQoN
Cg0KT25seSBmb2xsb3dpbmdzIHR5cGVzIG9mIGNvbW1hbmRzICh3aXRoICIlPFpvbmUtSUQ+Iikg
d29yayAvIGFyZSBhbGxvd2VkIHRvIGV4ZWN1dGUuDQoNCiAgICAgID4gcGluZzYgPExpbmstTG9j
YWxfQWRkcmVzc19BPiU8Wm9uZS1JRF9YPg0KICAgICAgPiBwaW5nNiA8TGluay1Mb2NhbF9BZGRy
ZXNzX0I+JTxab25lLUlEX1k+DQoNCiAgICAgID4gc3NoICAgPExpbmstTG9jYWxfQWRkcmVzc19B
PiU8Wm9uZS1JRF9YPg0KICAgICAgPiBzc2ggICA8TGluay1Mb2NhbF9BZGRyZXNzX0I+JTxab25l
LUlEX1k+DQoNClRoZXkgcmVxdWlyZSB0byBvcmRpbmFyeSB1c2VycyB0byBhY2NvbXBhbnkgd2l0
aCAiJTxab25lLUlEPiIgDQoNCg0KUHJvcG9zaW5nIGlkZWEgIlpvbmUtSUQgRnJlZSIgbWFrZXMg
dGhlIGZvbGxvd2luZyBjb21tYW5kcyAod2l0aG91dCAiJTxab25lLUlEPiIpIHBvc3NpYmxlIHRv
IGV4ZWN1dGUuDQoNCiAgICAgID4gcGluZzYgPExpbmstTG9jYWxfQWRkcmVzc19BPg0KICAgICAg
PiBwaW5nNiA8TGluay1Mb2NhbF9BZGRyZXNzX0I+DQoNCiAgICAgID4gc3NoICAgPExpbmstTG9j
YWxfQWRkcmVzc19BPg0KICAgICAgPiBzc2ggICA8TGluay1Mb2NhbF9BZGRyZXNzX0I+DQoNClRo
aXMgZW52aXJvbm1lbnQgbXVzdCBiZSBoYXBweSBmb3Igb3JkaW5hcnkgZW5kIHVzZXJzIHdobyBk
byBub3QgaGF2ZSBlbm91Z2ggbmV0d29yayBrbm93bGVkZ2UuDQoNCg0KDQo+ID4gSSB0aGluayBX
aW5kb3dzIHNpbXBseSBwaWNrcyBhIGRlZmF1bHQgaW50ZXJmYWNlIGlmIHlvdSBkb24ndCBzcGVj
aWZ5DQo+ID4gYSBab25lIElEICoqLg0KDQpJIHVuZGVyc3RhbmQuDQoNCkEgZGVmYXVsdCBpbnRl
cmZhY2UgaWRlYSBpcyBvbmUgb2YgbWV0aG9kcyB0byBhY2hpZXZlIG5vdCB0byBhY2NvbXBhbnkg
d2l0aCAiJTxab25lLUlEPiIuDQoNCg0KPiBJIGhhdmUgY29uZmlybWVkIG9uIG15IGhvbWUgc2V0
dXAgdGhhdCBXaW5kb3dzIGRvZXMgbm90IHJlcXVpcmUgYSBab25lSUQgZXZlbiB3aXRoIHR3byBm
dWxseSBhY3RpdmUgSVB2NiBpbnRlcmZhY2VzLiBJdA0KPiB1c2VkIHRoZSBjb3JyZWN0IGludGVy
ZmFjZSwgc2luY2UgdGhlIHBpbmcgc3VjY2VlZGVkLCBidXQgdGhhdCBtYXkganVzdCBiZSBsdWNr
Lg0KDQpBcyB5b3Ugc2F5ICJtYXkganVzdCBiZSBsdWNrIiwgYSBkZWZhdWx0IGludGVyZmFjZSBp
ZGVhIHdpbGwgYmUgbm90IHdpc2UgZW5vdWdoLg0KDQpJIHRoaW5rIHlvdSBoYXZlIGFscmVhZHkg
bm90aWNlZCB0aGF0IHRoZSBwcm9wb3NpbmcgaWRlYSAiWm9uZS1JRCBGcmVlIiBpcyBtb3JlIHdp
c2UsIGJlY2F1c2UgYXBwcm9wcmlhdGUgaW50ZXJmYWNlIGlzIGxlYXJuZWQgZHluYW1pY2FsbHku
DQoNCj4gPg0KPiA+PiAgICBJbiBvcmRlciB0byBhY2hpZXZlICJab25lLUlEIEZyZWUiIGZ1bmN0
aW9uLCB3ZSBleHRlbmQgdGhpcw0KPiA+PiAgICBvcGVyYXRpb24uICBXZSB3aWxsIHNlbmQgbXVs
dGlwbGUgTlMgcGFja2V0cyB2aWEgYXZhaWxhYmxlIGFsbA0KPiA+PiAgICBpbnRlcmZhY2VzLiBB
bmQgcmVwbGllZCBOQSBwYWNrZXQgdGhhdCBpcyByZWNlaXZlZCB2aWEgZWl0aGVyIG9mDQo+ID4+
ICAgIGludGVyZmFjZXMgdGhhdCBhcmUgdXNlZCBmb3IgdHJhbnNtaXR0aW5nIHRoZSBOUyBwYWNr
ZXRzIGlzIHdhaXRlZA0KPiA+PiAgICBmb3IuIEFmdGVyIGEgTkEgcGFja2V0IGlzIHJlY2VpdmVk
LCBjb3JyZXNwb25kaW5nIG5laWdoYm9yIGNhY2hlDQo+ID4+ICAgIGVudHJ5IHdpbGwgYmUgZmls
bGVkL3VwZGF0ZWQuDQo+ID4NCj4gPiBXaGF0IGhhcHBlbnMgaWYgTkEgcmVwbGllcyBhcmUgcmVj
ZWl2ZWQgb24gbW9yZSB0aGFuIG9uZSBpbnRlcmZhY2U/DQoNCkFmdGVyIG11bHRpcGxlIE5BcyBh
cmUgcmVjZWl2ZWQsIGNvcnJlc3BvbmRpbmcgbmVpZ2hib3IgY2FjaGUgZW50cmllcyB3aWxsIGJl
IGNyZWF0ZWQgKGFzIG5vcm1hbCBORCBpbXBsZW1lbnRhdGlvbiBkb2VzKS4NCg0KVGhlICJab25l
LUlEIEZyZWUiIGlkZWEgcHJvcG9zZXMgdG8gbW9kaWZ5IE5TIHRyYW5zbWl0dGluZyBvbmx5Lg0K
SXQgZG9lcyBOT1QgcHJvcG9zZSB0byBtb2RpZnkgTkEgcmVjZWl2aW5nLg0KDQoNCj4gPiBJdCBp
c24ndCBoYXJkIHRvIGltYWdpbmUgbmV0d29yayBzZXR1cHMgd2hlcmUgZXZlcnkgbGluayBoYXMg
YSBob3N0DQo+ID4gZmU4MDo6MS4NCg0KSSBhZ3JlZS4NCkkgdGhpbmsgeW91ciBxdWVzdGlvbiBp
cyB2ZXJ5IG5hdHVyYWwgcXVlc3Rpb24uDQoNCkZvciBzdWNoIGEgY2FzZSAodGhlIHNhbWUgdmFs
dWUgYWRkcmVzc2VzIGFyZSBsb2NhdGVkIG9uIGRpZmZlcmVudCBhdHRhY2hlZCBuZXR3b3JrcyBh
dCBzYW1lIHRpbWUpLCBpdCBpcyBpbXBvc3NpYmxlIHRvIHNwZWNpZnkgdGhlIGNvcnJlY3QgZGVz
dGluYXRpb24gd2l0aG91dCBhY2NvbXBhbnlpbmcgd2l0aCAiWm9uZS1JRCAoaW50ZXJmYWNlKSIN
CmluZm9ybWF0aW9uLg0KDQpBdCB0aGF0IHNpdHVhdGlvbiwgcGxlYXNlIGFjY29tcGFueSB3aXRo
ICJab25lLUlEIi4NCg0KDQpUaGUgIlpvbmUtSUQgRnJlZSIgaWRlYSBpcyB1cHBlciBjb21wYXRp
YmxlIHdpdGggY3VycmVudCBtZXRob2QuDQpJdCBkb2VzIG5vdCBkZW55IHVzaW5nICJab25lLUlE
Ii4NCg0KDQoNCkluIG15IEktRDoNCiAyLiBQcm9ibGVtIEFuYWx5c2lzIGFuZCBHb2FscyAgLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDMNCg0KIEkgZGVzY3JpYmUgZ29hbHMg
YW5kIHRhcmdldHMgYXMgZm9sbG93cy4NCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0NCiAgIEdvYWxzIG9mIHRoaXMgZG9jdW1lbnQgYXJlIHRvIG1ha2UgZW5kIHVzZXJzIGZy
ZWUgZnJvbSB1c2luZyBab25lLQ0KICAgSUQgYW5kIHRvIHByb3ZpZGUgZW52aXJvbm1lbnQgdGhh
dCB0aGV5IGRvIG5vdCByZXF1aXJlIHRvIGFjY29tcGFueQ0KICAgd2l0aCAlPFpvbmUtSUQ+IHRv
IHRoZWlyIGFwcGxpY2F0aW9ucyBhcmd1bWVudHMuDQoNCiAgIChOb24tVGFyZ2V0czogcGVvcGxl
IHdobyBoYXZlIGVub3VnaCB0ZWNobmljYWwga25vd2xlZGdlIG9mDQogICBuZXR3b3JrcyBhbmQg
ZG8gbm90IGZlZWwgYW55IGRpZmZpY3VsdGllcyB0byBhY2NvbXBhbnkgd2l0aCAlPFpvbmUtDQog
ICBJRD4gaW5mb3JtYXRpb24gYXJlIG5vdCB0YXJnZXQuIEFsc28sIGEgbmV0d29yayBlbnZpcm9u
bWVudCB0aGF0IGlzDQogICB0b28gY29tcGxpY2F0ZWQgdG8gZGVhbCB3aXRoIGZvciBub3JtYWwg
ZW5kIHVzZXJzIGlzIG5vdCB0YXJnZXQuKQ0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLQ0KDQpJIHRoaW5rIHRoaXMgZGVzY3JpcHRpb24gd2lsbCBhbnN3ZXIgeW91ciBxdWVz
dGlvbiBpbmRpcmVjdGx5Lg0KDQpUaGFuayB5b3UgZm9yIHlvdXIgcXVlc3Rpb25zLg0KDQpSZWdh
cmRzLA0KSGlyb3NoaQ0KDQoNCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9t
OiBCcmlhbiBFIENhcnBlbnRlciBbbWFpbHRvOmJyaWFuLmUuY2FycGVudGVyQGdtYWlsLmNvbV0N
Cj4gU2VudDogV2VkbmVzZGF5LCBPY3RvYmVyIDIzLCAyMDEzIDEyOjUwIFBNDQo+IFRvOiBkcmFm
dC1raXRhbXVyYS1pcHY2LXpvbmVpZC1mcmVlQHRvb2xzLmlldGYub3JnDQo+IFN1YmplY3Q6IFJl
OiBJLUQgQWN0aW9uOiBkcmFmdC1raXRhbXVyYS1pcHY2LXpvbmVpZC1mcmVlLTAxLnR4dA0KPiAN
Cj4gSSBoYXZlIGNvbmZpcm1lZCBvbiBteSBob21lIHNldHVwIHRoYXQgV2luZG93cyBkb2VzIG5v
dCByZXF1aXJlIGEgWm9uZUlEIGV2ZW4gd2l0aCB0d28gZnVsbHkgYWN0aXZlIElQdjYgaW50ZXJm
YWNlcy4gSXQNCj4gdXNlZCB0aGUgY29ycmVjdCBpbnRlcmZhY2UsIHNpbmNlIHRoZSBwaW5nIHN1
Y2NlZWRlZCwgYnV0IHRoYXQgbWF5IGp1c3QgYmUgbHVjay4NCj4gDQo+IEV0aGVybmV0IGFkYXB0
ZXIgc2l4eHM6DQo+IA0KPiAgICBDb25uZWN0aW9uLXNwZWNpZmljIEROUyBTdWZmaXggIC4gOg0K
PiAgICBEZXNjcmlwdGlvbiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gOiBUQVAtV2luMzIgQWRhcHRl
ciBWOQ0KPiAgICBQaHlzaWNhbCBBZGRyZXNzLiAuIC4gLiAuIC4gLiAuIC4gOiAwMC1GRi01OS04
RC0zOS1FNg0KPiAgICBESENQIEVuYWJsZWQuIC4gLiAuIC4gLiAuIC4gLiAuIC4gOiBZZXMNCj4g
ICAgQXV0b2NvbmZpZ3VyYXRpb24gRW5hYmxlZCAuIC4gLiAuIDogWWVzDQo+ICAgIElQdjYgQWRk
cmVzcy4gLiAuIC4gLiAuIC4gLiAuIC4gLiA6IDIwMDE6NDQyODoyMDA6MTJjOjoyKFByZWZlcnJl
ZCkNCj4gICAgSVB2NiBBZGRyZXNzLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDogMmEwMTozNDg6Njo1
ZDA6OjIoUHJlZmVycmVkKQ0KPiAgICBMaW5rLWxvY2FsIElQdjYgQWRkcmVzcyAuIC4gLiAuIC4g
OiBmZTgwOjo4MWEzOmM0ZDQ6YmNkYzo0ZDM1JTE3KFByZWZlcnJlZCkNCj4gICAgQXV0b2NvbmZp
Z3VyYXRpb24gSVB2NCBBZGRyZXNzLiAuIDogMTY5LjI1NC43Ny41MyhQcmVmZXJyZWQpDQo+ICAg
IFN1Ym5ldCBNYXNrIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiA6IDI1NS4yNTUuMC4wDQo+ICAgIERl
ZmF1bHQgR2F0ZXdheSAuIC4gLiAuIC4gLiAuIC4gLiA6IDJhMDE6MzQ4OjY6NWQwOjoxDQo+ICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIDIwMDE6NDQyODoyMDA6MTJjOjox
DQo+ICAgIERIQ1B2NiBJQUlEIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiA6IDYwNDA0NTE0NQ0KPiAg
ICBESENQdjYgQ2xpZW50IERVSUQuIC4gLiAuIC4gLiAuIC4gOiAwMC0wMS0wMC0wMS0xOC0zQi1B
Mi02OS1FOC0wMy05QS0zQy02Ny03QQ0KPiAgICBETlMgU2VydmVycyAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gOiAyMDAxOjQ3MDoyMDo6Mg0KPiAgICBOZXRCSU9TIG92ZXIgVGNwaXAuIC4gLiAuIC4g
LiAuIC4gOiBFbmFibGVkDQo+IA0KPiBXaXJlbGVzcyBMQU4gYWRhcHRlciBXaXJlbGVzcyBOZXR3
b3JrIENvbm5lY3Rpb246DQo+IA0KPiAgICBDb25uZWN0aW9uLXNwZWNpZmljIEROUyBTdWZmaXgg
IC4gOiBmcml0ei5ib3gNCj4gICAgRGVzY3JpcHRpb24gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDog
SW50ZWwoUikgQ2VudHJpbm8oUikgQWR2YW5jZWQtTiA2MjMwDQo+ICAgIFBoeXNpY2FsIEFkZHJl
c3MuIC4gLiAuIC4gLiAuIC4gLiA6IDg4LTUzLTJFLUI5LTU2LTIyDQo+ICAgIERIQ1AgRW5hYmxl
ZC4gLiAuIC4gLiAuIC4gLiAuIC4gLiA6IFllcw0KPiAgICBBdXRvY29uZmlndXJhdGlvbiBFbmFi
bGVkIC4gLiAuIC4gOiBZZXMNCj4gICAgSVB2NiBBZGRyZXNzLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IDogMjQwNjplMDAwOmUwMGE6MToyOGNjOmRjNGM6OTcwMzo2NzgxKFByZWZlcnJlZCkNCj4gICAg
VGVtcG9yYXJ5IElQdjYgQWRkcmVzcy4gLiAuIC4gLiAuIDogMjQwNjplMDAwOmUwMGE6MTpmODAx
OjM0YWM6YWUwNzpkYTc0KFByZWZlcnJlZCkNCj4gICAgTGluay1sb2NhbCBJUHY2IEFkZHJlc3Mg
LiAuIC4gLiAuIDogZmU4MDo6MjhjYzpkYzRjOjk3MDM6Njc4MSUxMihQcmVmZXJyZWQpDQo+ICAg
IElQdjQgQWRkcmVzcy4gLiAuIC4gLiAuIC4gLiAuIC4gLiA6IDE5Mi4xNjguMTc4LjIwKFByZWZl
cnJlZCkNCj4gICAgU3VibmV0IE1hc2sgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDogMjU1LjI1NS4y
NTUuMA0KPiAgICBMZWFzZSBPYnRhaW5lZC4gLiAuIC4gLiAuIC4gLiAuIC4gOiAyMyBPY3RvYmVy
IDIwMTMgMTY6Mjk6MTMNCj4gICAgTGVhc2UgRXhwaXJlcyAuIC4gLiAuIC4gLiAuIC4gLiAuIDog
MDIgTm92ZW1iZXIgMjAxMyAxNjoyOToxMw0KPiAgICBEZWZhdWx0IEdhdGV3YXkgLiAuIC4gLiAu
IC4gLiAuIC4gOiBmZTgwOjpiZTA1OjQzZmY6ZmU4ZTpjZTM5JTEyDQo+ICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIDE5Mi4xNjguMTc4LjENCj4gICAgREhDUCBTZXJ2ZXIg
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIDogMTkyLjE2OC4xNzguMQ0KPiAgICBESENQdjYgSUFJRCAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gOiAzMTA5MjQwNzgNCj4gICAgREhDUHY2IENsaWVudCBEVUlE
LiAuIC4gLiAuIC4gLiAuIDogMDAtMDEtMDAtMDEtMTgtM0ItQTItNjktRTgtMDMtOUEtM0MtNjct
N0ENCj4gICAgRE5TIFNlcnZlcnMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDogZmQwMDo6YmUwNTo0
M2ZmOmZlOGU6Y2UzOQ0KPiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAx
OTIuMTY4LjE3OC4xDQo+ICAgIE5ldEJJT1Mgb3ZlciBUY3BpcC4gLiAuIC4gLiAuIC4gLiA6IEVu
YWJsZWQNCj4gDQo+IA0KPiBDOlx3aW5kb3dzXHN5c3RlbTMyPnBpbmcgZmU4MDo6YmUwNTo0M2Zm
OmZlOGU6Y2UzOQ0KPiANCj4gUGluZ2luZyBmZTgwOjpiZTA1OjQzZmY6ZmU4ZTpjZTM5IHdpdGgg
MzIgYnl0ZXMgb2YgZGF0YToNCj4gUmVwbHkgZnJvbSBmZTgwOjpiZTA1OjQzZmY6ZmU4ZTpjZTM5
OiB0aW1lPTFtcyBSZXBseSBmcm9tIGZlODA6OmJlMDU6NDNmZjpmZThlOmNlMzk6IHRpbWU9MW1z
IFJlcGx5IGZyb20NCj4gZmU4MDo6YmUwNTo0M2ZmOmZlOGU6Y2UzOTogdGltZT0xbXMgUmVwbHkg
ZnJvbSBmZTgwOjpiZTA1OjQzZmY6ZmU4ZTpjZTM5OiB0aW1lPTFtcw0KPiANCj4gUGluZyBzdGF0
aXN0aWNzIGZvciBmZTgwOjpiZTA1OjQzZmY6ZmU4ZTpjZTM5Og0KPiAgICAgUGFja2V0czogU2Vu
dCA9IDQsIFJlY2VpdmVkID0gNCwgTG9zdCA9IDAgKDAlIGxvc3MpLCBBcHByb3hpbWF0ZSByb3Vu
ZCB0cmlwIHRpbWVzIGluIG1pbGxpLXNlY29uZHM6DQo+ICAgICBNaW5pbXVtID0gMW1zLCBNYXhp
bXVtID0gMW1zLCBBdmVyYWdlID0gMW1zDQo+IA0KPiAlIHRoaXMgb25lIGlzIGEgbG9vcGJhY2s6
DQo+IA0KPiBDOlx3aW5kb3dzXHN5c3RlbTMyPnBpbmcgZmU4MDo6ODFhMzpjNGQ0OmJjZGM6NGQz
NQ0KPiANCj4gUGluZ2luZyBmZTgwOjo4MWEzOmM0ZDQ6YmNkYzo0ZDM1IHdpdGggMzIgYnl0ZXMg
b2YgZGF0YToNCj4gUmVwbHkgZnJvbSBmZTgwOjo4MWEzOmM0ZDQ6YmNkYzo0ZDM1OiB0aW1lPDFt
cyBSZXBseSBmcm9tIGZlODA6OjgxYTM6YzRkNDpiY2RjOjRkMzU6IHRpbWU8MW1zIFJlcGx5IGZy
b20NCj4gZmU4MDo6ODFhMzpjNGQ0OmJjZGM6NGQzNTogdGltZTwxbXMgUmVwbHkgZnJvbSBmZTgw
Ojo4MWEzOmM0ZDQ6YmNkYzo0ZDM1OiB0aW1lPDFtcw0KPiANCj4gUGluZyBzdGF0aXN0aWNzIGZv
ciBmZTgwOjo4MWEzOmM0ZDQ6YmNkYzo0ZDM1Og0KPiAgICAgUGFja2V0czogU2VudCA9IDQsIFJl
Y2VpdmVkID0gNCwgTG9zdCA9IDAgKDAlIGxvc3MpLCBBcHByb3hpbWF0ZSByb3VuZCB0cmlwIHRp
bWVzIGluIG1pbGxpLXNlY29uZHM6DQo+ICAgICBNaW5pbXVtID0gMG1zLCBNYXhpbXVtID0gMG1z
LCBBdmVyYWdlID0gMG1zDQo+IA0KPiBSZWdhcmRzDQo+ICAgIEJyaWFuIENhcnBlbnRlcg0KPiAN
Cj4gT24gMjMvMTAvMjAxMyAxNDoyMywgQnJpYW4gRSBDYXJwZW50ZXIgd3JvdGU6DQo+ID4gSGks
DQo+ID4NCj4gPiBDYW4geW91IGV4cGxhaW4gYSByZWFsIHVzZSBjYXNlIHdoZXJlIGFuIG9yZGlu
YXJ5IHVzZXIgbmVlZHMgdG8gY2hvb3NlDQo+ID4gYSBab25lIElEPyAoT25lIGltcG9ydGFudCBh
c3BlY3Qgb2YgdGhlIEhPTUVORVQgV0cgaXMgdG8gZW5zdXJlIHRoYXQNCj4gPiB0aGVyZSBpcyBh
IGxvY2FsIG5hbWUgc2VydmljZSwgd2hpY2ggaXMgdmVyeSBpbXBvcnRhbnQgZm9yIG9yZGluYXJ5
DQo+ID4gdXNlcnMuKQ0KPiA+DQo+ID4gSSB0aGluayBXaW5kb3dzIHNpbXBseSBwaWNrcyBhIGRl
ZmF1bHQgaW50ZXJmYWNlIGlmIHlvdSBkb24ndCBzcGVjaWZ5DQo+ID4gYSBab25lIElEICoqLg0K
PiA+DQo+ID4+ICAgIEluIG9yZGVyIHRvIGFjaGlldmUgIlpvbmUtSUQgRnJlZSIgZnVuY3Rpb24s
IHdlIGV4dGVuZCB0aGlzDQo+ID4+ICAgIG9wZXJhdGlvbi4gIFdlIHdpbGwgc2VuZCBtdWx0aXBs
ZSBOUyBwYWNrZXRzIHZpYSBhdmFpbGFibGUgYWxsDQo+ID4+ICAgIGludGVyZmFjZXMuIEFuZCBy
ZXBsaWVkIE5BIHBhY2tldCB0aGF0IGlzIHJlY2VpdmVkIHZpYSBlaXRoZXIgb2YNCj4gPj4gICAg
aW50ZXJmYWNlcyB0aGF0IGFyZSB1c2VkIGZvciB0cmFuc21pdHRpbmcgdGhlIE5TIHBhY2tldHMg
aXMgd2FpdGVkDQo+ID4+ICAgIGZvci4gQWZ0ZXIgYSBOQSBwYWNrZXQgaXMgcmVjZWl2ZWQsIGNv
cnJlc3BvbmRpbmcgbmVpZ2hib3IgY2FjaGUNCj4gPj4gICAgZW50cnkgd2lsbCBiZSBmaWxsZWQv
dXBkYXRlZC4NCj4gPg0KPiA+IFdoYXQgaGFwcGVucyBpZiBOQSByZXBsaWVzIGFyZSByZWNlaXZl
ZCBvbiBtb3JlIHRoYW4gb25lIGludGVyZmFjZT8NCj4gPg0KPiA+IEl0IGlzbid0IGhhcmQgdG8g
aW1hZ2luZSBuZXR3b3JrIHNldHVwcyB3aGVyZSBldmVyeSBsaW5rIGhhcyBhIGhvc3QNCj4gPiBm
ZTgwOjoxLg0KPiA+DQo+ID4gICAgQnJpYW4NCj4gPg0KPiA+ICoqDQo+ID4gQzpcd2luZG93c1xz
eXN0ZW0zMj5waW5nIGZlODA6OjENCj4gPg0KPiA+IFBpbmdpbmcgZmU4MDo6MSB3aXRoIDMyIGJ5
dGVzIG9mIGRhdGE6DQo+ID4gRGVzdGluYXRpb24gaG9zdCB1bnJlYWNoYWJsZS4NCj4gPiBEZXN0
aW5hdGlvbiBob3N0IHVucmVhY2hhYmxlLg0KPiA+IFJlcXVlc3QgdGltZWQgb3V0Lg0KPiA+IFJl
cXVlc3QgdGltZWQgb3V0Lg0KPiA+DQo+ID4gUGluZyBzdGF0aXN0aWNzIGZvciBmZTgwOjoxOg0K
PiA+ICAgICBQYWNrZXRzOiBTZW50ID0gNCwgUmVjZWl2ZWQgPSAwLCBMb3N0ID0gNCAoMTAwJSBs
b3NzKQ0KPiA+DQo=

From alexandru.petrescu@gmail.com  Mon Oct 28 03:52:02 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F330021E8095 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 03:52:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level: 
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[AWL=-0.050, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zr4DQ+kjKU6q for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 03:51:55 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) by ietfa.amsl.com (Postfix) with ESMTP id 3678621E8093 for <ipv6@ietf.org>; Mon, 28 Oct 2013 03:51:52 -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 r9SApi4C017716 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 28 Oct 2013 11:51:44 +0100
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r9SAphn4015642; Mon, 28 Oct 2013 11:51:43 +0100 (envelope-from alexandru.petrescu@gmail.com)
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 r9SApdm4023822; Mon, 28 Oct 2013 11:51:43 +0100
Message-ID: <526E41BC.3080303@gmail.com>
Date: Mon, 28 Oct 2013 11:51:40 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Ray Hunter <v6ops@globis.net>, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CF079.7030804@globis.net>
In-Reply-To: <526CF079.7030804@globis.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Fernando Gont <fgont@si6networks.com>, Tim Chown <tjc@ecs.soton.ac.uk>, "<ipv6@ietf.org>" <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 10:52:02 -0000

Le 27/10/2013 11:52, Ray Hunter a écrit :
> Lorenzo Colitti wrote:
>> On Sat, Oct 26, 2013 at 5:42 PM, Fred Baker (fred) <fred@cisco.com>
>> wrote:
>>
>>>> Is this the sole reason for requiring subnets to be a /64?
>>> It was the driver for the change from RFC 1884's /80 (with a 48
>>> bit MAC in the IID) to RFC 2373's /64 (with an EUI-64). I would
>>> think that any argument today about the /64 would be about
>>> inertia if not the EUI-64.
>>>
>>
>> I think the split /64 extremely useful because it provides a
>> minimum size assignment that makes autoconfiguration easy, allows
>> privacy, and gives users the capability to number multiple
>> applications or multiple devices without having to use NAT.
>>
>> I have personally had more than one conversation with operators who
>> cannot see why they would ever want to give a user more than one
>> IPv6 address, because a) that's what they do in IPv4, and b) a /64
>> is a waste of space. Mobile operators seem particularly prone to
>> this line of reasoning. Telling them that there's plenty of space
>> to give every device a /64, or that their service is better if
>> users are allowed more than a /64 for privacy reasons, or that it
>> allows users to connect multiple devices, etc. has no effect.
>> Saying "it's specified in the standards and some implementations
>> might not work if you don't do it" has proven to be a much better
>> argument so far. Often those same operators then come to appreciate
>> the flexibility once they have deployed using /64 or larger and see
>> how it makes things better and easier.
>>
>> It's true that some operators can decide to use only DHCPv6 and
>> hand out /128s today, but since some platforms don't support
>> DHCPv6, that decision has compatibility consequences.
>>
>> If we ditch the one-size-fits all subnet size and leave the subnet
>> size up to the operator, it's virtually certain that we will end up
>> with some deployments that hand out /128s. That makes IPv4-style
>> NAT virtually inevitable, because users will want to connect more
>> than one device regardless of what the operator wants them to do.
>> Since apps have to adapt to the lowest-common denominator
>> connection, there's a good chance that apps will have to keep
>> IPv4-style NAT traversal mechanisms around forever. I think that's
>> a fundamentally bad deal, because there's no real reason to employ
>> address sharing if you have enough addresses; the side-effects of
>> NAT that people seem to like (e.g., security) come from stateful
>> inpection, not from the translation itself.
>>
>> On the other hand, if we do keep a one-size-fits-all subnet size,
>> then I think /64 is the best choice, not just for backwards
>> compatibility reasons, but for lots of other reasons such as
>> because it splits the address in two halves that are natural
>> machine integer sizes, provides enough space to protect against the
>> birthday paradox, and so on.
>>
>> Cheers, Lorenzo
>>
> If I read the above, you seem to be arguing that dropping fixed /64
> would be a bad thing because operators will use this as an
> opportunity to limit their customers to a single IPv6 address, and
> yet simultaneously you seem to be arguing that maintaing a fixed /64
> is a good thing even though it limits customers to a single subnet.
>
> Do I understand you correctly? The logic doesn't seem very
> self-consistent to me.
>
> Me? I believe in CIDR.

The IPv4's CIDR concept (route based on bitwise borders, instead of
8byte) seems to me a good clue for the discussion about the fix 64bit
limit in IPv6.

Alex

>



From alexandru.petrescu@gmail.com  Mon Oct 28 03:54:03 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15A9C21F9CAE for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 03:54:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.298
X-Spam-Level: 
X-Spam-Status: No, score=-10.298 tagged_above=-999 required=5 tests=[AWL=-0.049, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2cX1RJTxSGgB for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 03:53:56 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) by ietfa.amsl.com (Postfix) with ESMTP id 1472211E8174 for <ipv6@ietf.org>; Mon, 28 Oct 2013 03:53:52 -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 r9SArqd2019473 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ipv6@ietf.org>; Mon, 28 Oct 2013 11:53:52 +0100
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r9SArpbS016534 for <ipv6@ietf.org>; Mon, 28 Oct 2013 11:53:52 +0100 (envelope-from alexandru.petrescu@gmail.com)
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 r9SArpBg025191 for <ipv6@ietf.org>; Mon, 28 Oct 2013 11:53:51 +0100
Message-ID: <526E423F.7010307@gmail.com>
Date: Mon, 28 Oct 2013 11:53:51 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: Why /64 [was Deprecating EUI-64 Based IPv6 Addresses]
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar>	<526AA24F.6010609@gmail.com>	<526AACA5.7090604@si6networks.com>	<E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<526B0A30.9060600@gmail.com>	<526B0E15.8080602@si6networks.com>	<F6264230-19EB-4FEC-910C-C86F14C28A83@ecs.soton.ac.uk>	<EMEW3|d9e74aba9561d767d4403c2b6597aed6p9P8h103tjc|ecs.soton.ac.uk|F6264230-19EB-4FEC-910C-C86F14C28A83@ecs.soton.ac.uk> <526D24F2.7030701@gont.com.ar>
In-Reply-To: <526D24F2.7030701@gont.com.ar>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 10:54:03 -0000

Le 27/10/2013 15:36, Fernando Gont a écrit :
> On 10/26/2013 03:41 AM, Tim Chown wrote:
>>>
>>> That's why I think that relaxing the /64 requirement is a whole
>>> different game. -- If anything, a first step would be to relax this
>>> for hosts, and *at some point in the future*, relax it for routers
>>> -- otherwise, a "legacy" host that expects a /64 might break or
>>> fail to do SLAAC if an updated router where to advertise, say, a
>>> /80.
>>>
>>> OTOH, deprecating Modified EUI-64 is a local policy which is
>>> incrementally-deployable.
>>
>> Well yes, there’s obviously a large deployed code base where /64 has
>> been assumed. And changing that assumption may simply not be
>> practical.
>
> I'm not sure about whether that's practical or not.. but just wanted to
> note that it's a different game.
>
>
>
>> But… for example, some people who were concerned over the ND cache
>> problem have run with /120 and DHCPv6.
>
> Those should call a lemon a lemon, and ask their vendors to fix their ND
> implementations ;-).
>
>
>> I’m not advocating that.
>> Indeed the homenet arch text specifically mentions not using such
>> “tricks" where the ISP only allocates one /64 to a home which
>> requires multiple subnets.
>
> So.. what do ou do in that case... IPv6 NAT?

There is also this NPT... and I wonder whether it has this 64bit limit 
or not.

Alex

>
>
>
>> I’m just suggesting it would be interesting to spend a little time to
>> figure out where the /64 really is “burnt in” so that, if there were
>> a desire to explore proposing a /80 or /96 or whatever for a future
>> SLAAC, we would have a clearer idea of what the implications would
>> be, and how/if an incremental progression to variable length SLAAC
>> could be facilitated.
>
> Agreed.
>
> Thanks,
>



From alexandru.petrescu@gmail.com  Mon Oct 28 04:01:14 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE5E911E818F for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 04:01:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.296
X-Spam-Level: 
X-Spam-Status: No, score=-10.296 tagged_above=-999 required=5 tests=[AWL=-0.047, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wYBL2XUFmj65 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 04:01:08 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) by ietfa.amsl.com (Postfix) with ESMTP id 97E9811E8175 for <ipv6@ietf.org>; Mon, 28 Oct 2013 04:01:05 -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 r9SB0uDR010128 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 28 Oct 2013 12:00:56 +0100
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r9SB0uL9019526; Mon, 28 Oct 2013 12:00:56 +0100 (envelope-from alexandru.petrescu@gmail.com)
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 r9SB0tte029540; Mon, 28 Oct 2013 12:00:55 +0100
Message-ID: <526E43E8.3080601@gmail.com>
Date: Mon, 28 Oct 2013 12:00:56 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Octavio Alvarez <alvarezp@alvarezp.ods.org>, Jeroen Massar <jeroen@massar.ch>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com>	<526AACA5.7090604@si6networks.com>	<E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<526AC8AF.4060608@si6networks.com>	<8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org>
In-Reply-To: <526D3706.5070409@alvarezp.ods.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Fernando Gont <fgont@si6networks.com>, Tim Chown <tjc@ecs.soton.ac.uk>, "<ipv6@ietf.org>" <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 11:01:14 -0000

Le 27/10/2013 16:53, Octavio Alvarez a écrit :
> On 10/27/2013 02:26 AM, Jeroen Massar wrote:
>>> allows privacy,
>>
>> IMHO big nonsense. The company (amongst many others!) you work for uses
>> amongst others cookies to track their people, and if they really bother
>> could even use natural language structure, search query types, and other
>> behavior for breaking this 'privacy'. Also note that even if the last
>> 64bits are random, your company should be more than able to say "oh,
>> there are typically X users in there, it likely is Y"...
>
> Then why deprecate EUI-64?

I think there is a problem in naming that draft.

I think the intention of it is not to deprecate EUI-64 altogether.  If 
I'm not wrong EUI-64 is an IEEE concept that IETF reuses, and thus 6man 
wouldn't have the prerogatives to 'deprecate EUI-64'.

Second, reading through that draft it seemed to me it intended to 
deprecate the use of a hardware address as input into an IP address 
formation mechanism.

I think the draft _would_ allow to devise an IP address generation 
mechanism using an EUI-64 formed from something else which is not a 
hardware address.

But this is the other thread.

Alex


>
>
>



From alexandru.petrescu@gmail.com  Mon Oct 28 04:13:44 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4CB621E8056 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 04:13:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.295
X-Spam-Level: 
X-Spam-Status: No, score=-10.295 tagged_above=-999 required=5 tests=[AWL=-0.046, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IC52T6ganZHA for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 04:13:39 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) by ietfa.amsl.com (Postfix) with ESMTP id 8C88311E811D for <ipv6@ietf.org>; Mon, 28 Oct 2013 04:13:38 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r9SBDbUg029550 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ipv6@ietf.org>; Mon, 28 Oct 2013 12:13:37 +0100
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r9SBDbeV024086 for <ipv6@ietf.org>; Mon, 28 Oct 2013 12:13:37 +0100 (envelope-from alexandru.petrescu@gmail.com)
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 r9SBDWjK004113 for <ipv6@ietf.org>; Mon, 28 Oct 2013 12:13:36 +0100
Message-ID: <526E46DD.9000308@gmail.com>
Date: Mon, 28 Oct 2013 12:13:33 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar>	<526AA24F.6010609@gmail.com>	<526AACA5.7090604@si6networks.com>	<E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<526AC8AF.4060608@si6networks.com>	<8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com>	<CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com>	<526CDC59.4070204@massar.ch>	<CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com>	<CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com>	<526D0F47.5040803@massar.ch>	<CALOgxGaoB_u+br5bpyVu-A0w8vD=QjYkrzaPqYrrhtPK=z6BEw@mail.gmail.com> <526E21C5.9080707@massar.ch>
In-Reply-To: <526E21C5.9080707@massar.ch>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 11:13:44 -0000

Le 28/10/2013 09:35, Jeroen Massar a écrit :
> On 2013-10-27 20:04, TJ wrote:
>>>>> IMHO big nonsense. The company (amongst many others!) you
>>>>> work for
>>> uses amongst others cookies to track their people,
>>>>
>>>> Not sure we want to get into that argument here, but
>>>
>>> I _don't_ want to get into it here but I want to briefly support
>> Lorenzo
>>> on privacy.  Privacy through controlling tracking of an IP
>>> address is very different in mechanism and result from higher
>>> layer end-to-end privacy.
>>
>>
>> First off, ++1 to Lorenzo on all counts (and Scott, Karl).
>
> You can +1 without facts or any backing details, but the fun thing
> is, it is no difference at all: privacy addresses do not make you
> "private" in any way or form.

I tend to agree.

On one hand, privacy extensions to SLAAC is one little step towards
having just a little more privacy possible, as opposed to not using
privacy extensions.

But there are many aspects than just the IP address, visible in even the
simplest wireshark dump which when correlated reveal a surprising number
of things some may consider deeply private.

Even the time correlation of presence/absence of traffic can be a guide
about someone's habits. It can become as insane as thinking that only 
turning everything off forever could offer some privacy.  An hypothesis 
contradictory to the very essence of communication.

Alex

>
>
> The only thing higher levels gives the adversary is a easier
> detection and correlation. But unless you have exactly the same
> packet signature and you are hitting the same sites as other people
> in your /64 or /48 you are unique.
>
> Please note that a IPv6 Privacy Address is for a period of time, not
> per application (at least I have not seen an OS do that yet, it
> could, but they do not).
>
> As such, when your HTTP browser goes to a site, that IP address is
> identified as you; then anything else goes to another site, and
> voila, they know that that connection is also related to you. Then
> your privacy time window expires, you connect to that second site
> again, which is not HTTP, but as you have been there just a bit ago,
> there is a high chance that that is still you.
>
>> It does not matter if you have 1 IPv4 address with 2000 people
>> behind it, or 1 /48 with 2000 people behind it.
>>
>> The algorithms to de-anonimize and differentiate between the real
>> hosts behind them exist.
>>
>> Cookies are one way to do that, complete browser profiles or other
>>  differences in the client, be that the tcp stack level another.
>> For other protocols it is all much easier as they are typically
>> already authenticated anyway or have other bits.
>>
>>
>>
>> Having said that, FWIW - I partially disagree with Jeron here - it
>> does matter.
>
> With what exact part do you disagree and what part does matter?
>
>
>> A user can have browser extensions, multiple browsers (or mutliple
>> VMs with different OSes) and have a fairly good level of privacy
>> if so desires - as long as the underlying L3 provisioned does not
>> prevent it.  Is may not be exactly mainstream / commonplace, but
>> not uncommon enough to ignore (IMHO) either.
>
> Even though that would give you separate addresses and would
> initially give that user separate identities that are being tracked,
> that user is still coming out of the same /64 or /48.
>
> Thus on the IP level indeed it initially looks like multiple users.
> But as various organizations are pretty good at estimating amount of
> users in a location, they can easily guess that it is the same
> person anyway.
>
>
> I'll state again: if you want privacy use a mixnet, eg Tor. (and
> even then you are exposing all your random bits, thus beware what
> protocols and tools you use)
>
> Greets, Jeroen
>
> --------------------------------------------------------------------
>  IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>



From alexandru.petrescu@gmail.com  Mon Oct 28 04:18:38 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5366F11E816D for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 04:18:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.294
X-Spam-Level: 
X-Spam-Status: No, score=-10.294 tagged_above=-999 required=5 tests=[AWL=-0.045, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9ZebybwktxaY for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 04:18:33 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) by ietfa.amsl.com (Postfix) with ESMTP id 7548D11E81E3 for <ipv6@ietf.org>; Mon, 28 Oct 2013 04:18:30 -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 r9SBIRTU016868 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ipv6@ietf.org>; Mon, 28 Oct 2013 12:18:27 +0100
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r9SBIR63025610 for <ipv6@ietf.org>; Mon, 28 Oct 2013 12:18:27 +0100 (envelope-from alexandru.petrescu@gmail.com)
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 r9SBIQXv006665 for <ipv6@ietf.org>; Mon, 28 Oct 2013 12:18:27 +0100
Message-ID: <526E4803.8020808@gmail.com>
Date: Mon, 28 Oct 2013 12:18:27 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar>	<526AA24F.6010609@gmail.com>	<526AACA5.7090604@si6networks.com>	<E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<526AC8AF.4060608@si6networks.com>	<8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com>	<CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com>	<526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org>	<526E1F5A.2070901@massar.ch>	<3135C2851EB6764BACEF35D8B495596806FAC25D4E@MOPESMBX01.eu.thmulti.com> <1E6580AB-7010-4E45-8903-6126E82A9772@steffann.nl>
In-Reply-To: <1E6580AB-7010-4E45-8903-6126E82A9772@steffann.nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 11:18:38 -0000

Le 28/10/2013 10:22, Sander Steffann a écrit :
> Hi Carl,
>
>> +1 for the /64 on the link and /48 for enterprise,
>>
>> but "at least" a /56 for home (with /60 too tiny) ?? Can you
>> elaborate on why you would need more than 4 bits subnets @ home?
>
> Today 4 bits can be enough for simple cases with i.e. a home
> network, a guest network and maybe a home-office network. But IPv6 is
> meant to last for some time, and in the (near) future it is not that
> difficult to see networks for lighting and sensors (i.e. 6lowPAN)
> being added to that.

I agree.

And I would add another aspect.  One could hardly imagine that a single
subnet (any subnet) could hold together 2^64 nodes.  That is a matter of
link-layer technology.  I think not even the largest single subnet
switch/vlan-based office networks or datacenter would approach that number.

(a single IEEE subnet is one where link-scope link-layer multicast works
across, and IP datagrams are not decremented their Hop Limit when
transmitted through).

Alex

> And I'm not being very creative right now ;-)  Besides: home users
> often don't understand the different between a wireless router and an
> access point, so they tend to daisy-chain them. In IPv4 this would
> cause multiple layers of NAT, in IPv6 you need more subnets.
>
> PS: Look at DT's plans, they are giving multiple /56s to each home.
> One for best-effort internet access, one for voice, one for
> streaming audio/video, etc. See
> https://ripe67.ripe.net/presentations/131-ripe2-2.pdf. I'm not
> saying this is the way everybody should deploy IPv6, but it is an
> example of using IPv6 address space in a different way.
>
> Cheers, Sander
>
> --------------------------------------------------------------------
>  IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>



From lorenzo@google.com  Mon Oct 28 05:25:15 2013
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0671621E8092 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 05:25:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level: 
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[AWL=0.065,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hHGo22na6zP7 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 05:25:10 -0700 (PDT)
Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 957D821E8093 for <ipv6@ietf.org>; Mon, 28 Oct 2013 05:25:03 -0700 (PDT)
Received: by mail-ie0-f178.google.com with SMTP id x13so11443539ief.9 for <ipv6@ietf.org>; Mon, 28 Oct 2013 05:25: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=kJah1za1tBwggS+dyAp4TPwerzx+UAXjmT/IiQzj1JA=; b=fvgLBtSWU6ZsKz9dTdUPHtKFrX3mTo3vUF9cH93v96qV1GHl6dL90gRvvpH+kS4J2a PLsVr7MOWVtKkyz1gwhHg1zrOdIEPNAUJqiqZs9nLSUBb70XRTYoeLvc28hGw+QEOlvU 9nSLoqaVbgY+p8/9mqlHWXhtLWf+z1ENWEgUj5T2TVyAwQwjN+CvXjax2dsDkhjQrsHw f+2bF5j3HyJ6cfqVcrmuSiy8F2KYE/uK/1In97G+nOSjX1zrUbEQdOjZQ8QR+HdCHk7P iIxk1Do96vPiL1A+/30ImWd2w4oyTC04xgC+Wsxvrtu/lKABDyFQr1QTwkGcc+MMuor1 GlpA==
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=kJah1za1tBwggS+dyAp4TPwerzx+UAXjmT/IiQzj1JA=; b=ToJ6JbpnxNTvy08SXHAcazTM0xqvAe1UQ8lG2YXIIcUI727Lj2VL2gVEpirNscz66J bqKiQVdL5OsyxjX30Pifyx17DDfAMwv/PNguvvM0SritSOsSP1iQidc8QJH9jZMW6v9n 2Grhg4d+JTWvhqbJ3b3mbkUcyehBUzYRjgHG18ECXWwkfoZYNvbRwN3mACCRzUhw8gVG OHcFuiBcltkXXSfgtsTy/Vz21Bc8ahWduM93o1XsFBzKdZtgDslORl9ETr3IPcdU9N+/ jZLY/F4T5U1MuzkNtr4yDEPGRmErhYJcbJfdcg1VcB59MVjgSMSIJqc/f4u2Ra8BcMzU qBng==
X-Gm-Message-State: ALoCoQmq1U7NZbV/9gKkjeqNjP262JnDwvlq1hpaSe5rWKxGfwnSZGYRvDkJeZ1tKJgmqrWK3VV8NPqETcQTGvraRHSS/3SBMXGsAwxEiFjmaFC2q8rd98vtqZ+ys/FhB3RuvG+ChviKSIf9jsdSygb/D3AK3EM9/tRAOc2i0YicEQtmdcYckBBvv0Bhz9afq336GSgrtlb2
X-Received: by 10.42.53.148 with SMTP id n20mr217033icg.69.1382963103067; Mon, 28 Oct 2013 05:25:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.86.106 with HTTP; Mon, 28 Oct 2013 05:24:41 -0700 (PDT)
In-Reply-To: <8392F9BAC6AD5F47920216A6D7853F7E1D581938@BPXM02GP.gisp.nec.co.jp>
References: <8392F9BAC6AD5F47920216A6D7853F7E1D581938@BPXM02GP.gisp.nec.co.jp>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 28 Oct 2013 21:24:41 +0900
Message-ID: <CAKD1Yr2yUTUgmbsse1h38qmGjZ0uSZaHdyehXdEJBUty8p81tg@mail.gmail.com>
Subject: Re: I-D Action: draft-kitamura-ipv6-zoneid-free-01.txt
To: Hiroshi Kitamura <kitamura@da.jp.nec.com>
Content-Type: multipart/alternative; boundary=20cf302236757f0fef04e9cc30a8
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "Ata, Shingo \(ata@info.eng.osaka-cu.ac.jp\)" <ata@info.eng.osaka-cu.ac.jp>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 12:25:17 -0000

--20cf302236757f0fef04e9cc30a8
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Oct 28, 2013 at 7:43 PM, Hiroshi Kitamura <kitamura@da.jp.nec.com>wrote:

> For such a case (the same value addresses are located on different
> attached networks at same time), it is impossible to specify the correct
> destination without accompanying with "Zone-ID (interface)"
> information.
>
> At that situation, please accompany with "Zone-ID".
>

So you're saying that we shouldn't use scope IDs, but if the same IPv6
address is on two links, then we must use scope IDs? How is the user
supposed to know whether to use the scope ID or not?

--20cf302236757f0fef04e9cc30a8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Mon, Oct 28, 2013 at 7:43 PM, Hiroshi Kitamura <span di=
r=3D"ltr">&lt;<a href=3D"mailto:kitamura@da.jp.nec.com" target=3D"_blank">k=
itamura@da.jp.nec.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><=
div class=3D"gmail_quote">


<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">For such a case (the same value addresses ar=
e located on different attached networks at same time), it is impossible to=
 specify the correct destination without accompanying with &quot;Zone-ID (i=
nterface)&quot;<br>



information.<br>
<br>
At that situation, please accompany with &quot;Zone-ID&quot;.<br></blockquo=
te><div><br></div><div>So you&#39;re saying that we shouldn&#39;t use scope=
 IDs, but if the same IPv6 address is on two links, then we must use scope =
IDs? How is the user supposed to know whether to use the scope ID or not?</=
div>


</div></div></div>

--20cf302236757f0fef04e9cc30a8--

From mackermann@bcbsm.com  Mon Oct 28 09:13:25 2013
Return-Path: <mackermann@bcbsm.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45DB421E8095 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 09:13:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.031
X-Spam-Level: 
X-Spam-Status: No, score=-6.031 tagged_above=-999 required=5 tests=[AWL=-0.032, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YNadVPR9qbAN for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 09:13:19 -0700 (PDT)
Received: from mx.z120.zixworks.com (mx.z120.zixworks.com [199.30.235.120]) by ietfa.amsl.com (Postfix) with ESMTP id CB05411E8248 for <ipv6@ietf.org>; Mon, 28 Oct 2013 09:13:17 -0700 (PDT)
Received: from vmvpm02.z120.zixworks.com (ZixVPM [127.0.0.1]) by Outbound.z120.zixworks.com (Proprietary) with ESMTP id 421272FF6A3 for <ipv6@ietf.org>; Mon, 28 Oct 2013 11:13:17 -0500 (CDT)
Received: from imsva1.bcbsm.com (unknown [12.107.172.80]) by mx.z120.zixworks.com (Proprietary) with SMTP id 23FA3307427; Mon, 28 Oct 2013 11:13:16 -0500 (CDT)
Received: from imsva1.bcbsm.com (unknown [127.0.0.1]) by IMSVA80 (Postfix) with ESMTP id 0CF194F804D; Mon, 28 Oct 2013 12:02:52 -0400 (EDT)
Received: from pwn401ea100.ent.corp.bcbsm.com (unknown [10.64.80.217]) by imsva1.bcbsm.com (Postfix) with ESMTP id E76C24F8049; Mon, 28 Oct 2013 12:02:51 -0400 (EDT)
Received: from PWN401EA105.ent.corp.bcbsm.com (10.64.102.241) by PWN401EA100.ent.corp.bcbsm.com (10.64.80.217) with Microsoft SMTP Server (TLS) id 14.1.438.0; Mon, 28 Oct 2013 12:13:14 -0400
Received: from PWN401EA160.ent.corp.bcbsm.com ([fe80::fdcb:603d:469e:b1db]) by PWN401EA105.ent.corp.bcbsm.com ([fe80::f13e:83e4:1dae:5345%10]) with mapi id 14.01.0438.000; Mon, 28 Oct 2013 12:13:13 -0400
From: "Ackermann, Michael" <MAckermann@bcbsm.com>
To: Ray Hunter <v6ops@globis.net>
Subject: RE: [v6ops] Fw: New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-04.txt
Thread-Topic: [v6ops] Fw: New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-04.txt
Thread-Index: AQHO0OGzc1wNgnhly0SIwwwBJHHHZZoEfl4ggAF03YCABFViAA==
Date: Mon, 28 Oct 2013 16:13:13 +0000
Message-ID: <4FC37E442D05A748896589E468752CAA0CA8B1CD@PWN401EA160.ent.corp.bcbsm.com>
References: <20131017032024.5051.20799.idtracker@ietfa.amsl.com> <1381980305.36254.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com> <5263C783.1080001@globis.net> <1382396300.22968.YahooMailNeo@web2801.biz.mail.ne1.yahoo.com> <526616C4.40304@globis.net> <4FC37E442D05A748896589E468752CAA0CA88734@PWN401EA160.ent.corp.bcbsm.com> <52695E3A.9090406@globis.net> <4FC37E442D05A748896589E468752CAA0CA8A36F@PWN401EA160.ent.corp.bcbsm.com> <526AAC81.3050402@globis.net>
In-Reply-To: <526AAC81.3050402@globis.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.64.10.35]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-20254.000
x-tm-as-result: No--39.910400-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: v6ops WG <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>, "bill.jouris@insidethestack.com" <bill.jouris@insidethestack.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 16:13:25 -0000

Hey Ray

It appears your experiences with Time Synch and Stratum levels are =
different than mine.   In the older Telecom and Voice World Stratum was a =
great indicator of clocking accuracy.   Still is as far as I know.   This =
was always true with or without NTP in the picture.  =20
And whenever we had two Stratum 0's or 1's, be they the same or different =
masters, they WOULD be in synch.   We never had a situation that was an =
exception to that, with or without NTP. =20

Thanks

Mike


-----Original Message-----
From: Ray Hunter =5Bmailto:v6ops=40globis.net=5D=20
Sent: Friday, October 25, 2013 1:38 PM
To: Ackermann, Michael
Cc: Nalini Elkins; v6ops WG; 6man WG; ippm=40ietf.org; =
bill.jouris=40insidethestack.com; keven.haining=40usbank.com
Subject: Re: =5Bv6ops=5D Fw: New Version Notification for =
draft-elkins-6man-ipv6-pdm-dest-option-04.txt

> Ackermann, Michael <mailto:MAckermann=40bcbsm.com>
> 25 October 2013 01:44
> Ray
>
> Your Comment:=20
> No. I think what I said was that the level of certainty in your =
measurements is dependent on the level of synchronisation of the 2 clock =
sources if you are calculating a delta of timestamp of clock 1 - timestamp =
clock 2.
> My Response:
> Then it sounds like we are in agreement.   Given the appropriate stratum =
level at both nodes, the desired level of time synchronization is =
achieved.=20
>
No. We are not in agreement.

Stratum is an indication of how far down you are in the hierarchy from any =
NTP Stratum 0 clock.

It says nothing about whether your stratum 0 and my stratum 0 are =
synchronised.

We could both be running caesium clocks, and there could still be an =
offset if I don't set my reference time of my caesium clock the same as =
your reference time. When talking about microsecond or picosecond timing =
that will almost certainly be significant.

You really need to know that the true provenance of the clock source is =
identical in order to make PDM 1 calculations, not just the stratum.

Hence my comment to couple some sort of =22clock ID=22 to the timestamp.
> Your Comment:=20
> I think it might be instructive to go back and look at high school =
physics books on making measurements, precision, accuracy, and error =
estimations, especially when taking the difference of two measurements, or =
making other calculations on top of raw observations
> My Response:  Not sure exactly what this means but I can say that this =
sounds like theoretical doubt that time synchronization will not work =
properly in geographically dispersed environments?    I can tell you that =
it does in our experiences and that the surrounding =
protocols/implementations are crafted to account for such vicissitudes. =20
> I will say that I have no field experience with DCF-77 sources, only GPS =
and Cesium. =20
>
>
> Your Comment:
> Equally a stratum 0 clock can be free running if it loses it's radio =
signal.
> My Response:=20
> This comment sort of confused me as well, but suffice to say, if any =
component is broken, results will be impaired.   Obviously this is not =
limited to the time synch subject. =20
>
>
> Finally, your comment about =22Middleboxes=22.    I hope it can be as =
simple to accommodate as you describe.   My concern is that if there are =
numerous middleboxes, the fields may get repetitively overlaid, or there =
will need to be so many separate fields, we could incur excessive =
complexity or overhead.    Given that we can accomplish this with a =
workable solution, I am certainly all for it.  =20
> The more information I can have to manage networks and solve problems, =
the better=21
>
> Thanks again for your thoughts, inputs and questions=21
>
> Mike
>
>
>
>
>
>
>
>
>
>
>



The information contained in this communication is highly confidential and =
is intended solely for the use of the individual(s) to whom this =
communication is directed. If you are not the intended recipient, you are =
hereby notified that any viewing, copying, disclosure or distribution of =
this information is prohibited. Please notify the sender, by electronic =
mail or telephone, of any unintended receipt and delete the original =
message without making any copies.
=20
 Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are =
nonprofit corporations and independent licensees of the Blue Cross and =
Blue Shield Association.

From brian@innovationslab.net  Mon Oct 28 09:24:19 2013
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69EA521F9F08; Mon, 28 Oct 2013 09:24:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.562
X-Spam-Level: 
X-Spam-Status: No, score=-102.562 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uJT9wXzC8fBb; Mon, 28 Oct 2013 09:24:13 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id EC8F421F9FE9; Mon, 28 Oct 2013 09:24:12 -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 6B2A6880A4; Mon, 28 Oct 2013 09:24:12 -0700 (PDT)
Received: from 102527254.rudm1.ra.johnshopkins.edu (addr16212925014.ippl.jhmi.edu [162.129.250.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id D1EE3130003; Mon, 28 Oct 2013 09:24:11 -0700 (PDT)
Message-ID: <526E8FA3.70506@innovationslab.net>
Date: Mon, 28 Oct 2013 12:24:03 -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.0.1
MIME-Version: 1.0
To: "Ackermann, Michael" <MAckermann@bcbsm.com>, Ray Hunter <v6ops@globis.net>
Subject: Re: [v6ops] Fw: New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-04.txt
References: <20131017032024.5051.20799.idtracker@ietfa.amsl.com>	<1381980305.36254.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com>	<5263C783.1080001@globis.net>	<1382396300.22968.YahooMailNeo@web2801.biz.mail.ne1.yahoo.com>	<526616C4.40304@globis.net>	<4FC37E442D05A748896589E468752CAA0CA88734@PWN401EA160.ent.corp.bcbsm.com>	<52695E3A.9090406@globis.net>	<4FC37E442D05A748896589E468752CAA0CA8A36F@PWN401EA160.ent.corp.bcbsm.com>	<526AAC81.3050402@globis.net> <4FC37E442D05A748896589E468752CAA0CA8B1CD@PWN401EA160.ent.corp.bcbsm.com>
In-Reply-To: <4FC37E442D05A748896589E468752CAA0CA8B1CD@PWN401EA160.ent.corp.bcbsm.com>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="LXMC8R1hVTxIoGgRMCMvKvREBwr3bvGvq"
Cc: v6ops WG <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 16:24:19 -0000

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

Hi Michael.

On 10/28/13 12:13 PM, Ackermann, Michael wrote:
> Hey Ray
>=20
> It appears your experiences with Time Synch and Stratum levels are
> different than mine.   In the older Telecom and Voice World Stratum
> was a great indicator of clocking accuracy.   Still is as far as I
> know.   This was always true with or without NTP in the picture. And
> whenever we had two Stratum 0's or 1's, be they the same or different
> masters, they WOULD be in synch.   We never had a situation that was
> an exception to that, with or without NTP.

The NTP definition of stratum is different from that used in the
telecommunications domain.  The primary feature of a NTP stratum 0 clock
is the ability to generate accurate pulse per second signals, hence
calling them reference clocks.  It should be noted that in NTP, stratum
0 clocks are *not* NTP servers, they are the source of time information
to stratum 1 servers that serve time via NTP.

Regards,
Brian


--LXMC8R1hVTxIoGgRMCMvKvREBwr3bvGvq
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

iQEcBAEBCgAGBQJSbo+oAAoJEBOZRqCi7goqJT8IANGmjK6dYI7nZ/3QdwAVIANj
fVHFVQ/XBKDld0ZX37POiLxI8FwfqYYRmEEWeyRRrej2qcHiAyGD+d1YstctL/qw
PVIZbBwZSHkZIGp/Sd6PZEm//R3opF8RhV/TFnJL35vEELyfClH0qb70BJaZ9Fxu
EBfIoXI4IJB3YS7h+De/lD0VYd4JprdUVj3kbnVOI23UWR7OMUiG4o1nQy0rPkvP
ItKZq4BzNUp8fhZovlwOb0GlocyBx1qmXl7Ptiij4SmM0BRBVHNhZ0uoRyyq7C73
PodrP7N68+VVszPfU9Xv5LgVGIE2iTyLQVt5QFdFl6dDfaAEM5N6Q36Cc0IY6f4=
=tJLW
-----END PGP SIGNATURE-----

--LXMC8R1hVTxIoGgRMCMvKvREBwr3bvGvq--

From alvarezp@alvarezp.ods.org  Mon Oct 28 09:32:24 2013
Return-Path: <alvarezp@alvarezp.ods.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F57011E82BD for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 09:32:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S4sF9ondDuAs for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 09:32:18 -0700 (PDT)
Received: from sobre.alvarezp.com (sobre.alvarezp.com [173.230.155.94]) by ietfa.amsl.com (Postfix) with ESMTP id B52E511E8292 for <ipv6@ietf.org>; Mon, 28 Oct 2013 09:32:16 -0700 (PDT)
Received: from [192.168.2.251] (189.220.45.207.cable.dyn.cableonline.com.mx [189.220.45.207]) by sobre.alvarezp.com (Postfix) with ESMTPSA id 5F5C1613D; Mon, 28 Oct 2013 12:32:16 -0400 (EDT)
Message-ID: <526E91A3.8000807@alvarezp.ods.org>
Date: Mon, 28 Oct 2013 09:32:35 -0700
From: Octavio Alvarez <alvarezp@alvarezp.ods.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130821 Icedove/17.0.8
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com>	<526AACA5.7090604@si6networks.com>	<E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<526AC8AF.4060608@si6networks.com>	<8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org> <526E43E8.3080601@gmail.com>
In-Reply-To: <526E43E8.3080601@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>, Tim Chown <tjc@ecs.soton.ac.uk>, "Fred Baker \(fred\)" <fred@cisco.com>, Fernando Gont <fgont@si6networks.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 16:32:24 -0000

On 10/28/2013 04:00 AM, Alexandru Petrescu wrote:
> Le 27/10/2013 16:53, Octavio Alvarez a écrit :
>> On 10/27/2013 02:26 AM, Jeroen Massar wrote:
>>>> allows privacy,
>>>
>>> IMHO big nonsense. The company (amongst many others!) you work for uses
>>> amongst others cookies to track their people, and if they really bother
>>> could even use natural language structure, search query types, and other
>>> behavior for breaking this 'privacy'. Also note that even if the last
>>> 64bits are random, your company should be more than able to say "oh,
>>> there are typically X users in there, it likely is Y"...
>>
>> Then why deprecate EUI-64?
> 
> I think there is a problem in naming that draft.

I meant "why deprecate EUI-64 as device-ID in IPv6 addresses". Sorry if
this starts a misconception.



From jinmei.tatuya@gmail.com  Mon Oct 28 09:46:53 2013
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2FDF11E814C; Mon, 28 Oct 2013 09:46:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.222
X-Spam-Level: *
X-Spam-Status: No, score=1.222 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QdWl+qb4APO1; Mon, 28 Oct 2013 09:46:53 -0700 (PDT)
Received: from mail-we0-x233.google.com (mail-we0-x233.google.com [IPv6:2a00:1450:400c:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id A153111E8260; Mon, 28 Oct 2013 09:46:49 -0700 (PDT)
Received: by mail-we0-f179.google.com with SMTP id w61so6752092wes.38 for <multiple recipients>; Mon, 28 Oct 2013 09:46:48 -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=TQylOX+RjV8qapGkBxtbp59ua6uTc10LbFEI6ta389c=; b=AaHdt1RwIa6jFqNbP+QfCAXGBJwqe6A40j3x2mGHIKxc684EL9qawnhcoEUn35WEom 86M+3eggxTx9KZXxMwUmW7udnv4Ty8WmYo24oJv2khWg9Tql2eeSb2qQ396r+P7OZ/sU dqHyIKg0Rl8ys6ZyPw+ccJWL9s//2oqvgL7rYLDOHzeZf13cJoqbVfD9R0QAObCFnCQf aD6b3T/CrGV336JRPPpU8tEM8Tgdd7871ySUpqKY0iW9lne/rmw3GdNTUYqt78Jzo8TG nr/B1GrQX/GraXTaumYqYl1hhRb5DtPfVh3ECcbyibszKAKsCxXgBkwQHcd111y5HulZ 22gQ==
MIME-Version: 1.0
X-Received: by 10.194.77.41 with SMTP id p9mr2287263wjw.66.1382978808625; Mon, 28 Oct 2013 09:46:48 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.120.167 with HTTP; Mon, 28 Oct 2013 09:46:48 -0700 (PDT)
In-Reply-To: <4518F39EB578034D8C99A9B7776CDBA301C06DD6@xmb-aln-x04.cisco.com>
References: <3599.1381852752@sandelman.ca> <CE82BA46.24343%d.sturek@att.net> <CABOxzu2nLuny5uySEEdb6ji9ucE6xqGZ6DLe-mc6KUqVszNfFg@mail.gmail.com> <525DC6C9.2010808@gridmerge.com> <CABOxzu2apwBRpU1h4mKJwpO+U+Y9Q_q-h5AhZ+hGzAdjdPdmUQ@mail.gmail.com> <525E5064.4050109@gridmerge.com> <CABOxzu0L-EY0iDGpAJ+ER15CPL-3v8F77ewn-G=gZYODixevZg@mail.gmail.com> <3CC8783F-F4DA-47B9-A051-DBBA6EF00C19@gmail.com> <4518F39EB578034D8C99A9B7776CDBA301C067D0@xmb-aln-x04.cisco.com> <1daea916972b4e60be575e5f5276cb78@BY2PR03MB269.namprd03.prod.outlook.com> <4518F39EB578034D8C99A9B7776CDBA301C06DD6@xmb-aln-x04.cisco.com>
Date: Mon, 28 Oct 2013 09:46:48 -0700
X-Google-Sender-Auth: MgmCN6IzTKBpROM0ljIkjsISEaQ
Message-ID: <CAJE_bqcyWMYw4NHS8xMu+JtWQwV8t97Lcf0BzC1Qe0zgmR4aMQ@mail.gmail.com>
Subject: Re: draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re: [Roll] [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope value of 3 - subnet-local)
From: =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>
To: "Ralph Droms (rdroms)" <rdroms@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Routing Over Low power and Lossy networks <roll@ietf.org>, "6man@ietf.org" <6man@ietf.org>, Dave Thaler <dthaler@microsoft.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 16:46:54 -0000

At Fri, 25 Oct 2013 20:44:57 +0000,
"Ralph Droms (rdroms)" <rdroms@cisco.com> wrote:

> >>   NEW:
> >>
> >>         Interface-Local, Link-Local, and Realm-Local scope boundaries
> >>         are automatically derived from physical connectivity or
> >>         other, non-multicast related configuration.  Global scope has
> >>         no boundary.  The boundaries of all other non-reserved scopes
> >>         are administratively configured.
> >
> > I disagree with the last sentence above.  Specifically
> > "non-reserved" should be removed.  That is, we should not start
> > precluding admin configuration of reserved scopes, given we didn't
> > before.  They just didn't have defined names or uses, but they could
> > have been used within private environments.
>
> Good catch.  So the last sentence should read:
>
>   The boundaries of all other scopes are administratively configured.

First off, whether we include "non-reserved" or not, we should clarify
this only applies to admin-local or larger.  So, e.g.

   The boundaries of all other scopes of Admin-Local or larger are
   administratively configured.

Secondly, I don't think the "NEW" text (necessarily) precludes admin
configuration of reserved scopes (in this context it specifically
means scope 15).  With "non-reserved", I meant it specifically means
scopes # 5-13.  It intended to not say about scope #15, rather than
preclude admin configuration for it.  On the other hand, the suggested
revised version  explicitly states that the boundaries of scope #15
are administratively configured.  I don't know if that's what this
scope was supposed to be.  If it was, then this version is okay.  If
not, and if the "NEW" version was confusing, I suggest:

  The boundaries of all other non-reserved scopes of Admin-Local or
  larger are administratively configured.  For reserved scopes, the
  way of configuring their boundaries will be defined when the
  semantics of the scope is defined.

--
JINMEI, Tatuya

From alvarezp@alvarezp.ods.org  Mon Oct 28 09:47:16 2013
Return-Path: <alvarezp@alvarezp.ods.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0F9F11E814C for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 09:47:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6jMRjuxxAomf for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 09:47:16 -0700 (PDT)
Received: from sobre.alvarezp.com (sobre.alvarezp.com [IPv6:2600:3c01::f03c:91ff:fe96:8fec]) by ietfa.amsl.com (Postfix) with ESMTP id 7EEB121E80AB for <ipv6@ietf.org>; Mon, 28 Oct 2013 09:47:04 -0700 (PDT)
Received: from [192.168.2.251] (189.220.45.207.cable.dyn.cableonline.com.mx [189.220.45.207]) by sobre.alvarezp.com (Postfix) with ESMTPSA id 8D9E8613D; Mon, 28 Oct 2013 12:47:00 -0400 (EDT)
Message-ID: <526E9517.1090207@alvarezp.ods.org>
Date: Mon, 28 Oct 2013 09:47:19 -0700
From: Octavio Alvarez <alvarezp@alvarezp.ods.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130821 Icedove/17.0.8
MIME-Version: 1.0
To: Jeroen Massar <jeroen@massar.ch>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com>	<526AACA5.7090604@si6networks.com>	<E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<526AC8AF.4060608@si6networks.com>	<8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com>	<CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com>	<526CDC59.4070204@massar.ch>	<CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com>	<CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com> <CAKFn1SG1PC_kA-pO5Or8VyeaOzvLfpmQe0LiiYkXU_HzNqGzCQ@mail.gmail.com> <526E250E.5050607@massar.ch>
In-Reply-To: <526E250E.5050607@massar.ch>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 16:47:16 -0000

On 10/28/2013 01:49 AM, Jeroen Massar wrote:
> On 2013-10-27 15:50, Roger Jørgensen wrote:
> [..]
>> Privacy isn't just one single thing. That the user might lose privacy
>> elsewhere in the entire stack that make up Internet, that's NOT an
>> argument to give up /64 because we have lost privacy anyhow.
> 
> I am NOT arguing that a /64 should go the way of the dodo.
> I am only stating that this "IPv6 Privacy Address" thing is a myth.

Which is also inaccurate, as the purpose is not to provide privacy, but
just to prevent anti-privacy through the IPv6 address.

It's difficult to choose the right words for this.

From mackermann@bcbsm.com  Mon Oct 28 09:49:56 2013
Return-Path: <mackermann@bcbsm.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CB0821E80BF for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 09:49:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.026
X-Spam-Level: 
X-Spam-Status: No, score=-6.026 tagged_above=-999 required=5 tests=[AWL=-0.027, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j9EE9+b+6xuM for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 09:49:50 -0700 (PDT)
Received: from mx.z120.zixworks.com (mx.z120.zixworks.com [199.30.235.120]) by ietfa.amsl.com (Postfix) with ESMTP id D99FF21E80AC for <ipv6@ietf.org>; Mon, 28 Oct 2013 09:49:26 -0700 (PDT)
Received: from vmvpm02.z120.zixworks.com (ZixVPM [127.0.0.1]) by Outbound.z120.zixworks.com (Proprietary) with ESMTP id 8C69C2FF696 for <ipv6@ietf.org>; Mon, 28 Oct 2013 11:49:26 -0500 (CDT)
Received: from imsva2.bcbsm.com (unknown [12.107.172.81]) by mx.z120.zixworks.com (Proprietary) with SMTP id BAD5230742E; Mon, 28 Oct 2013 11:49:25 -0500 (CDT)
Received: from imsva2.bcbsm.com (unknown [127.0.0.1]) by IMSVA80 (Postfix) with ESMTP id C733D2F0049; Mon, 28 Oct 2013 12:38:42 -0400 (EDT)
Received: from pwn401ea100.ent.corp.bcbsm.com (unknown [10.64.80.217]) by imsva2.bcbsm.com (Postfix) with ESMTP id BAB912F0043; Mon, 28 Oct 2013 12:38:42 -0400 (EDT)
Received: from PWN401EA105.ent.corp.bcbsm.com (10.64.102.241) by PWN401EA100.ent.corp.bcbsm.com (10.64.80.217) with Microsoft SMTP Server (TLS) id 14.1.438.0; Mon, 28 Oct 2013 12:49:24 -0400
Received: from PWN401EA160.ent.corp.bcbsm.com ([fe80::fdcb:603d:469e:b1db]) by PWN401EA105.ent.corp.bcbsm.com ([fe80::f13e:83e4:1dae:5345%10]) with mapi id 14.01.0438.000; Mon, 28 Oct 2013 12:49:23 -0400
From: "Ackermann, Michael" <MAckermann@bcbsm.com>
To: Brian Haberman <brian@innovationslab.net>, Ray Hunter <v6ops@globis.net>
Subject: RE: [v6ops] Fw: New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-04.txt
Thread-Topic: [v6ops] Fw: New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-04.txt
Thread-Index: AQHO0OGzc1wNgnhly0SIwwwBJHHHZZoEfl4ggAF03YCABFViAIAATOiA///D2ZA=
Date: Mon, 28 Oct 2013 16:49:21 +0000
Message-ID: <4FC37E442D05A748896589E468752CAA0CA8B261@PWN401EA160.ent.corp.bcbsm.com>
References: <20131017032024.5051.20799.idtracker@ietfa.amsl.com> <1381980305.36254.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com> <5263C783.1080001@globis.net> <1382396300.22968.YahooMailNeo@web2801.biz.mail.ne1.yahoo.com> <526616C4.40304@globis.net> <4FC37E442D05A748896589E468752CAA0CA88734@PWN401EA160.ent.corp.bcbsm.com> <52695E3A.9090406@globis.net> <4FC37E442D05A748896589E468752CAA0CA8A36F@PWN401EA160.ent.corp.bcbsm.com> <526AAC81.3050402@globis.net> <4FC37E442D05A748896589E468752CAA0CA8B1CD@PWN401EA160.ent.corp.bcbsm.com> <526E8FA3.70506@innovationslab.net>
In-Reply-To: <526E8FA3.70506@innovationslab.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.64.10.35]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-20254.000
x-tm-as-result: No--36.829100-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: v6ops WG <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 16:49:56 -0000

Thank you Brian.

What you say matches my understanding and experiences



-----Original Message-----
From: Brian Haberman =5Bmailto:brian=40innovationslab.net=5D=20
Sent: Monday, October 28, 2013 12:24 PM
To: Ackermann, Michael; Ray Hunter
Cc: v6ops WG; 6man WG; ippm=40ietf.org
Subject: Re: =5Bv6ops=5D Fw: New Version Notification for =
draft-elkins-6man-ipv6-pdm-dest-option-04.txt

Hi Michael.

On 10/28/13 12:13 PM, Ackermann, Michael wrote:
> Hey Ray
>=20
> It appears your experiences with Time Synch and Stratum levels are
> different than mine.   In the older Telecom and Voice World Stratum
> was a great indicator of clocking accuracy.   Still is as far as I
> know.   This was always true with or without NTP in the picture. And
> whenever we had two Stratum 0's or 1's, be they the same or different
> masters, they WOULD be in synch.   We never had a situation that was
> an exception to that, with or without NTP.

The NTP definition of stratum is different from that used in the =
telecommunications domain.  The primary feature of a NTP stratum 0 clock =
is the ability to generate accurate pulse per second signals, hence =
calling them reference clocks.  It should be noted that in NTP, stratum
0 clocks are *not* NTP servers, they are the source of time information to =
stratum 1 servers that serve time via NTP.

Regards,
Brian



The information contained in this communication is highly confidential and =
is intended solely for the use of the individual(s) to whom this =
communication is directed. If you are not the intended recipient, you are =
hereby notified that any viewing, copying, disclosure or distribution of =
this information is prohibited. Please notify the sender, by electronic =
mail or telephone, of any unintended receipt and delete the original =
message without making any copies.
=20
 Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are =
nonprofit corporations and independent licensees of the Blue Cross and =
Blue Shield Association.

From alvarezp@alvarezp.ods.org  Mon Oct 28 09:56:51 2013
Return-Path: <alvarezp@alvarezp.ods.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7F3D21E80DF for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 09:56:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6bnxHRG8hxii for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 09:56:36 -0700 (PDT)
Received: from sobre.alvarezp.com (sobre.alvarezp.com [173.230.155.94]) by ietfa.amsl.com (Postfix) with ESMTP id 2242011E818D for <ipv6@ietf.org>; Mon, 28 Oct 2013 09:56:03 -0700 (PDT)
Received: from [192.168.2.251] (189.220.45.207.cable.dyn.cableonline.com.mx [189.220.45.207]) by sobre.alvarezp.com (Postfix) with ESMTPSA id 9D100613D; Mon, 28 Oct 2013 12:56:02 -0400 (EDT)
Message-ID: <526E9735.8080708@alvarezp.ods.org>
Date: Mon, 28 Oct 2013 09:56:21 -0700
From: Octavio Alvarez <alvarezp@alvarezp.ods.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130821 Icedove/17.0.8
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CF079.7030804@globis.net> <526E41BC.3080303@gmail.com>
In-Reply-To: <526E41BC.3080303@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>, Ray Hunter <v6ops@globis.net>, Tim Chown <tjc@ecs.soton.ac.uk>, "Fred Baker \(fred\)" <fred@cisco.com>, Fernando Gont <fgont@si6networks.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 16:56:51 -0000

On 10/28/2013 03:51 AM, Alexandru Petrescu wrote:
>> Me? I believe in CIDR.
> 
> The IPv4's CIDR concept (route based on bitwise borders, instead of
> 8byte) seems to me a good clue for the discussion about the fix 64bit
> limit in IPv6.

CIDR is already being used. /80s, /96s and other arbitrary netmasks can
be set on some devices and should work. Some of them may misbehave, though.

But still, there is nothing to fix. The /64 limit is not a problem and
will not be.

Also, RFC 4941 (and some others) depend on /64 networks.

Cheers.

From james.cutler@consultant.com  Mon Oct 28 09:58:36 2013
Return-Path: <james.cutler@consultant.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B72E21E80AA for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 09:58:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SOCU2ZofaEhI for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 09:58:26 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [74.208.4.200]) by ietfa.amsl.com (Postfix) with ESMTP id D690621E80EB for <ipv6@ietf.org>; Mon, 28 Oct 2013 09:57:41 -0700 (PDT)
Received: from [192.168.1.44] ([68.43.142.33]) by mail.gmx.com (mrgmxus001) with ESMTPSA (Nemesis) id 0M4Gij-1Vs5jc4B2x-00rtFr for <ipv6@ietf.org>; Mon, 28 Oct 2013 17:57:41 +0100
Content-Type: multipart/signed; boundary="Apple-Mail=_4131A7D2-A07B-4DA4-9414-BD6083408703"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Subject: Re: [v6ops] Fw: New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-04.txt
From: Cutler James R <james.cutler@consultant.com>
In-Reply-To: <4FC37E442D05A748896589E468752CAA0CA8B1CD@PWN401EA160.ent.corp.bcbsm.com>
Date: Mon, 28 Oct 2013 12:57:36 -0400
Message-Id: <1B14CBF5-5F4D-4B92-B1BB-31E15AD7786D@consultant.com>
References: <20131017032024.5051.20799.idtracker@ietfa.amsl.com> <1381980305.36254.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com> <5263C783.1080001@globis.net> <1382396300.22968.YahooMailNeo@web2801.biz.mail.ne1.yahoo.com> <526616C4.40304@globis.net> <4FC37E442D05A748896589E468752CAA0CA88734@PWN401EA160.ent.corp.bcbsm.com> <52695E3A.9090406@globis.net> <4FC37E442D05A748896589E468752CAA0CA8A36F@PWN401EA160.ent.corp.bcbsm.com> <526AAC81.3050402@globis.net> <4FC37E442D05A748896589E468752CAA0CA8B1CD@PWN401EA160.ent.corp.bcbsm.com>
To: "Ackermann, Michael" <MAckermann@bcbsm.com>
X-Mailer: Apple Mail (2.1816)
X-Provags-ID: V03:K0:DxEEmIFvqXelqJ2NR+fhFmhyJ+jJYG6S4I48rlCSuOHXE7Vov4X fCP9Y+HVnL2+n+Sp1u1apEY7c9qrLBHI99+4ooSk/2EKtmEZzYEZ9JRg74yM+EXdqGK2a4p 2/SawheEQrNzgoDM5duUNph4Fjoi2n3euHNPnG0jPEnIKoXLS2gTOjro+v5hnbOd+G7BaRj x9NB+SyitFWqXjYerlpXA==
Cc: Ray Hunter <v6ops@globis.net>, v6ops WG <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "bill.jouris@insidethestack.com" <bill.jouris@insidethestack.com>, "ippm@ietf.org" <ippm@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 16:58:36 -0000

--Apple-Mail=_4131A7D2-A07B-4DA4-9414-BD6083408703
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

On Oct 28, 2013, at 12:13 PM, Ackermann, Michael <MAckermann@bcbsm.com> =
wrote:

> Hey Ray
>=20
> It appears your experiences with Time Synch and Stratum levels are =
different than mine.   In the older Telecom and Voice World Stratum was =
a great indicator of clocking accuracy.   Still is as far as I know.   =
This was always true with or without NTP in the picture.  =20
> And whenever we had two Stratum 0's or 1's, be they the same or =
different masters, they WOULD be in synch.   We never had a situation =
that was an exception to that, with or without NTP. =20
>=20
> Thanks
>=20
> Mike

Before getting too deep into this particular argument, it would be good =
to review documents at http://www.eecis.udel.edu/~mills/ntp.html and =
ntp.org. =20

When discussion time synchronization using NTP, stratum refers to the =
distance from reference clock.  Accuracy is separately a function of =
reference clock and there are many variants of reference clock.  That =
two systems are =93in synch=94 is the magic of NTP algorithms and is =
orthogonal to accuracy.

James R. Cutler
james.cutler@consultant.com





--Apple-Mail=_4131A7D2-A07B-4DA4-9414-BD6083408703
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-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlJul4AACgkQHzETiNcaVPm/0gCgkKNJcGiI9JB5dp8MKjpgjhk7
Pq0An3M3/w1/+86pdlWThCMUlJkpQCTK
=yNzd
-----END PGP SIGNATURE-----

--Apple-Mail=_4131A7D2-A07B-4DA4-9414-BD6083408703--

From jeroen@massar.ch  Mon Oct 28 10:06:51 2013
Return-Path: <jeroen@massar.ch>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C35AD11E8286 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 10:06:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=2.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b5dOFedDtj2w for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 10:06:34 -0700 (PDT)
Received: from icaras.de.unfix.org (icaras.de.unfix.org [78.47.209.234]) by ietfa.amsl.com (Postfix) with ESMTP id E5CD211E8260 for <ipv6@ietf.org>; Mon, 28 Oct 2013 10:06:11 -0700 (PDT)
Received: from yomi.ch.unfix.org (84-73-144-213.dclient.hispeed.ch [84.73.144.213]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeroen) by icaras.de.unfix.org (Postfix) with ESMTPSA id 9C569801C2A2; Mon, 28 Oct 2013 18:06:01 +0100 (CET)
Message-ID: <526E995D.1000502@massar.ch>
Date: Mon, 28 Oct 2013 18:05:33 +0100
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar Networking
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Octavio Alvarez <alvarezp@alvarezp.ods.org>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com>	<526AACA5.7090604@si6networks.com>	<E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<526AC8AF.4060608@si6networks.com>	<8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com>	<CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com>	<526CDC59.4070204@massar.ch>	<CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com>	<CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com> <CAKFn1SG1PC_kA-pO5Or8VyeaOzvLfpmQe0LiiYkXU_HzNqGzCQ@mail.gmail.com> <526E250E.5050607@massar.ch> <526E9517.1090207@alvarezp.ods.org>
In-Reply-To: <526E9517.1090207@alvarezp.ods.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 17:06:52 -0000

On 2013-10-28 17:47 , Octavio Alvarez wrote:
> On 10/28/2013 01:49 AM, Jeroen Massar wrote:
>> On 2013-10-27 15:50, Roger Jørgensen wrote:
>> [..]
>>> Privacy isn't just one single thing. That the user might lose privacy
>>> elsewhere in the entire stack that make up Internet, that's NOT an
>>> argument to give up /64 because we have lost privacy anyhow.
>>
>> I am NOT arguing that a /64 should go the way of the dodo.
>> I am only stating that this "IPv6 Privacy Address" thing is a myth.
> 
> Which is also inaccurate, as the purpose is not to provide privacy, but
> just to prevent anti-privacy through the IPv6 address.

Please explain this "anti-privacy" concept.

> It's difficult to choose the right words for this.

You mean that it is difficult to justify randomizing bits as it does not
solve the problem at hand: you can and will be tracked.

>From the intro of RFC4941:
----
   Changing the interface
   identifier (and the global scope addresses generated from it) over
   time makes it more difficult for eavesdroppers and other information
   collectors to identify when different addresses used in different
   transactions actually correspond to the same node."
----

As it states 'more difficult'. Since 2001 (RFC3041 which has the same
wording and intent) this kind of tracking tech and the compute power has
advanced enough though that the difficulty is futile.

Greets,
 Jeroen


From joelja@bogus.com  Mon Oct 28 10:07:08 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E44E21E80BA; Mon, 28 Oct 2013 10:07:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.25
X-Spam-Level: 
X-Spam-Status: No, score=-102.25 tagged_above=-999 required=5 tests=[AWL=-0.251, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7uORJfg7G7hd; Mon, 28 Oct 2013 10:07:02 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id D150111E8286; Mon, 28 Oct 2013 10:06:56 -0700 (PDT)
Received: from 00698a-hsutim.corp.zynga.com ([199.48.105.4]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r9SH6oA9084644 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 28 Oct 2013 17:06:51 GMT (envelope-from joelja@bogus.com)
Content-Type: multipart/signed; boundary="Apple-Mail=_F0041254-84C3-481F-8877-236BC366790F"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Subject: Re: [v6ops] Fw: New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-04.txt
From: joel jaeggli <joelja@bogus.com>
In-Reply-To: <4FC37E442D05A748896589E468752CAA0CA8B261@PWN401EA160.ent.corp.bcbsm.com>
Date: Mon, 28 Oct 2013 10:06:44 -0700
Message-Id: <822EAF96-CFCF-4584-B590-08CAFE6AF260@bogus.com>
References: <20131017032024.5051.20799.idtracker@ietfa.amsl.com> <1381980305.36254.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com> <5263C783.1080001@globis.net> <1382396300.22968.YahooMailNeo@web2801.biz.mail.ne1.yahoo.com> <526616C4.40304@globis.net> <4FC37E442D05A748896589E468752CAA0CA88734@PWN401EA160.ent.corp.bcbsm.com> <52695E3A.9090406@globis.net> <4FC37E442D05A748896589E468752CAA0CA8A36F@PWN401EA160.ent.corp.bcbsm.com> <526AAC81.3050402@globis.net> <4FC37E442D05A748896589E468752CAA0CA8B1CD@PWN401EA160.ent.corp.bcbsm.com> <526E8FA3.70506@innovationslab.net> <4FC37E442D05A748896589E468752CAA0CA8B261@PWN401EA160.ent.corp.bcbsm.com>
To: "Ackermann, Michael" <MAckermann@bcbsm.com>
X-Mailer: Apple Mail (2.1816)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Mon, 28 Oct 2013 17:06:52 +0000 (UTC)
Cc: Ray Hunter <v6ops@globis.net>, Brian Haberman <brian@innovationslab.net>, 6man WG <ipv6@ietf.org>, v6ops WG <v6ops@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 17:07:09 -0000

--Apple-Mail=_F0041254-84C3-481F-8877-236BC366790F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Oct 28, 2013, at 9:49 AM, Ackermann, Michael <MAckermann@bcbsm.com> =
wrote:

> Thank you Brian.
>=20
> What you say matches my understanding and experiences
>=20

Then you should revise your statement accordingly=85

>=20
>=20
> -----Original Message-----
> From: Brian Haberman [mailto:brian@innovationslab.net]=20
> Sent: Monday, October 28, 2013 12:24 PM
> To: Ackermann, Michael; Ray Hunter
> Cc: v6ops WG; 6man WG; ippm@ietf.org
> Subject: Re: [v6ops] Fw: New Version Notification for =
draft-elkins-6man-ipv6-pdm-dest-option-04.txt
>=20
> Hi Michael.
>=20
> On 10/28/13 12:13 PM, Ackermann, Michael wrote:
>> Hey Ray
>>=20
>> It appears your experiences with Time Synch and Stratum levels are
>> different than mine.   In the older Telecom and Voice World Stratum
>> was a great indicator of clocking accuracy.   Still is as far as I
>> know.   This was always true with or without NTP in the picture. And
>> whenever we had two Stratum 0's or 1's, be they the same or different
>> masters, they WOULD be in synch.   We never had a situation that was
>> an exception to that, with or without NTP.
>=20
> The NTP definition of stratum is different from that used in the =
telecommunications domain.  The primary feature of a NTP stratum 0 clock =
is the ability to generate accurate pulse per second signals, hence =
calling them reference clocks.  It should be noted that in NTP, stratum
> 0 clocks are *not* NTP servers, they are the source of time =
information to stratum 1 servers that serve time via NTP.
>=20
> Regards,
> Brian
>=20
>=20
>=20
> The information contained in this communication is highly confidential =
and is intended solely for the use of the individual(s) to whom this =
communication is directed. If you are not the intended recipient, you =
are hereby notified that any viewing, copying, disclosure or =
distribution of this information is prohibited. Please notify the =
sender, by electronic mail or telephone, of any unintended receipt and =
delete the original message without making any copies.
>=20
> Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan =
are nonprofit corporations and independent licensees of the Blue Cross =
and Blue Shield Association.
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>=20


--Apple-Mail=_F0041254-84C3-481F-8877-236BC366790F
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 - http://gpgtools.org

iEYEARECAAYFAlJumaQACgkQ8AA1q7Z/VrKNTwCeKwXEXH3o3mhMn6Nk+j9OFjSy
hv8AniJHBe98K8aKQCwTjT/H6QszaUy9
=wjCb
-----END PGP SIGNATURE-----

--Apple-Mail=_F0041254-84C3-481F-8877-236BC366790F--

From nalini.elkins@insidethestack.com  Mon Oct 28 10:18:43 2013
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56EC511E828D for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 10:18:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.136
X-Spam-Level: 
X-Spam-Status: No, score=-2.136 tagged_above=-999 required=5 tests=[AWL=-0.138, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HAxb9jcVe679 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 10:18:43 -0700 (PDT)
Received: from nm17-vm6.access.bullet.mail.bf1.yahoo.com (nm17-vm6.access.bullet.mail.bf1.yahoo.com [216.109.115.69]) by ietfa.amsl.com (Postfix) with ESMTP id 3A05E11E8290 for <ipv6@ietf.org>; Mon, 28 Oct 2013 10:18:35 -0700 (PDT)
Received: from [66.196.81.161] by nm17.access.bullet.mail.bf1.yahoo.com with NNFMP; 28 Oct 2013 17:18:34 -0000
Received: from [66.196.81.148] by tm7.access.bullet.mail.bf1.yahoo.com with NNFMP; 28 Oct 2013 17:18:34 -0000
Received: from [127.0.0.1] by omp1024.access.mail.bf1.yahoo.com with NNFMP; 28 Oct 2013 17:18:34 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 494279.57474.bm@omp1024.access.mail.bf1.yahoo.com
Received: (qmail 33934 invoked by uid 60001); 28 Oct 2013 17:18:33 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1382980713; bh=rXSK8sW+3/5tdnyY0Sc8auV9s0yAGCkwsuBtqJmFW/A=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=SM4NOdNvVxNHda879K2Amj/aMc01mozea4IvVNWrqYJ06m/lAM+O57tupP91OFQ0Dr3Hb5/2X5KIhq6qvRKfOlxUXV2TWREjtUov2wCnlcFmMycrTCTH/CoFKiA3/dpyYCLXQCjoK1HSDiKd4CDBqAAMCYvLK4gB+EYA/AePKqA=
X-YMail-OSG: USF1x1wVM1lqW_gBckIC_LJIXQA4iP2lj3vtUpC5f.TD5Cv WGZYTTSFbmhu_ifAK2fO6IR3gclr8ESV4X05Z5JsRCOyKYswGVAFJprWvEVo PDZaqsftfM9V_Bf.tN8HDOok51CkgqkpX3WuNC5ENZck3VxRpTBiTEeKaN3I d0fxvLK9nR9nJ6SWrBX.SXbSkudpu63hG3nQTVnoP5IxOot5aIsz_TrOPGJ. qdDES5Qkf1F0qE2vw6mQEnsESYo0wtmPqsfmMRsZNaXArY3S4sxTC.dqN6xw CoAL4.8ERCXWflpMQ2Imd3c.agkJQDbrrh0qL31ARHcCXoqOs0DxZybDNJEH NJjZD3FN1wFGKv_fnicu9XfKI2Nab_QV7mN45QRXMKACed0DmXzDK8azfArw y7oUYFs36TYzJbslMFwgvKY7CN_oMEK_L.YfC2.KQS0BvS2fYmOYTYLMpeba 0HFiy9baTLNqcxxpOIeJ8IDksfpYnfR8RqVqIlrbRlJ0ZWdAMQWchs6bjFdj qiLhKZ2R_020HnmmnM5TjE0qVpFprMhG1v9AZYkQl95qdkfKYI2ybgHywSNF 9PApXtRRXTXIjuRJ3sGYYYPN0Mf02RKDPcH3U3_WgvA7bQGZzN5MlNvtQsaF ed5gThAd35Dql2blZvUu0W0slHsMkgUB04G_59f_swTr7iLyeF0ikiv_3ivh lX8iN
Received: from [24.130.37.147] by web2805.biz.mail.ne1.yahoo.com via HTTP; Mon, 28 Oct 2013 10:18:33 PDT
X-Rocket-MIMEInfo: 002.001, Sm9hY2hpbSwKwqAKVGhhbmtzIHZlcnkgbXVjaC4gwqBXZSB3aWxsIHRha2UgYSBsb29rIGFuZCByZXZpc2UgdGhlIGRyYWZ0cyBhY2NvcmRpbmdseS4KCk5hbGluaSBFbGtpbnMKSW5zaWRlIFByb2R1Y3RzLCBJbmMuCig4MzEpIDY1OS04MzYwCnd3dy5pbnNpZGV0aGVzdGFjay5jb20KCgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KIEZyb206IEpvYWNoaW0gRmFiaW5pIDxKb2FjaGltLkZhYmluaUB0dXdpZW4uYWMuYXQ.ClRvOiAiQWNrZXJtYW5uLCBNaWNoYWVsIiA8TUFja2VybWFubkBiY2IBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.160.587
References: <20131017032024.5051.20799.idtracker@ietfa.amsl.com> <1381980305.36254.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com> <5263C783.1080001@globis.net> <1382396300.22968.YahooMailNeo@web2801.biz.mail.ne1.yahoo.com> <526616C4.40304@globis.net> <4FC37E442D05A748896589E468752CAA0CA88734@PWN401EA160.ent.corp.bcbsm.com> <52695E3A.9090406@globis.net> <4FC37E442D05A748896589E468752CAA0CA8A36F@PWN401EA160.ent.corp.bcbsm.com> <526AAC81.3050402@globis.net> <4FC37E442D05A748896589E468752CAA0CA8B1CD@PWN401EA160.ent.corp.bcbsm.com> <526E936D.1000404@tuwien.ac.at>
Message-ID: <1382980713.24463.YahooMailNeo@web2805.biz.mail.ne1.yahoo.com>
Date: Mon, 28 Oct 2013 10:18:33 -0700 (PDT)
From: Nalini Elkins <nalini.elkins@insidethestack.com>
Subject: Re: [ippm] [v6ops] Fw: New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-04.txt
To: Joachim Fabini <Joachim.Fabini@tuwien.ac.at>, "Ackermann, Michael" <MAckermann@bcbsm.com>, Ray Hunter <v6ops@globis.net>
In-Reply-To: <526E936D.1000404@tuwien.ac.at>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="1619178251-1261008546-1382980713=:24463"
Cc: v6ops WG <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "bill.jouris@insidethestack.com" <bill.jouris@insidethestack.com>, "ippm@ietf.org" <ippm@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Nalini Elkins <nalini.elkins@insidethestack.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: Mon, 28 Oct 2013 17:18:43 -0000

--1619178251-1261008546-1382980713=:24463
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Joachim,=0A=A0=0AThanks very much. =A0We will take a look and revise the dr=
afts accordingly.=0A=0ANalini Elkins=0AInside Products, Inc.=0A(831) 659-83=
60=0Awww.insidethestack.com=0A=0A=0A=0A________________________________=0A =
From: Joachim Fabini <Joachim.Fabini@tuwien.ac.at>=0ATo: "Ackermann, Michae=
l" <MAckermann@bcbsm.com>; Ray Hunter <v6ops@globis.net> =0ACc: v6ops WG <v=
6ops@ietf.org>; 6man WG <ipv6@ietf.org>; "bill.jouris@insidethestack.com" <=
bill.jouris@insidethestack.com>; "ippm@ietf.org" <ippm@ietf.org> =0ASent: M=
onday, October 28, 2013 9:40 AM=0ASubject: Re: [ippm] [v6ops] Fw: New Versi=
on Notification for draft-elkins-6man-ipv6-pdm-dest-option-04.txt=0A =0A=0A=
Mike, Nalini,=0A=0Aplease have a look at http://tools.ietf.org/html/rfc2330=
#section-10 =0Aand/or http://tools.ietf.org/html/rfc5905 for a detailed tec=
hnical =0Adiscussion on time issues/NTP. With respect to these parameters, =
the =0Aterm "in sync" which you use is _purely_ theoretical and must be =0A=
consolidated to a technical specification in terms of RFC2330 clock =0Apara=
meters (accuracy, resolution, etc.) to be usable in practice. I =0Athink th=
is is what Ray meant. Stratum per se (in the NTP sense) is imho =0Amisleadi=
ng/useless as a quality indicator.=0A=0Aregards=0AJoachim=0A=0A=0AAm 28.10.=
2013 17:13, schrieb Ackermann, Michael:=0A> Hey Ray=0A>=0A> It appears your=
 experiences with Time Synch and Stratum levels are different than mine.=A0=
  In the older Telecom and Voice World Stratum was a great indicator of clo=
cking accuracy.=A0  Still is as far as I know.=A0  This was always true wit=
h or without NTP in the picture.=0A> And whenever we had two Stratum 0's or=
 1's, be they the same or different masters, they WOULD be in synch.=A0  We=
 never had a situation that was an exception to that, with or without NTP.=
=0A>=0A> Thanks=0A>=0A> Mike=0A>=0A>=0A> -----Original Message-----=0A> Fro=
m: Ray Hunter [mailto:v6ops@globis.net]=0A> Sent: Friday, October 25, 2013 =
1:38 PM=0A> To: Ackermann, Michael=0A> Cc: Nalini Elkins; v6ops WG; 6man WG=
; ippm@ietf.org; bill.jouris@insidethestack.com; keven.haining@usbank.com=
=0A> Subject: Re: [v6ops] Fw: New Version Notification for draft-elkins-6ma=
n-ipv6-pdm-dest-option-04.txt=0A>=0A>> Ackermann, Michael <mailto:MAckerman=
n@bcbsm.com>=0A>> 25 October 2013 01:44=0A>> Ray=0A>>=0A>> Your Comment:=0A=
>> No. I think what I said was that the level of certainty in your measurem=
ents is dependent on the level of synchronisation of the 2 clock sources if=
 you are calculating a delta of timestamp of clock 1 - timestamp clock 2.=
=0A>> My Response:=0A>> Then it sounds like we are in agreement.=A0  Given =
the appropriate stratum level at both nodes, the desired level of time sync=
hronization is achieved.=0A>>=0A> No. We are not in agreement.=0A>=0A> Stra=
tum is an indication of how far down you are in the hierarchy from any NTP =
Stratum 0 clock.=0A>=0A> It says nothing about whether your stratum 0 and m=
y stratum 0 are synchronised.=0A>=0A> We could both be running caesium cloc=
ks, and there could still be an offset if I don't set my reference time of =
my caesium clock the same as your reference time. When talking about micros=
econd or picosecond timing that will almost certainly be significant.=0A>=
=0A> You really need to know that the true provenance of the clock source i=
s identical in order to make PDM 1 calculations, not just the stratum.=0A>=
=0A> Hence my comment to couple some sort of "clock ID" to the timestamp.=
=0A>> Your Comment:=0A>> I think it might be instructive to go back and loo=
k at high school physics books on making measurements, precision, accuracy,=
 and error estimations, especially when taking the difference of two measur=
ements, or making other calculations on top of raw observations=0A>> My Res=
ponse:=A0 Not sure exactly what this means but I can say that this sounds l=
ike theoretical doubt that time synchronization will not work properly in g=
eographically dispersed environments?=A0 =A0 I can tell you that it does in=
 our experiences and that the surrounding protocols/implementations are cra=
fted to account for such vicissitudes.=0A>> I will say that I have no field=
 experience with DCF-77 sources, only GPS and Cesium.=0A>>=0A>>=0A>> Your C=
omment:=0A>> Equally a stratum 0 clock can be free running if it loses it's=
 radio signal.=0A>> My Response:=0A>> This comment sort of confused me as w=
ell, but suffice to say, if any component is broken, results will be impair=
ed.=A0  Obviously this is not limited to the time synch subject.=0A>>=0A>>=
=0A>> Finally, your comment about "Middleboxes".=A0 =A0 I hope it can be as=
 simple to accommodate as you describe.=A0  My concern is that if there are=
 numerous middleboxes, the fields may get repetitively overlaid, or there w=
ill need to be so many separate fields, we could incur excessive complexity=
 or overhead.=A0 =A0 Given that we can accomplish this with a workable solu=
tion, I am certainly all for it.=0A>> The more information I can have to ma=
nage networks and solve problems, the better!=0A>>=0A>> Thanks again for yo=
ur thoughts, inputs and questions!=0A>>=0A>> Mike=0A>>=0A>>=0A>>=0A>>=0A>>=
=0A>>=0A>>=0A>>=0A>>=0A>>=0A>>=0A>=0A>=0A>=0A> The information contained in=
 this communication is highly confidential and is intended solely for the u=
se of the individual(s) to whom this communication is directed. If you are =
not the intended recipient, you are hereby notified that any viewing, copyi=
ng, disclosure or distribution of this information is prohibited. Please no=
tify the sender, by electronic mail or telephone, of any unintended receipt=
 and delete the original message without making any copies.=0A>=0A>=A0  Blu=
e Cross Blue Shield of Michigan and Blue Care Network of Michigan are nonpr=
ofit corporations and independent licensees of the Blue Cross and Blue Shie=
ld Association.=0A> _______________________________________________=0A> ipp=
m mailing list=0A> ippm@ietf.org=0A> https://www.ietf.org/mailman/listinfo/=
ippm=0A>=0A_______________________________________________=0Aippm mailing l=
ist=0Aippm@ietf.org=0Ahttps://www.ietf.org/mailman/listinfo/ippm
--1619178251-1261008546-1382980713=:24463
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:ar=
ial, helvetica, sans-serif;font-size:12pt"><div><span>Joachim,</span></div>=
<div></div><div>&nbsp;</div><div>Thanks very much. &nbsp;We will take a loo=
k and revise the drafts accordingly.</div><div><br></div><div>Nalini Elkins=
<br>Inside Products, Inc.<br>(831) 659-8360<br>www.insidethestack.com<br></=
div><br>  <div style=3D"font-family: arial, helvetica, sans-serif; font-siz=
e: 12pt;"> <div style=3D"font-family: 'times new roman', 'new york', times,=
 serif; font-size: 12pt;"> <div dir=3D"ltr"> <hr size=3D"1">  <font size=3D=
"2" face=3D"Arial"> <b><span style=3D"font-weight:bold;">From:</span></b> J=
oachim Fabini &lt;Joachim.Fabini@tuwien.ac.at&gt;<br> <b><span style=3D"fon=
t-weight: bold;">To:</span></b> "Ackermann, Michael" &lt;MAckermann@bcbsm.c=
om&gt;; Ray Hunter &lt;v6ops@globis.net&gt; <br><b><span style=3D"font-weig=
ht: bold;">Cc:</span></b> v6ops WG &lt;v6ops@ietf.org&gt;; 6man WG
 &lt;ipv6@ietf.org&gt;; "bill.jouris@insidethestack.com" &lt;bill.jouris@in=
sidethestack.com&gt;; "ippm@ietf.org" &lt;ippm@ietf.org&gt; <br> <b><span s=
tyle=3D"font-weight: bold;">Sent:</span></b> Monday, October 28, 2013 9:40 =
AM<br> <b><span style=3D"font-weight: bold;">Subject:</span></b> Re: [ippm]=
 [v6ops] Fw: New Version Notification for draft-elkins-6man-ipv6-pdm-dest-o=
ption-04.txt<br> </font> </div> <div class=3D"y_msg_container"><br>=0AMike,=
 Nalini,<br><br>please have a look at http://tools.ietf.org/html/rfc2330#se=
ction-10 <br>and/or http://tools.ietf.org/html/rfc5905 for a detailed techn=
ical <br>discussion on time issues/NTP. With respect to these parameters, t=
he <br>term "in sync" which you use is _purely_ theoretical and must be <br=
>consolidated to a technical specification in terms of RFC2330 clock <br>pa=
rameters (accuracy, resolution, etc.) to be usable in practice. I <br>think=
 this is what Ray meant. Stratum per se (in the NTP sense) is imho <br>misl=
eading/useless as a quality indicator.<br><br>regards<br>Joachim<br><br><br=
>Am 28.10.2013 17:13, schrieb Ackermann, Michael:<br>&gt; Hey Ray<br>&gt;<b=
r>&gt; It appears your experiences with Time Synch and Stratum levels are d=
ifferent than mine.&nbsp;  In the older Telecom and Voice World Stratum was=
 a great indicator of clocking accuracy.&nbsp;  Still is as far as I know.&=
nbsp;  This was always true with or without NTP in the
 picture.<br>&gt; And whenever we had two Stratum 0's or 1's, be they the s=
ame or different masters, they WOULD be in synch.&nbsp;  We never had a sit=
uation that was an exception to that, with or without NTP.<br>&gt;<br>&gt; =
Thanks<br>&gt;<br>&gt; Mike<br>&gt;<br>&gt;<br>&gt; -----Original Message--=
---<br>&gt; From: Ray Hunter [mailto:<a ymailto=3D"mailto:v6ops@globis.net"=
 href=3D"mailto:v6ops@globis.net">v6ops@globis.net</a>]<br>&gt; Sent: Frida=
y, October 25, 2013 1:38 PM<br>&gt; To: Ackermann, Michael<br>&gt; Cc: Nali=
ni Elkins; v6ops WG; 6man WG; <a ymailto=3D"mailto:ippm@ietf.org" href=3D"m=
ailto:ippm@ietf.org">ippm@ietf.org</a>; <a ymailto=3D"mailto:bill.jouris@in=
sidethestack.com" href=3D"mailto:bill.jouris@insidethestack.com">bill.jouri=
s@insidethestack.com</a>; <a ymailto=3D"mailto:keven.haining@usbank.com" hr=
ef=3D"mailto:keven.haining@usbank.com">keven.haining@usbank.com</a><br>&gt;=
 Subject: Re: [v6ops] Fw: New Version Notification for
 draft-elkins-6man-ipv6-pdm-dest-option-04.txt<br>&gt;<br>&gt;&gt; Ackerman=
n, Michael &lt;mailto:<a ymailto=3D"mailto:MAckermann@bcbsm.com" href=3D"ma=
ilto:MAckermann@bcbsm.com">MAckermann@bcbsm.com</a>&gt;<br>&gt;&gt; 25 Octo=
ber 2013 01:44<br>&gt;&gt; Ray<br>&gt;&gt;<br>&gt;&gt; Your Comment:<br>&gt=
;&gt; No. I think what I said was that the level of certainty in your measu=
rements is dependent on the level of synchronisation of the 2 clock sources=
 if you are calculating a delta of timestamp of clock 1 - timestamp clock 2=
.<br>&gt;&gt; My Response:<br>&gt;&gt; Then it sounds like we are in agreem=
ent.&nbsp;  Given the appropriate stratum level at both nodes, the desired =
level of time synchronization is achieved.<br>&gt;&gt;<br>&gt; No. We are n=
ot in agreement.<br>&gt;<br>&gt; Stratum is an indication of how far down y=
ou are in the hierarchy from any NTP Stratum 0 clock.<br>&gt;<br>&gt; It sa=
ys nothing about whether your stratum 0 and my stratum 0 are
 synchronised.<br>&gt;<br>&gt; We could both be running caesium clocks, and=
 there could still be an offset if I don't set my reference time of my caes=
ium clock the same as your reference time. When talking about microsecond o=
r picosecond timing that will almost certainly be significant.<br>&gt;<br>&=
gt; You really need to know that the true provenance of the clock source is=
 identical in order to make PDM 1 calculations, not just the stratum.<br>&g=
t;<br>&gt; Hence my comment to couple some sort of "clock ID" to the timest=
amp.<br>&gt;&gt; Your Comment:<br>&gt;&gt; I think it might be instructive =
to go back and look at high school physics books on making measurements, pr=
ecision, accuracy, and error estimations, especially when taking the differ=
ence of two measurements, or making other calculations on top of raw observ=
ations<br>&gt;&gt; My Response:&nbsp; Not sure exactly what this means but =
I can say that this sounds like theoretical doubt that time
 synchronization will not work properly in geographically dispersed environ=
ments?&nbsp; &nbsp; I can tell you that it does in our experiences and that=
 the surrounding protocols/implementations are crafted to account for such =
vicissitudes.<br>&gt;&gt; I will say that I have no field experience with D=
CF-77 sources, only GPS and Cesium.<br>&gt;&gt;<br>&gt;&gt;<br>&gt;&gt; You=
r Comment:<br>&gt;&gt; Equally a stratum 0 clock can be free running if it =
loses it's radio signal.<br>&gt;&gt; My Response:<br>&gt;&gt; This comment =
sort of confused me as well, but suffice to say, if any component is broken=
, results will be impaired.&nbsp;  Obviously this is not limited to the tim=
e synch subject.<br>&gt;&gt;<br>&gt;&gt;<br>&gt;&gt; Finally, your comment =
about "Middleboxes".&nbsp; &nbsp; I hope it can be as simple to accommodate=
 as you describe.&nbsp;  My concern is that if there are numerous middlebox=
es, the fields may get repetitively overlaid, or there will need to
 be so many separate fields, we could incur excessive complexity or overhea=
d.&nbsp; &nbsp; Given that we can accomplish this with a workable solution,=
 I am certainly all for it.<br>&gt;&gt; The more information I can have to =
manage networks and solve problems, the better!<br>&gt;&gt;<br>&gt;&gt; Tha=
nks again for your thoughts, inputs and questions!<br>&gt;&gt;<br>&gt;&gt; =
Mike<br>&gt;&gt;<br>&gt;&gt;<br>&gt;&gt;<br>&gt;&gt;<br>&gt;&gt;<br>&gt;&gt=
;<br>&gt;&gt;<br>&gt;&gt;<br>&gt;&gt;<br>&gt;&gt;<br>&gt;&gt;<br>&gt;<br>&g=
t;<br>&gt;<br>&gt; The information contained in this communication is highl=
y confidential and is intended solely for the use of the individual(s) to w=
hom this communication is directed. If you are not the intended recipient, =
you are hereby notified that any viewing, copying, disclosure or distributi=
on of this information is prohibited. Please notify the sender, by electron=
ic mail or telephone, of any unintended receipt and delete the
 original message without making any copies.<br>&gt;<br>&gt;&nbsp;  Blue Cr=
oss Blue Shield of Michigan and Blue Care Network of Michigan are nonprofit=
 corporations and independent licensees of the Blue Cross and Blue Shield A=
ssociation.<br>&gt; _______________________________________________<br>&gt;=
 ippm mailing list<br>&gt; <a ymailto=3D"mailto:ippm@ietf.org" href=3D"mail=
to:ippm@ietf.org">ippm@ietf.org</a><br>&gt; <a href=3D"https://www.ietf.org=
/mailman/listinfo/ippm" target=3D"_blank">https://www.ietf.org/mailman/list=
info/ippm</a><br>&gt;<br>_______________________________________________<br=
>ippm mailing list<br><a ymailto=3D"mailto:ippm@ietf.org" href=3D"mailto:ip=
pm@ietf.org">ippm@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/l=
istinfo/ippm" target=3D"_blank">https://www.ietf.org/mailman/listinfo/ippm<=
/a><br><br><br></div> </div> </div>  </div></body></html>
--1619178251-1261008546-1382980713=:24463--

From Joachim.Fabini@tuwien.ac.at  Mon Oct 28 09:40:27 2013
Return-Path: <Joachim.Fabini@tuwien.ac.at>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B040B21E80A8; Mon, 28 Oct 2013 09:40:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.13
X-Spam-Level: 
X-Spam-Status: No, score=-5.13 tagged_above=-999 required=5 tests=[AWL=-0.300,  BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pUV1h2jSDlYM; Mon, 28 Oct 2013 09:40:23 -0700 (PDT)
Received: from mail1.zserv.tuwien.ac.at (mail1.zserv.tuwien.ac.at [128.130.35.37]) by ietfa.amsl.com (Postfix) with ESMTP id AFD7421F9E89; Mon, 28 Oct 2013 09:40:22 -0700 (PDT)
Received: from [128.131.88.241] (priamos.ibk.tuwien.ac.at [128.131.88.241]) (authenticated bits=0) by mail1.zserv.tuwien.ac.at (8.13.8/8.13.8) with ESMTP id r9SGeFgY012631 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Oct 2013 17:40:15 +0100
Message-ID: <526E936D.1000404@tuwien.ac.at>
Date: Mon, 28 Oct 2013 17:40:13 +0100
From: Joachim Fabini <Joachim.Fabini@tuwien.ac.at>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: "Ackermann, Michael" <MAckermann@bcbsm.com>, Ray Hunter <v6ops@globis.net>
Subject: Re: [ippm] [v6ops] Fw: New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-04.txt
References: <20131017032024.5051.20799.idtracker@ietfa.amsl.com>	<1381980305.36254.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com>	<5263C783.1080001@globis.net>	<1382396300.22968.YahooMailNeo@web2801.biz.mail.ne1.yahoo.com>	<526616C4.40304@globis.net>	<4FC37E442D05A748896589E468752CAA0CA88734@PWN401EA160.ent.corp.bcbsm.com>	<52695E3A.9090406@globis.net>	<4FC37E442D05A748896589E468752CAA0CA8A36F@PWN401EA160.ent.corp.bcbsm.com>	<526AAC81.3050402@globis.net> <4FC37E442D05A748896589E468752CAA0CA8B1CD@PWN401EA160.ent.corp.bcbsm.com>
In-Reply-To: <4FC37E442D05A748896589E468752CAA0CA8B1CD@PWN401EA160.ent.corp.bcbsm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 28 Oct 2013 10:21:21 -0700
Cc: v6ops WG <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "bill.jouris@insidethestack.com" <bill.jouris@insidethestack.com>, "ippm@ietf.org" <ippm@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 16:40:27 -0000

Mike, Nalini,

please have a look at http://tools.ietf.org/html/rfc2330#section-10 
and/or http://tools.ietf.org/html/rfc5905 for a detailed technical 
discussion on time issues/NTP. With respect to these parameters, the 
term "in sync" which you use is _purely_ theoretical and must be 
consolidated to a technical specification in terms of RFC2330 clock 
parameters (accuracy, resolution, etc.) to be usable in practice. I 
think this is what Ray meant. Stratum per se (in the NTP sense) is imho 
misleading/useless as a quality indicator.

regards
Joachim


Am 28.10.2013 17:13, schrieb Ackermann, Michael:
> Hey Ray
>
> It appears your experiences with Time Synch and Stratum levels are different than mine.   In the older Telecom and Voice World Stratum was a great indicator of clocking accuracy.   Still is as far as I know.   This was always true with or without NTP in the picture.
> And whenever we had two Stratum 0's or 1's, be they the same or different masters, they WOULD be in synch.   We never had a situation that was an exception to that, with or without NTP.
>
> Thanks
>
> Mike
>
>
> -----Original Message-----
> From: Ray Hunter [mailto:v6ops@globis.net]
> Sent: Friday, October 25, 2013 1:38 PM
> To: Ackermann, Michael
> Cc: Nalini Elkins; v6ops WG; 6man WG; ippm@ietf.org; bill.jouris@insidethestack.com; keven.haining@usbank.com
> Subject: Re: [v6ops] Fw: New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-04.txt
>
>> Ackermann, Michael <mailto:MAckermann@bcbsm.com>
>> 25 October 2013 01:44
>> Ray
>>
>> Your Comment:
>> No. I think what I said was that the level of certainty in your measurements is dependent on the level of synchronisation of the 2 clock sources if you are calculating a delta of timestamp of clock 1 - timestamp clock 2.
>> My Response:
>> Then it sounds like we are in agreement.   Given the appropriate stratum level at both nodes, the desired level of time synchronization is achieved.
>>
> No. We are not in agreement.
>
> Stratum is an indication of how far down you are in the hierarchy from any NTP Stratum 0 clock.
>
> It says nothing about whether your stratum 0 and my stratum 0 are synchronised.
>
> We could both be running caesium clocks, and there could still be an offset if I don't set my reference time of my caesium clock the same as your reference time. When talking about microsecond or picosecond timing that will almost certainly be significant.
>
> You really need to know that the true provenance of the clock source is identical in order to make PDM 1 calculations, not just the stratum.
>
> Hence my comment to couple some sort of "clock ID" to the timestamp.
>> Your Comment:
>> I think it might be instructive to go back and look at high school physics books on making measurements, precision, accuracy, and error estimations, especially when taking the difference of two measurements, or making other calculations on top of raw observations
>> My Response:  Not sure exactly what this means but I can say that this sounds like theoretical doubt that time synchronization will not work properly in geographically dispersed environments?    I can tell you that it does in our experiences and that the surrounding protocols/implementations are crafted to account for such vicissitudes.
>> I will say that I have no field experience with DCF-77 sources, only GPS and Cesium.
>>
>>
>> Your Comment:
>> Equally a stratum 0 clock can be free running if it loses it's radio signal.
>> My Response:
>> This comment sort of confused me as well, but suffice to say, if any component is broken, results will be impaired.   Obviously this is not limited to the time synch subject.
>>
>>
>> Finally, your comment about "Middleboxes".    I hope it can be as simple to accommodate as you describe.   My concern is that if there are numerous middleboxes, the fields may get repetitively overlaid, or there will need to be so many separate fields, we could incur excessive complexity or overhead.    Given that we can accomplish this with a workable solution, I am certainly all for it.
>> The more information I can have to manage networks and solve problems, the better!
>>
>> Thanks again for your thoughts, inputs and questions!
>>
>> Mike
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
>
> The information contained in this communication is highly confidential and is intended solely for the use of the individual(s) to whom this communication is directed. If you are not the intended recipient, you are hereby notified that any viewing, copying, disclosure or distribution of this information is prohibited. Please notify the sender, by electronic mail or telephone, of any unintended receipt and delete the original message without making any copies.
>
>   Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are nonprofit corporations and independent licensees of the Blue Cross and Blue Shield Association.
> _______________________________________________
> ippm mailing list
> ippm@ietf.org
> https://www.ietf.org/mailman/listinfo/ippm
>

From sthaug@nethelp.no  Mon Oct 28 10:46:09 2013
Return-Path: <sthaug@nethelp.no>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A019211E819B for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 10:46:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RW7Q9g9AjgMi for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 10:46:04 -0700 (PDT)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by ietfa.amsl.com (Postfix) with SMTP id 0F0AC11E828B for <ipv6@ietf.org>; Mon, 28 Oct 2013 10:45:55 -0700 (PDT)
Received: (qmail 89628 invoked from network); 28 Oct 2013 17:45:53 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 28 Oct 2013 17:45:53 -0000
Date: Mon, 28 Oct 2013 18:45:53 +0100 (CET)
Message-Id: <20131028.184553.78794962.sthaug@nethelp.no>
To: alvarezp@alvarezp.ods.org
Subject: Re: Why /64
From: sthaug@nethelp.no
In-Reply-To: <526E9735.8080708@alvarezp.ods.org>
References: <526CF079.7030804@globis.net> <526E41BC.3080303@gmail.com> <526E9735.8080708@alvarezp.ods.org>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: alexandru.petrescu@gmail.com, ipv6@ietf.org, v6ops@globis.net, tjc@ecs.soton.ac.uk, fred@cisco.com, fgont@si6networks.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 17:46:09 -0000

> > The IPv4's CIDR concept (route based on bitwise borders, instead of
> > 8byte) seems to me a good clue for the discussion about the fix 64bit
> > limit in IPv6.
> 
> CIDR is already being used. /80s, /96s and other arbitrary netmasks can
> be set on some devices and should work. Some of them may misbehave, though.

"Some devices"? They work on all devices I've tried. And I certainly
*expect* normal longest prefix match based forwarding to work, with
no arbitrary /64 limitation. 

The only limitations I've seen are IPv6 ACLs on some Cisco switches,
where the 144 bit wide CAM cannot accomodate a 128 bit IPv6 address
*and* 2 x 16 bit port numbers.

Steinar Haug, AS 2116

From markzzzsmith@yahoo.com.au  Mon Oct 28 12:23:47 2013
Return-Path: <markzzzsmith@yahoo.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72B1211E8297 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 12:23:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level: 
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[AWL=0.220,  BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wCsiDUBlPCPX for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 12:23:42 -0700 (PDT)
Received: from nm13-vm0.bullet.mail.bf1.yahoo.com (nm13-vm0.bullet.mail.bf1.yahoo.com [98.139.213.79]) by ietfa.amsl.com (Postfix) with ESMTP id 6A74511E82BD for <ipv6@ietf.org>; Mon, 28 Oct 2013 12:23:39 -0700 (PDT)
Received: from [98.139.212.144] by nm13.bullet.mail.bf1.yahoo.com with NNFMP; 28 Oct 2013 19:23:38 -0000
Received: from [98.139.212.249] by tm1.bullet.mail.bf1.yahoo.com with NNFMP; 28 Oct 2013 19:23:38 -0000
Received: from [127.0.0.1] by omp1058.mail.bf1.yahoo.com with NNFMP; 28 Oct 2013 19:23:38 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 785343.27876.bm@omp1058.mail.bf1.yahoo.com
Received: (qmail 92714 invoked by uid 60001); 28 Oct 2013 19:23:38 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s1024; t=1382988218; bh=XlEX0vY1/T0uShpjDZPwNkvNQTolVV7F98kdDlzqcqQ=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=qc6O+zO3W1c5ZatgcEruenVBZ1lgZYjsFR7z9sSOCbFKzZbv68VB/oq82QixIjc4bspnW+aUAWJEfBPdLKcwqjFSosrbxgk1kl55NyS9usWufjU//m19sFT1n7nU/hpWovupf3Jq/IFygPWcDhlRCTVK4gctlN1Si3pGGsgTC1Y=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.au; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=NOhzyKB9mANmPnSeEekObMWJOtT6VmiMiTMgeNYDM5wh0KxSqptt03SCpnKNg3MkE5B9dtGQpaypVKje3oK1vGKcEpl/UlTO6+ip+gszcGtfJHiQz159sKL8Oj0xjiaWhywMI89zYiYCF9AdqBPDHhMH9pecCgMRjf+guBRg1ew=;
X-YMail-OSG: hbqU4DUVM1krVNpoRxebUKuU2a3JNB3ir9nFxkX7Uy2hots 6HAubZZob5Ef90f11pZsp7DWVVRHuIyiwc.25umOwoq0Pf6kj0373QiBzL.d WxXSyTha0K8FhWuRznEl8bGbwexa_f8IIC1NRPNc7WrH4gYiRy6hkQqxui5t ctjCkakkPsOENCSAtZLKGpmIz_Y8JVUlBJIAmHadFiMuzngg6D29jiR_1u3q xFU13esDoIxVxl.xaljOC1dDrj0AKtFYkiGoJg4PbJOxJ_bJ.Pt9veK1.oT0 kmcvDHP.9k3keQXShHsc3NUN24nq9aqYU.yvlR6wCdzljLdLKt2HuAszCZV0 TksSe2tN3r5MQc8BemN2U8wo6mkfw9gLH3lMeBWbh_WYvQeQkcgnWSXX1cP7 7bEb6Vw1SkDwWPEREj5SBslLuxlkTEKM18oDl.7G5IPyXZ68xZ6N3P5TQ77O 5T7VOzzBK4N77.sMyWTWh7MBQUvhifuKJPlw4tF0G8uGa7mvNR4RDfPiITpm PISgeIOnILnLgB_Fxr4x6bjYHbe1nUNB6RdScA4TVcqinxywfABWQXMQl_3I NwBDtzJomhwxKdlvhayQr3U2eATj3t9NHlJVjHxQATjA-
Received: from [150.101.221.237] by web142504.mail.bf1.yahoo.com via HTTP; Mon, 28 Oct 2013 12:23:38 PDT
X-Rocket-MIMEInfo: 002.001, CgoKCi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0KPiBGcm9tOiAic3RoYXVnQG5ldGhlbHAubm8iIDxzdGhhdWdAbmV0aGVscC5ubz4KPiBUbzogYWx2YXJlenBAYWx2YXJlenAub2RzLm9yZwo.IENjOiBhbGV4YW5kcnUucGV0cmVzY3VAZ21haWwuY29tOyBpcHY2QGlldGYub3JnOyB2Nm9wc0BnbG9iaXMubmV0OyB0amNAZWNzLnNvdG9uLmFjLnVrOyBmcmVkQGNpc2NvLmNvbTsgZmdvbnRAc2k2bmV0d29ya3MuY29tCj4gU2VudDogVHVlc2RheSwgMjkgT2N0b2JlciAyMDEzIDQ6NDUgQU0KPiBTdWJqZWMBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.160.587
References: <526CF079.7030804@globis.net> <526E41BC.3080303@gmail.com>	<526E9735.8080708@alvarezp.ods.org> <20131028.184553.78794962.sthaug@nethelp.no>
Message-ID: <1382988218.92574.YahooMailNeo@web142504.mail.bf1.yahoo.com>
Date: Mon, 28 Oct 2013 12:23:38 -0700 (PDT)
From: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
Subject: Re: Why /64
To: "sthaug@nethelp.no" <sthaug@nethelp.no>, "alvarezp@alvarezp.ods.org" <alvarezp@alvarezp.ods.org>
In-Reply-To: <20131028.184553.78794962.sthaug@nethelp.no>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "alexandru.petrescu@gmail.com" <alexandru.petrescu@gmail.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "v6ops@globis.net" <v6ops@globis.net>, "tjc@ecs.soton.ac.uk" <tjc@ecs.soton.ac.uk>, "fred@cisco.com" <fred@cisco.com>, "fgont@si6networks.com" <fgont@si6networks.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 28 Oct 2013 19:23:47 -0000

=0A=0A=0A=0A----- Original Message -----=0A> From: "sthaug@nethelp.no" <sth=
aug@nethelp.no>=0A> To: alvarezp@alvarezp.ods.org=0A> Cc: alexandru.petresc=
u@gmail.com; ipv6@ietf.org; v6ops@globis.net; tjc@ecs.soton.ac.uk; fred@cis=
co.com; fgont@si6networks.com=0A> Sent: Tuesday, 29 October 2013 4:45 AM=0A=
> Subject: Re: Why /64=0A> =0A>>  > The IPv4's CIDR concept (route based on=
 bitwise borders, instead =0A> of=0A>>  > 8byte) seems to me a good clue fo=
r the discussion about the fix 64bit=0A>>  > limit in IPv6.=0A>> =0A>>  CID=
R is already being used. /80s, /96s and other arbitrary netmasks can=0A>>  =
be set on some devices and should work. Some of them may misbehave, though.=
=0A> =0A> "Some devices"? They work on all devices I've tried. And I =0A> c=
ertainly=0A> *expect* normal longest prefix match based forwarding to work,=
 with=0A> no arbitrary /64 limitation. =0A>=A0=0A=0AI'd expect it to work t=
oo.=0A=0AI think the difference between IPv6 and other protocols in this ar=
ea is that while it has a longest match rule across the whole address, ther=
e are "soft" rather than hard field boundaries in a portion of the address =
space because they're much easier to deal with operationally, and easier to=
 develop systems to deal with. The longest match rule is there to ensure th=
at if the soft field boundaries end up being incorrect, different soft boun=
daries can be defined in a different portion of the address space, it won't=
 require router upgrades to fix as the move from Classful IPv4 to CIDR did.=
=0A=0APeople like flexibility, but don't seem to think much about the costs=
 it may incur. Flexibility and options creates opportunity for error. It's =
hard to get prefix length wrong when all subnets are /64s and when all of y=
our customers have /48s. If your customers have a mix of /56s and /48s, you=
 now have to manage your space more carefully, costing you time and effort,=
 and over time a few customers may get given the wrong prefix size for thei=
r needs, with the costs of dealing with those error may exceed any savings =
there were in trying to "right size" allocations.=A0Simplicity is usually c=
heaper and more robust.=0A=0A> The only limitations I've seen are IPv6 ACLs=
 on some Cisco switches,=0A> where the 144 bit wide CAM cannot accomodate a=
 128 bit IPv6 address=0A> *and* 2 x 16 bit port numbers.=0A> =0A> Steinar H=
aug, AS 2116=0A> =0A> -----------------------------------------------------=
---------------=0A> IETF IPv6 working group mailing list=0A> ipv6@ietf.org=
=0A> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6=0A=
> --------------------------------------------------------------------=0A> 

From alvarezp@alvarezp.ods.org  Mon Oct 28 12:41:10 2013
Return-Path: <alvarezp@alvarezp.ods.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2295621F95D0 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 12:41:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 57UVurxrQYzq for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 12:41:09 -0700 (PDT)
Received: from sobre.alvarezp.com (sobre.alvarezp.com [IPv6:2600:3c01::f03c:91ff:fe96:8fec]) by ietfa.amsl.com (Postfix) with ESMTP id 5456C21F93B9 for <ipv6@ietf.org>; Mon, 28 Oct 2013 12:41:06 -0700 (PDT)
Received: from [10.8.4.35] (unknown [201.139.192.242]) by sobre.alvarezp.com (Postfix) with ESMTPSA id 5D81D613D; Mon, 28 Oct 2013 15:41:05 -0400 (EDT)
Message-ID: <526EBDD0.4050600@alvarezp.ods.org>
Date: Mon, 28 Oct 2013 12:41:04 -0700
From: Octavio Alvarez <alvarezp@alvarezp.ods.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: Jeroen Massar <jeroen@massar.ch>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com>	<526AACA5.7090604@si6networks.com>	<E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<526AC8AF.4060608@si6networks.com>	<8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com>	<CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com>	<526CDC59.4070204@massar.ch>	<CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com>	<CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com> <CAKFn1SG1PC_kA-pO5Or8VyeaOzvLfpmQe0LiiYkXU_HzNqGzCQ@mail.gmail.com> <526E250E.5050607@massar.ch> <526E9517.1090207@alvarezp.ods.org> <526E995D.1000502@massar.ch>
In-Reply-To: <526E995D.1000502@massar.ch>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 19:41:10 -0000

On 28/10/13 10:05, Jeroen Massar wrote:
> On 2013-10-28 17:47 , Octavio Alvarez wrote:
>> On 10/28/2013 01:49 AM, Jeroen Massar wrote:
>>> On 2013-10-27 15:50, Roger Jørgensen wrote:
>>> [..]
>>>> Privacy isn't just one single thing. That the user might lose privacy
>>>> elsewhere in the entire stack that make up Internet, that's NOT an
>>>> argument to give up /64 because we have lost privacy anyhow.
>>>
>>> I am NOT arguing that a /64 should go the way of the dodo.
>>> I am only stating that this "IPv6 Privacy Address" thing is a myth.
>>
>> Which is also inaccurate, as the purpose is not to provide privacy, but
>> just to prevent anti-privacy through the IPv6 address.
>
> Please explain this "anti-privacy" concept.

Made up word, as in "explicitly not privacy". It's not the same "this 
address will not make it as easy for a tracker to track me at least in 
some applications but it is possible if you try hard enough and it will 
cost some more resources to the tracker" than "here you go, it's me and 
you even know what brand of NIC I'm using".

Also, Web != Internet.

>> It's difficult to choose the right words for this.
>
> You mean that it is difficult to justify randomizing bits as it does not
> solve the problem at hand: you can and will be tracked.
>
>  From the intro of RFC4941:
> ----
>     Changing the interface
>     identifier (and the global scope addresses generated from it) over
>     time makes it more difficult for eavesdroppers and other information
>     collectors to identify when different addresses used in different
>     transactions actually correspond to the same node."
> ----
 >
> As it states 'more difficult'. Since 2001 (RFC3041 which has the same
> wording and intent) this kind of tracking tech and the compute power has
> advanced enough though that the difficulty is futile.

Under that logic, punching a hole on my house roof with a drill is just 
more difficult than opening a door, and given a drill is easy to buy and 
not so expensive for people that want, let's all leave our doors 
unlocked and open.

I *also think*, however, that changing address without restarting all 
connections just nullifies the effect of any changing-address privacy 
extension.

I'm not a pro-removing-EUI-64-device-IDs, I'm just saying that 
randomizing bits does something helpful.

From stig@venaas.com  Mon Oct 28 12:49:47 2013
Return-Path: <stig@venaas.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D58B111E80E7; Mon, 28 Oct 2013 12:49:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.016
X-Spam-Level: 
X-Spam-Status: No, score=-102.016 tagged_above=-999 required=5 tests=[AWL=0.283, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nrn8xtyuh9Dl; Mon, 28 Oct 2013 12:49:47 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id 9958C11E8153; Mon, 28 Oct 2013 12:49:46 -0700 (PDT)
Received: from [10.33.12.93] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id 54307802A; Mon, 28 Oct 2013 20:49:44 +0100 (CET)
Message-ID: <526EBFD2.50806@venaas.com>
Date: Mon, 28 Oct 2013 12:49:38 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>,  "Ralph Droms (rdroms)" <rdroms@cisco.com>
Subject: Re: draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re: [Roll] [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope value of 3 - subnet-local)
References: <3599.1381852752@sandelman.ca> <CE82BA46.24343%d.sturek@att.net>	<CABOxzu2nLuny5uySEEdb6ji9ucE6xqGZ6DLe-mc6KUqVszNfFg@mail.gmail.com>	<525DC6C9.2010808@gridmerge.com>	<CABOxzu2apwBRpU1h4mKJwpO+U+Y9Q_q-h5AhZ+hGzAdjdPdmUQ@mail.gmail.com>	<525E5064.4050109@gridmerge.com>	<CABOxzu0L-EY0iDGpAJ+ER15CPL-3v8F77ewn-G=gZYODixevZg@mail.gmail.com>	<3CC8783F-F4DA-47B9-A051-DBBA6EF00C19@gmail.com>	<4518F39EB578034D8C99A9B7776CDBA301C067D0@xmb-aln-x04.cisco.com>	<1daea916972b4e60be575e5f5276cb78@BY2PR03MB269.namprd03.prod.outlook.com>	<4518F39EB578034D8C99A9B7776CDBA301C06DD6@xmb-aln-x04.cisco.com> <CAJE_bqcyWMYw4NHS8xMu+JtWQwV8t97Lcf0BzC1Qe0zgmR4aMQ@mail.gmail.com>
In-Reply-To: <CAJE_bqcyWMYw4NHS8xMu+JtWQwV8t97Lcf0BzC1Qe0zgmR4aMQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Routing Over Low power and Lossy networks <roll@ietf.org>, "6man@ietf.org" <6man@ietf.org>, Dave Thaler <dthaler@microsoft.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 19:49:48 -0000

Hi

On 10/28/2013 9:46 AM, ç¥žæ˜Žé�”å“‰ wrote:
> At Fri, 25 Oct 2013 20:44:57 +0000,
> "Ralph Droms (rdroms)" <rdroms@cisco.com> wrote:
>
>>>>    NEW:
>>>>
>>>>          Interface-Local, Link-Local, and Realm-Local scope boundaries
>>>>          are automatically derived from physical connectivity or
>>>>          other, non-multicast related configuration.  Global scope has
>>>>          no boundary.  The boundaries of all other non-reserved scopes
>>>>          are administratively configured.
>>>
>>> I disagree with the last sentence above.  Specifically
>>> "non-reserved" should be removed.  That is, we should not start
>>> precluding admin configuration of reserved scopes, given we didn't
>>> before.  They just didn't have defined names or uses, but they could
>>> have been used within private environments.
>>
>> Good catch.  So the last sentence should read:
>>
>>    The boundaries of all other scopes are administratively configured.
>
> First off, whether we include "non-reserved" or not, we should clarify
> this only applies to admin-local or larger.  So, e.g.
>
>     The boundaries of all other scopes of Admin-Local or larger are
>     administratively configured.
>
> Secondly, I don't think the "NEW" text (necessarily) precludes admin
> configuration of reserved scopes (in this context it specifically
> means scope 15).  With "non-reserved", I meant it specifically means
> scopes # 5-13.  It intended to not say about scope #15, rather than
> preclude admin configuration for it.  On the other hand, the suggested
> revised version  explicitly states that the boundaries of scope #15
> are administratively configured.  I don't know if that's what this
> scope was supposed to be.  If it was, then this version is okay.  If
> not, and if the "NEW" version was confusing, I suggest:
>
>    The boundaries of all other non-reserved scopes of Admin-Local or
>    larger are administratively configured.  For reserved scopes, the
>    way of configuring their boundaries will be defined when the
>    semantics of the scope is defined.

I think this text might be fine. The main thing I want to say is that
manual configuration of unassigned scopes is fine (as long as not
reserved). But I don't think we want anyone to use reserved scopes in
any way. Scope #14 is global and I don't think we have a meaningful
way of using #15.

Stig

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


From rogerj@gmail.com  Mon Oct 28 14:28:23 2013
Return-Path: <rogerj@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CAAF11E82B5 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 14:28:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.287
X-Spam-Level: 
X-Spam-Status: No, score=-2.287 tagged_above=-999 required=5 tests=[AWL=0.013,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x2MwqzEOESml for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 14:28:22 -0700 (PDT)
Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 5DC9811E82BC for <ipv6@ietf.org>; Mon, 28 Oct 2013 14:28:19 -0700 (PDT)
Received: by mail-wi0-f171.google.com with SMTP id f4so349471wiw.4 for <ipv6@ietf.org>; Mon, 28 Oct 2013 14:28:18 -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 :cc:content-type:content-transfer-encoding; bh=mORHwZmtLfDahf2baRNaU3qCTjAF8Bo2gQLKcq0ntzk=; b=brEWWtF0PVcRheKsd8wsf06S9JHNe3IhCtBfzUaqS346a9jibr7QNqjN/b3eeblnH5 OvgT/8Gon1eYHZmqpaj9+swkjdsXShRnoAB6AnskGvIu2TOViqwyLK1guKB7unTryQye lBoCJI3lMrkyQJUGBuzNecdNjN3AO1vFotbY63YCEIRegWaruklYTVEBcicLIkmJpJzk FzohKfuX6Vy63hZfBSCQvKNtLrH9NpPkkD8DUEbwkaU4iDTxQAhWo8/9JRfhBTXRpiAT mJF9gRMy7+ESrMc7Nk+mfGjhKgXYwiBRHjYj916MvR2oVFt3h87Jb+l/F8PF7LJ+ChI0 xrZQ==
MIME-Version: 1.0
X-Received: by 10.180.36.105 with SMTP id p9mr10957178wij.2.1382995698414; Mon, 28 Oct 2013 14:28:18 -0700 (PDT)
Received: by 10.216.213.72 with HTTP; Mon, 28 Oct 2013 14:28:18 -0700 (PDT)
In-Reply-To: <526E9517.1090207@alvarezp.ods.org>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com> <CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com> <CAKFn1SG1PC_kA-pO5Or8VyeaOzvLfpmQe0LiiYkXU_HzNqGzCQ@mail.gmail.com> <526E250E.5050607@massar.ch> <526E9517.1090207@alvarezp.ods.org>
Date: Mon, 28 Oct 2013 22:28:18 +0100
Message-ID: <CAKFn1SFrcoD45WAHS3fRiA3Jz=4MR6hpMEaxOPEvo_h2s_oRGg@mail.gmail.com>
Subject: Re: Why /64
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: Octavio Alvarez <alvarezp@alvarezp.ods.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 21:28:23 -0000

On Mon, Oct 28, 2013 at 5:47 PM, Octavio Alvarez
<alvarezp@alvarezp.ods.org> wrote:
> On 10/28/2013 01:49 AM, Jeroen Massar wrote:
>> On 2013-10-27 15:50, Roger J=F8rgensen wrote:
>> [..]
>>> Privacy isn't just one single thing. That the user might lose privacy
>>> elsewhere in the entire stack that make up Internet, that's NOT an
>>> argument to give up /64 because we have lost privacy anyhow.
>>
>> I am NOT arguing that a /64 should go the way of the dodo.
>> I am only stating that this "IPv6 Privacy Address" thing is a myth.
>
> Which is also inaccurate, as the purpose is not to provide privacy, but
> just to prevent anti-privacy through the IPv6 address.
>
> It's difficult to choose the right words for this.

I think you are quite right on that one. Privacy isn't really PRIVACY,
it's more about trying not to reveal Everything there is about whoever
is using whatever IP, however that IP is "created". Call it EUI-64,
"IPv6 privacy" or whatever.
None of them really provide 100% privacy, they are all just a bit
better than none, even EUI-64 has some... Which is the point isn't it?



--=20

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

From acooper@cdt.org  Mon Oct 28 15:40:36 2013
Return-Path: <acooper@cdt.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D14B11E81B5 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 15:40:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.658
X-Spam-Level: 
X-Spam-Status: No, score=-102.658 tagged_above=-999 required=5 tests=[AWL=-0.059, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UAkPDy7Vm5vd for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 15:40:08 -0700 (PDT)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by ietfa.amsl.com (Postfix) with ESMTP id 0112B21F9E01 for <ipv6@ietf.org>; Mon, 28 Oct 2013 15:40:05 -0700 (PDT)
X-Footer: Y2R0Lm9yZw==
Received: from localhost ([127.0.0.1]) by mail.maclaboratory.net (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Mon, 28 Oct 2013 18:40:01 -0400
Content-Type: multipart/signed; boundary="Apple-Mail=_4A2F9B0F-650F-4B80-81BD-21D3A6F2EF5F"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification	for draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
From: Alissa Cooper <acooper@cdt.org>
In-Reply-To: <001101ced0e5$fc380120$f4a80360$@rozanak.com>
Date: Mon, 28 Oct 2013 15:39:59 -0700
Message-Id: <435088E6-5DB8-42F4-8A92-1DE8F40009DD@cdt.org>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <001101ced0e5$fc380120$f4a80360$@rozanak.com>
To: Hosnieh Rafiee <ietf@rozanak.com>
X-Mailer: Apple Mail (2.1499)
Cc: ipv6@ietf.org, 'Fernando Gont' <fernando@gont.com.ar>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 22:40:39 -0000

--Apple-Mail=_4A2F9B0F-650F-4B80-81BD-21D3A6F2EF5F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi Hosnieh,

Assuming this is the relevant text from your draft, I will try to give =
my interpretation of it and how it differs from the recommendations in =
draft-gont:

"Step 3 in Section 3.3 of RFC 4941MUST be ignored. When a node uses
   the mechanism explained in this document to generate an IID, it MUST
   not use any other IID generation approaches that are based on MAC
   addresses (RFC 4862) for either temporary or non temporary IID
   generation. The node MIGHT use the algorithm explained in
   [StableAddresses] for the generation of a public address that does
   not make use of EUI-64 or the MAC address for public (global)
   addresses."

1. The implication of the first sentence is that a node that creates a =
public address as described in 4862 MUST NOT create a temporary address =
as specified in 4941.

2. There is no recommendation as to whether or when to use the mechanism =
you specify in ra-privacy, but the second sentence says that when a node =
uses that mechanism, it MUST NOT (assuming you meant for the "not" to =
have 2119 meaning) use any IID-generation mechanism based on a MAC =
address.

3. The third sentence is editorial because MIGHT is not a 2119 keyword.

The combination of the three statements above is rather different from =
the recommendations made in =
draft-gont-6man-deprecate-eui64-based-addresses. In draft-gont, we say:

  "Nodes MUST NOT employ IPv6 address generation schemes that embed the
   underlying hardware address in the Interface Identifier.  Namely,
   nodes MUST NOT generate Interface Identifiers with the schemes
   specified in [RFC2464], [RFC2467], and [RFC2470].

   Nodes SHOULD implement and employ
   [I-D.ietf-6man-stable-privacy-addresses] as the default scheme for
   generating stable IPv6 addresses with SLAAC."

Thus we do not speak to temporary addresses, we deprecate the use of =
hardware identifiers in IIDs, and we recommend the use of the mechanism =
of stable-privacy-addresses when a stable address is needed. Of course =
there has been some discussion about whether these normative =
recommendations are the right ones and whether making them is worthwhile =
and that discussion should continue, but in any event the two drafts' =
recommendations appear to be rather different.

I am also bought in to the idea that if some recommendation is to be =
made about use of hardware identifiers in IIDs, it should be in a simple =
stand-alone draft.

Hope this helps,
Alissa

On Oct 24, 2013, at 11:22 AM, Hosnieh Rafiee <ietf@rozanak.com> wrote:

> Hi,
>=20
> I guess you also included the section regarding ra-privacy draft in =
this
> draft.  Are you going to merge my draft with yours?=20
>=20
> @Alissia: Did I missed something? I guess we discussed to keep this in =
my
> draft (the email that Ole and others were also included)
>=20
> I am not totally disagree with deprecating the use of EUI-64 but I =
would
> like to clarify the status of my draft that was active for some =
months.
> Thanks,
>=20
> -----------smile----------
> Hosnieh
> . success is a journey, not a destination..
> You cannot change your destination overnight, but you can change your
> direction ... Focus on the journey
>=20
>=20
> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf =
Of
> Fernando Gont
> Sent: Thursday, October 24, 2013 7:50 PM
> To: 6man@ietf.org
> Cc: draft-gont-6man-deprecate-eui64-based-addresses@tools.ietf.org
> Subject: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version
> Notification for =
draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
>=20
> Folks,
>=20
> We have posted a new I-D entitled "Deprecating EUI-64 Based IPv6 =
Addresses"
> =
(http://www.ietf.org/internet-drafts/draft-gont-6man-deprecate-eui64-based=
-a
> ddresses-00.txt).
>=20
> It's a spin-off of the work we've been doing on IPv6 addressing
> secuity/privacy considerations
> (draft-ietf-6man-ipv6-address-generation-privacy and
> draft-ietf-6man-stable-privacy-addresses), and the idea had already =
been
> discussed among several folks mstly off-list and at IETF meeting =
corridors.
>=20
> Any comments will be appreciated.
>=20
> Thanks!
>=20
> Best regards,
> Fernando
>=20
>=20
>=20
>=20
> -------- Original Message --------
> Subject: New Version Notification for
> draft-gont-6man-deprecate-eui64-based-addresses-00.txt
> Date: Mon, 21 Oct 2013 15:43:46 -0700
> From: internet-drafts@ietf.org
> To: Fernando Gont <fgont@si6networks.com>, Will Liu
> <liushucheng@huawei.com>, Alissa Cooper <acooper@cdt.org>, Dave Thaler
> <dthaler@microsoft.com>
>=20
>=20
> A new version of I-D, =
draft-gont-6man-deprecate-eui64-based-addresses-00.txt
> has been successfully submitted by Fernando Gont and posted to the =
IETF
> repository.
>=20
> Filename:	 draft-gont-6man-deprecate-eui64-based-addresses
> Revision:	 00
> Title:		 Deprecating EUI-64 Based IPv6 Addresses
> Creation date:	 2013-10-22
> Group:		 Individual Submission
> Number of pages: 6
> URL:
> =
http://www.ietf.org/internet-drafts/draft-gont-6man-deprecate-eui64-based-=
ad
> dresses-00.txt
> Status:
> =
http://datatracker.ietf.org/doc/draft-gont-6man-deprecate-eui64-based-addr=
es
> ses
> Htmlized:
> =
http://tools.ietf.org/html/draft-gont-6man-deprecate-eui64-based-addresses=
-0
> 0
>=20
>=20
> Abstract:
>   Stateless Address Autoconfiguration (SLAAC) for IPv6 typically
>   results in hosts configuring one or more stable addresses composed =
of
>   a network prefix advertised by a local router, and an Interface
>   Identifier that typically embeds a hardware address (e.g., an IEEE
>   LAN MAC address).  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 scheme to mitigate these issues.
>   This document deprecates the use of hardware addresses in IPv6
>   Interface Identifiers, and recommends the use of an alternative
>   scheme ([I-D.ietf-6man-stable-privacy-addresses]) for the generation
>   of IPv6 stable addresses.
>=20
>=20
>=20
>=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
> The IETF Secretariat
>=20
>=20
>=20
>=20
>=20
> --
> Fernando Gont
> e-mail: fernando@gont.com.ar || fgont@si6networks.com PGP Fingerprint: =
7809
> 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
>=20
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20
>=20


--Apple-Mail=_4A2F9B0F-650F-4B80-81BD-21D3A6F2EF5F
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-----

iQEcBAEBAgAGBQJSbue/AAoJEIXyHQftqgBQs+sIAJv4+sGjIjl27ICRniSFdZpB
b3UVrZC0AtmIrUnGwyZTqB95IGw3Og9Vlh93dgeeRkKhlMScB+0CqVtQHbklW5/c
TjLGnli3E/SbZunrF3CmCeP5l3UZToFr6/pxAGXvAEbGPAcDcpYxTgpf932rcVkx
0f7eoqhCfWh0rth3w6JPOnwXO1ZV6RU3QY6PZOpOtSno+Y0pltCOe7YtTF6BX3mP
SqFmr6+nqQdj0ijuFCQoHeZfOq4/uv0+euPdtvkgoDX9+KWEpS17RtDsMLEjhxSK
1s8MIo7lfLxrunRq3a3Xi/SObz8SHIeoZlFj418xJOghIcQTCQexuwVJ50aSjJ8=
=gTE5
-----END PGP SIGNATURE-----

--Apple-Mail=_4A2F9B0F-650F-4B80-81BD-21D3A6F2EF5F--


From acooper@cdt.org  Mon Oct 28 15:42:23 2013
Return-Path: <acooper@cdt.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4A1321E80EC for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 15:42:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.506
X-Spam-Level: 
X-Spam-Status: No, score=-102.506 tagged_above=-999 required=5 tests=[AWL=-0.207, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Svz1Q278Apoa for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 15:42:14 -0700 (PDT)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by ietfa.amsl.com (Postfix) with ESMTP id 7BB0811E820F for <ipv6@ietf.org>; Mon, 28 Oct 2013 15:40:30 -0700 (PDT)
X-Footer: Y2R0Lm9yZw==
Received: from localhost ([127.0.0.1]) by mail.maclaboratory.net (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Mon, 28 Oct 2013 18:40:16 -0400
Content-Type: multipart/signed; boundary="Apple-Mail=_A0561349-B482-429D-B0FD-2A9941E36DBE"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Tracking and correlation properties of IIDs (was Re: Why /64)
From: Alissa Cooper <acooper@cdt.org>
In-Reply-To: <CAKFn1SFrcoD45WAHS3fRiA3Jz=4MR6hpMEaxOPEvo_h2s_oRGg@mail.gmail.com>
Date: Mon, 28 Oct 2013 15:40:15 -0700
Message-Id: <FD89F576-FBBA-40AE-8AA7-F98A2AA3A25B@cdt.org>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com> <CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com> <CAKFn1SG1PC_kA-pO5Or8VyeaOzvLfpmQe0LiiYkXU_HzNqGzCQ@mail.gmail.com> <526E250E.5050607@massar.ch> <526E9517.1090207@alvarezp.ods.org> <CAKFn1SFrcoD45WAHS3fRiA3Jz=4MR6hpMEaxOPEvo_h2s_oRGg@mail.gmail.com>
To: =?iso-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 22:42:23 -0000

--Apple-Mail=_A0561349-B482-429D-B0FD-2A9941E36DBE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

On Oct 28, 2013, at 2:28 PM, Roger J=F8rgensen <rogerj@gmail.com> wrote:

> On Mon, Oct 28, 2013 at 5:47 PM, Octavio Alvarez
> <alvarezp@alvarezp.ods.org> wrote:
>> On 10/28/2013 01:49 AM, Jeroen Massar wrote:
>>> On 2013-10-27 15:50, Roger J=F8rgensen wrote:
>>> [..]
>>>> Privacy isn't just one single thing. That the user might lose =
privacy
>>>> elsewhere in the entire stack that make up Internet, that's NOT an
>>>> argument to give up /64 because we have lost privacy anyhow.
>>>=20
>>> I am NOT arguing that a /64 should go the way of the dodo.
>>> I am only stating that this "IPv6 Privacy Address" thing is a myth.
>>=20
>> Which is also inaccurate, as the purpose is not to provide privacy, =
but
>> just to prevent anti-privacy through the IPv6 address.
>>=20
>> It's difficult to choose the right words for this.
>=20
> I think you are quite right on that one. Privacy isn't really PRIVACY,
> it's more about trying not to reveal Everything there is about whoever
> is using whatever IP, however that IP is "created". Call it EUI-64,
> "IPv6 privacy" or whatever.

It does seem like the discussion over on that other thread devolved =
because of semantics a bit. This is part of the reason why we use =
terminology very carefully in =
draft-ietf-6man-ipv6-address-generation-privacy to discuss the threats =
against different mechanisms for IID generation, and even to name the =
mechanisms themselves. It's unfortunate that RFC 4941 is called "privacy =
extensions" and that folks call the associated addresses "privacy =
addresses"; in the above-referenced draft we call them "temporary =
addresses" for a reason -- they are temporary. No claims that they =
provide 100% anonymity at all times are thereby attached.

If this discussion continues, it might help if folks referenced the =
specific properties vis a vis correlation and tracking that a particular =
IID generation mechanism provides, rather than focusing on "privacy" as =
some sort of binary state that a user either has or doesn't have.

Alissa=20

> None of them really provide 100% privacy, they are all just a bit
> better than none, even EUI-64 has some... Which is the point isn't it?
>=20
>=20
>=20
> --=20
>=20
> Roger Jorgensen           | ROJO9-RIPE
> rogerj@gmail.com          | - IPv6 is The Key!
> http://www.jorgensen.no   | roger@jorgensen.no
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20


--Apple-Mail=_A0561349-B482-429D-B0FD-2A9941E36DBE
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-----

iQEcBAEBAgAGBQJSbufPAAoJEIXyHQftqgBQo84H/RI1k3SmjxLm6MPQP8TjAOxS
Svhm2T5j+SP2z9Td7jbO5AJXHVe5sv+X2wdb/YgDOhNh0aekHGX+jZYWLCeMwa3w
uqnM8JPMySpJy+dReldHUtdqJj3c2CrB81nb+PuXARjSxWTAIslw2twX2BCdzDth
AG3xDuPFBjLmgAFjiRjcEORzJojVHzS7aLYbvGN/NKNOvWFBYvejOzEGQZvbbkOr
uqC2xdbZaljRcazpGbG1mrtJHJSIBcEqbYpKZAE5/pNroC//HTRNTTbmr22aB150
pmbL0aLscIXeRFrl/gBmWJV5OqgL6MfeNlGe05HNO1LNGLgs9EyIh6pHnrS75y8=
=Yza6
-----END PGP SIGNATURE-----

--Apple-Mail=_A0561349-B482-429D-B0FD-2A9941E36DBE--


From fernando@gont.com.ar  Mon Oct 28 15:59:22 2013
Return-Path: <fernando@gont.com.ar>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B19F121E80B7 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 15:59:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_ABOUTYOU=0.5, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GLE2o447Xee5 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 15:59:22 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 434AE11E8152 for <ipv6@ietf.org>; Mon, 28 Oct 2013 15:59:07 -0700 (PDT)
Received: from [2001:13c7:7003:89:50c6:8049:8463:836e] by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fernando@gont.com.ar>) id 1Vavlz-00013a-N1; Mon, 28 Oct 2013 23:58:59 +0100
Message-ID: <526EEC30.6010709@gont.com.ar>
Date: Mon, 28 Oct 2013 18:58:56 -0400
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Hosnieh Rafiee <ietf@rozanak.com>, 'Fernando Gont' <fernando@gont.com.ar>, Alissa Cooper <acooper@cdt.org>
Subject: Re: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification for draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar> <001101ced0e5$fc380120$f4a80360$@rozanak.com>
In-Reply-To: <001101ced0e5$fc380120$f4a80360$@rozanak.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 22:59:22 -0000

Hosnieh,

On 10/24/2013 02:22 PM, Hosnieh Rafiee wrote:
> 
> I guess you also included the section regarding ra-privacy draft in this
> draft.  Are you going to merge my draft with yours? 

To be quite honest, I'm not sure what you mean. But before juping to the
specifics of this I-D we've published, let me clarify some bits about
this topic:

1) I authored draft-gont-6man-stable-privacy-addresses in 2011. At the
time, that I-D was meant to deprecate Modified EUI-64 IIDs. During the
process of wg adoption, it was seen as a better approach to have this
I-D just propose the algorithm, rather than have it deprecate EUI-64...
hence the deprecation was eventually removed.

2) In a similar way, draft-ietf-6man-stable-privacy-addresses used to
contain a threat assessment -- notably improved in response to Alissa's
feedback (during WGLC or IETF LC, IIRC). Eventually, this threat
assessment was removed (since, among other things, it was a whole topic
by itself).


"2)" later resulted in a stand-alone document... and, more recently, so
did "1)".


draft-gont-6man-deprecate-eui64-based-addresses-00.txt borrows text from
stable-privacy and from Alissa's I-D -- that's how Will and me produced
the initial -00 version, which was later discussed and edited with the
other co-authors before publication.


Now, if asked about the specifics (and having just taken a look at your
document), -- and assuming this is the part you're referring to -- your
document says:

>    Step 3 in Section 3.3 of RFC 4941 MUST be ignored. When a node uses
>    the mechanism explained in this document to generate an IID, it MUST
>    not use any other IID generation approaches that are based on MAC
>    addresses ( RFC 4862) for either temporary or non temporary IID
>    generation.

This text does not deprecate Modified EUI-64. It rather provides an
optional alternative to generating IIDs.

Besides, Section 3 of
<http://tools.ietf.org/html/draft-gont-6man-stable-privacy-addresses-00>
(dated December *2011*) contains this text:

  > IPv6 implementations conforming to this specification MUST generate
  > interface identifiers with the algorithm specified in this section.
  > The aforementioned algorithm MUST be employed for generating the
  > interface identifiers for all the IPv6 addresses configured with
  > SLAAC for a given interface, including IPv6 link-local addresses.

.. which pretty much reads like the text in your I-D ("MUST NOT use
EUI-64 *when this algorithm is employed*")...

So I'm rather curious about your suggestion of "plagiarism" on our side,
I should say.


>    The node MIGHT use the algorithm explained in
>    [StableAddresses] for the generation of a public address that does
>    not make use of EUI-64 or the MAC address for public (global)
>    addresses.

FWIW, our document recommends draft-ietf-6man-stable-privacy-addresses,
rather than listing it as one possible option.

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 ietf@rozanak.com  Tue Oct 29 00:53:59 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7B6511E8193 for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 00:53:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_ABOUTYOU=0.5, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J3dD1P7eU88A for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 00:53:54 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id C200411E8121 for <ipv6@ietf.org>; Tue, 29 Oct 2013 00:53:45 -0700 (PDT)
Received: from oxuslxltgw07.lxa.perfora.net (oxuslxltgw07.lxa.perfora.net [172.19.206.9]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0MAP10-1VPTXq1cde-00BcxM; Tue, 29 Oct 2013 03:53:40 -0400
Date: Tue, 29 Oct 2013 03:53:40 -0400 (EDT)
From: Hosnieh <ietf@rozanak.com>
To: Alissa Cooper <acooper@cdt.org>, Fernando Gont <fernando@gont.com.ar>
Message-ID: <373361003.202110.1383033220363.open-xchange@email.1and1.com>
In-Reply-To: <526EEC30.6010709@gont.com.ar>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar> <001101ced0e5$fc380120$f4a80360$@rozanak.com> <526EEC30.6010709@gont.com.ar>
Subject: Re: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification for draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_202109_666086274.1383033220323"
X-Priority: 3
Importance: Medium
X-Mailer: Open-Xchange Mailer v7.2.2-Rev25
X-Provags-ID: V02:K0:QzjP7RIsPqnEKpOGPKziHPxFpBOe/TTM7XukA1Gn0cB Eap6oI3vpz6OUWXPkMmj1X8yAtI5T4FMZbe86ZEFleawakgf3U eD0W21us0w3MObz8Cjp/rqocD/ff0021ZCN9DuyAqIe/TvoQ6n AnmCwH1Ujg9BBGVaqhDnqbJUOIraKwWMJR7B1AdOeWEOFLsahy KrbDtQP5uhMuhe2wIHCECtnKKfhG6EKRDl4xhVErpLJ5Iylrx/ AniYEQTfcCUdwLx2nkk0VoZYDDJa4ByGdUNKKrX9ohjRAT+Wek U6iPT1DrtEnOUyYcChmzPr6xYKPhDyhqQc8XoX02I3jfMksq5l 1lQBgZ8Q/0ltZJb2jq0MmcXGBDap8ryx8ROypu4oLtH+Y7ih9b iB3+EzbMDuJqYqlfX1JMm0vhqBBw/ajVwxZoZPeftH0QUp2Vr2 9F4Qf
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Hosnieh <ietf@rozanak.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, 29 Oct 2013 07:53:59 -0000

------=_Part_202109_666086274.1383033220323
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Fernando,


> So I'm rather curious about your suggestion of "plagiarism" on our side,
> I should say.
>

That section of the draft in ra-privacy also says not to use EUI-64 as both
temporary and public addresses. This section is not new and you can find it in
early versions of ra-privacy as well because it was one of the problem of RFC
4941. Your draft expands this section and make it more general to deprecate
EUI-64.

What I can remember during and after IETF 87, there was also offlist discussion
about this and I said, since this part is in this draft and already explained, I
suggest to keep it as it is and nobody said otherwise. You were also includede
in that discussion.

So, when you planned to have that section out of this draft and make it more
general, at least you could mention it and discuss about this or refer to this
draft.

Hosnieh


------=_Part_202109_666086274.1383033220323
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>
 
 </head><body style="">
 
  <div>
   Fernando,
  </div> 
  <div>
   &#160;
  </div> 
  <div>
   &#160;
  </div> 
  <div>
   &#62; So I&#39;m rather curious about your suggestion of &#34;plagiarism&#34; on our side,
   <br/>&#62; I should say.
   <br/>&#62;
  </div> 
  <div>
   &#160;
  </div> 
  <div>
   That section of the draft in ra-privacy also says not to use EUI-64 as both temporary and public addresses. This section is not new and you can find it in early versions of ra-privacy as well because it was one of the problem of RFC 4941. Your draft expands this section and make it more general to deprecate EUI-64. 
  </div> 
  <div>
   &#160;
  </div> 
  <div>
   What I can remember during and after IETF 87, there was also offlist discussion about this and I said, since this part is in this draft and already explained, I suggest to keep it as it is and nobody said otherwise. You were also includede in that discussion. 
  </div> 
  <div>
   &#160;
  </div> 
  <div>
   So, when you planned to have that section out of this draft and make it more general, at least you could mention it and discuss about this or refer to this draft.
  </div> 
  <div>
   &#160;
  </div> 
  <div>
   Hosnieh
  </div> 
  <div>
   &#160;
  </div> 
  <div>
   &#160;
  </div>
 
</body></html>
------=_Part_202109_666086274.1383033220323--

From jeroen@massar.ch  Tue Oct 29 02:43:35 2013
Return-Path: <jeroen@massar.ch>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC52911E81BC for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 02:43:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[AWL=-0.700, BAYES_00=-2.599, J_CHICKENPOX_51=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m7ePDRAE3KYL for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 02:43:35 -0700 (PDT)
Received: from icaras.de.unfix.org (icaras.de.unfix.org [IPv6:2a01:4f8:130:74c1:5054:ff:fec4:f7d4]) by ietfa.amsl.com (Postfix) with ESMTP id 0FB8711E81F0 for <ipv6@ietf.org>; Tue, 29 Oct 2013 02:43:33 -0700 (PDT)
Received: from yomi.ch.unfix.org (84-73-144-213.dclient.hispeed.ch [84.73.144.213]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeroen) by icaras.de.unfix.org (Postfix) with ESMTPSA id 151E0801C2A2; Tue, 29 Oct 2013 10:43:24 +0100 (CET)
Message-ID: <526F831C.5080408@massar.ch>
Date: Tue, 29 Oct 2013 10:42:52 +0100
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar Networking
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Peter Dordal <pld@cs.luc.edu>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<526AC8AF.4060608@si6networks.com>	<8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com>	<CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com>	<526CDC59.4070204@massar.ch>	<CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com>	<CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com>	<CAKFn1SG1PC_kA-pO5Or8VyeaOzvLfpmQe0LiiYkXU_HzNqGzCQ@mail.gmail.com>	<526E250E.5050607@massar.ch>	<CAKD1Yr1evbMf1pD4yBrZyvF2XLXGOre3bHDB0gOZTLme7vnh2A@mail.gmail.com>	<526E267E.2070705@massar.ch>	<CAKD1Yr1K+4H+Gq9dWK-tVJu_3_pw+q7Q1owGz69eg6jy--XN5A@mail.gmail.com>	<526E2A56.7070503@massar.ch>	<CAKD1Yr3quaLS8zmDuf301MHL_y+uLQg0UfAEU+Kk-hwfv0oqtw@mail.gmail.com> <526E2E0C.904@massar.ch> <526E9B7F.3020004@cs.luc.e du>
In-Reply-To: <526E9B7F.3020004@cs.luc.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 29 Oct 2013 09:43:36 -0000

On 2013-10-28 18:14 , Peter Dordal wrote:
> On 10/28/2013 04:27 AM, Jeroen Massar wrote:
>> See my other messages: IPv6 Privacy addresses are a myth, they do not
>> work. You can track people even when you just see IP addresses and
>> ignore the upper layers. The upper layers just make it easier.
>>
>> Greets,
>>   Jeroen
>>
>>
> In what sense exactly is this claim meant?I agree that "privacy"
> addresses are in many scenarios not all that private,
> but I am not sure that makes them useless.
> 
> 1. Suppose I connect both at work and home; each site has
> a different /64 prefix. I do not want anyone to correlate my work
> and home traffic.

For different sites, not using the MAC-derived EUI-64 is indeed a great
thing. But you could just as well use DHCPv6 or just pick random number
like ::5 and use that insted.

The actual IPv6 Privacy address, including the randomization and
expiration does not add much there in avoiding tracking.

Note that a lot of folks have IM clients (using specific jabber
servicers), mail clients (using specific smtp/imap/pop3 servers)
configured. Thus if there are only a few users on the destination
server, it is easy enough to designate all that randomly picked source
still as the same person based on that.

(If you want to hide on the IP level, use mixnet...)

> Assume I am either not using http, or I erase
> cookies frequently; higher layers are not exposing me in any
> "obvious" way.

Actually, erasing your cookies makes you obvious as there are very few
people who do not have cookies as you get them all the time.

Hence why some people where 'exchanging' cookies at one point (can't
seem to quickly find the site that had the plugins etc to do so).

But seems Christian wrote a article about that earlier this year:

http://huitema.wordpress.com/2013/03/17/lets-build-a-cookie-exchange/

> If I use SLAAC at both sites, using the same EUI-64 identifier
> as my low-order bits, then this gives me away.

Definitely. And that can be considered a good thing (logging, ACLs) and
a bad thing: makes tracking really easy.

> How else can I avoid this besides using privacy addresses?

As above, configure something like ::2 or use other such numbers.

> 2. Suppose I connect to two different remote sites, A and B,
> while at work. I don't want someone reviewing the logs at A and B
> to know the same host made both these connections.
> 
> There are thousands of others at my same workplace using the
> same /64 prefix; an outside observer will not be able to infer
> that the same person connected to A and B from the prefix alone.

But they can make a pretty good guess. There will be a lot of meta data
in those connections, much of it that will make you unique.

Try this for the fun of it:
 - keep your cookies that you have
 - google for something common "how do you..."
   and see how autocomplete answers (that is, if you still have that
enabled). or if you do not (smart! but also makes you unique again)
   just hit the search button and see which answers you get

now clear those cookies and change that IPv6 address of yours to
something else random and try again. Gee, you say, same results!?

Now ask a colleague to repeat the same thing on a different host and
he/she will be getting different results. Gee, why? There is more meta
information than that...

And HTTP is not the only way to detect things, every protocol has meta
data. It just depends on how much the adversary wants to know who you
are and how much they can collect.

> I want to choose different IPv6 addresses at my end
> for each of these connections, differing of course only in the
> low-order bits. Again I use SLAAC. How do I create
> the second IPv6 address except by using privacy addresses?

The privacy extensions are not per-application and neither
per-connection. They are time-based instead and thus if you make
connections during a certain bucket of time they all are coming at the
same time.

They would be much better already if they did do per-app, per-connect.

But still you would just be thrown into a bit-bucket of 'that /64
contains users X Y Z" and thus based on other properties than IP you
would still be seen as identity X.

Greets,
 Jeroen


From alexandru.petrescu@gmail.com  Tue Oct 29 03:06:48 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7806421E8109 for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 03:06:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.284
X-Spam-Level: 
X-Spam-Status: No, score=-10.284 tagged_above=-999 required=5 tests=[AWL=-0.035, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d24QuPNRLGp9 for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 03:06:41 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) by ietfa.amsl.com (Postfix) with ESMTP id BF66A11E8209 for <ipv6@ietf.org>; Tue, 29 Oct 2013 03:06:21 -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 r9TA6CPX008468 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 29 Oct 2013 11:06:13 +0100
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r9TA6CbI016332; Tue, 29 Oct 2013 11:06:12 +0100 (envelope-from alexandru.petrescu@gmail.com)
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 r9TA667l009362; Tue, 29 Oct 2013 11:06:12 +0100
Message-ID: <526F888E.20609@gmail.com>
Date: Tue, 29 Oct 2013 11:06:06 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Octavio Alvarez <alvarezp@alvarezp.ods.org>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com>	<526AACA5.7090604@si6networks.com>	<E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<526AC8AF.4060608@si6networks.com>	<8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org> <526E43E8.3080601@gmail.com> <526E91A3.8000807@alvarezp.ods.org>
In-Reply-To: <526E91A3.8000807@alvarezp.ods.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>, Tim Chown <tjc@ecs.soton.ac.uk>, "Fred Baker \(fred\)" <fred@cisco.com>, Fernando Gont <fgont@si6networks.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 29 Oct 2013 10:06:48 -0000

Le 28/10/2013 17:32, Octavio Alvarez a écrit :
> On 10/28/2013 04:00 AM, Alexandru Petrescu wrote:
>> Le 27/10/2013 16:53, Octavio Alvarez a écrit :
>>> On 10/27/2013 02:26 AM, Jeroen Massar wrote:
>>>>> allows privacy,
>>>>
>>>> IMHO big nonsense. The company (amongst many others!) you work
>>>> for uses amongst others cookies to track their people, and if
>>>> they really bother could even use natural language structure,
>>>> search query types, and other behavior for breaking this
>>>> 'privacy'. Also note that even if the last 64bits are random,
>>>> your company should be more than able to say "oh, there are
>>>> typically X users in there, it likely is Y"...
>>>
>>> Then why deprecate EUI-64?
>>
>> I think there is a problem in naming that draft.
>
> I meant "why deprecate EUI-64 as device-ID in IPv6 addresses".

Ok, but even then there might be an issue.

It is a 'Modified EUI-64', not an 'EUI-64'.

It is an Interface ID, not a device-id.

But I can understand you correctly ok, no problem :-)

This leads to me thinking that what they'd like to deprecate is this
phrase from RFC2464:
> The Interface Identifier [AARCH] for an Ethernet interface is based
> on the EUI-64 identifier [EUI64] derived from the interface's built-
> in 48-bit IEEE 802 address.  The EUI-64 is formed as follows.
> (Canonical bit order is assumed throughout.)

And I still have a problem with it, because it is not IETF who requires
the EUI-64 to be formed from the hardware address, but it is IEEE who
requires that.  IETF only requires the 'Modified EUI-64' to modify the
EUI-64 e.g. by inverting the u/g bits.

What IETF could deprecate is this other phrase from RFC2464:
> The Interface Identifier is then formed from the EUI-64 by
> complementing the "Universal/Local" (U/L) bit, which is the next-to-
> lowest order bit of the first octet of the EUI-64.

It should say this:
> The Interface Identifier MAY be formed from the EUI-64; if so, then
> it MAY be complementing the "Universal/Local" (U/L) bit, which is the
> next-to- lowest order bit of the first octet of the EUI-64.

Moreover, RFC4291 says this:
> For all unicast addresses, except those that start with the binary
> value 000, Interface IDs are required to be 64 bits long and to be
> constructed in Modified EUI-64 format.

This gives an opportunity to people to form IPv6 address starting with
000 and without necessarily using Modified EUI-64, thus not necessarily
using EUI-64, and thus not necessarily using hardware addresses, and
thus not necessarily using 64-bit Interface Identifiers, and hence maybe
longer than 64 prefix lengths.

Otherwise, the RFC4291 spec _could_ say this:
> For all unicast addresses, except those that start with the binary
> value 000, Interface IDs are required to be 64 bits long and MAY be
> constructed in Modified EUI-64 format.

or it could say this:
> For all unicast addresses, except those that start with the binary
> value 000, Interface IDs MAY be formed using the 'Modified EUI-64'
> format, in which case their length is 64 bits.

Alex




From alexandru.petrescu@gmail.com  Tue Oct 29 03:20:06 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E72B321E8107 for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 03:20:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.283
X-Spam-Level: 
X-Spam-Status: No, score=-10.283 tagged_above=-999 required=5 tests=[AWL=-0.034, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5oK8r4EnMIJx for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 03:20:01 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) by ietfa.amsl.com (Postfix) with ESMTP id A081D21E8105 for <ipv6@ietf.org>; Tue, 29 Oct 2013 03:20:00 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r9TAJmL5031316 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 29 Oct 2013 11:19:48 +0100
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r9TAJmWB022830; Tue, 29 Oct 2013 11:19:48 +0100 (envelope-from alexandru.petrescu@gmail.com)
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 r9TAJiEm018866; Tue, 29 Oct 2013 11:19:47 +0100
Message-ID: <526F8BC0.505@gmail.com>
Date: Tue, 29 Oct 2013 11:19:44 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>, "sthaug@nethelp.no" <sthaug@nethelp.no>, "alvarezp@alvarezp.ods.org" <alvarezp@alvarezp.ods.org>
Subject: Re: Why /64
References: <526CF079.7030804@globis.net> <526E41BC.3080303@gmail.com>	<526E9735.8080708@alvarezp.ods.org> <20131028.184553.78794962.sthaug@nethelp.no> <1382988218.92574.YahooMailNeo@web142504.mail.bf1.yahoo.com>
In-Reply-To: <1382988218.92574.YahooMailNeo@web142504.mail.bf1.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "v6ops@globis.net" <v6ops@globis.net>, "tjc@ecs.soton.ac.uk" <tjc@ecs.soton.ac.uk>, "ipv6@ietf.org" <ipv6@ietf.org>, "fred@cisco.com" <fred@cisco.com>, "fgont@si6networks.com" <fgont@si6networks.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 29 Oct 2013 10:20:07 -0000

Le 28/10/2013 20:23, Mark ZZZ Smith a écrit :
>
>
>
>
> ----- Original Message -----
>> From: "sthaug@nethelp.no" <sthaug@nethelp.no> To:
>> alvarezp@alvarezp.ods.org Cc: alexandru.petrescu@gmail.com;
>> ipv6@ietf.org; v6ops@globis.net; tjc@ecs.soton.ac.uk;
>> fred@cisco.com; fgont@si6networks.com Sent: Tuesday, 29 October
>> 2013 4:45 AM Subject: Re: Why /64
>>
>>>> The IPv4's CIDR concept (route based on bitwise borders,
>>>> instead
>> of
>>>> 8byte) seems to me a good clue for the discussion about the fix
>>>> 64bit limit in IPv6.
>>>
>>> CIDR is already being used. /80s, /96s and other arbitrary
>>> netmasks can be set on some devices and should work. Some of them
>>> may misbehave, though.
>>
>> "Some devices"? They work on all devices I've tried. And I
>> certainly *expect* normal longest prefix match based forwarding to
>> work, with no arbitrary /64 limitation.
>>
>
> I'd expect it to work too.

Yes, I expect routing to work on larger-than-64 and bitwise boundaries.

But is also a matter of the subnet mask of the smallest possible subnet. 
  Can one have an IPv6 subnet comprising only 4 entities, on 
Ethernet-compatible, and using Stateless Address Auto-Configuration?

> I think the difference between IPv6 and other protocols in this area
> is that while it has a longest match rule across the whole address,
> there are "soft" rather than hard field boundaries in a portion of
> the address space because they're much easier to deal with
> operationally, and easier to develop systems to deal with. The
> longest match rule is there to ensure that if the soft field
> boundaries end up being incorrect, different soft boundaries can be
> defined in a different portion of the address space, it won't require
> router upgrades to fix as the move from Classful IPv4 to CIDR did.
>
> People like flexibility, but don't seem to think much about the costs
> it may incur. Flexibility and options creates opportunity for error.
> It's hard to get prefix length wrong when all subnets are /64s and
> when all of your customers have /48s. If your customers have a mix of
> /56s and /48s, you now have to manage your space more carefully,
> costing you time and effort, and over time a few customers may get
> given the wrong prefix size for their needs, with the costs of
> dealing with those error may exceed any savings there were in trying
> to "right size" allocations. Simplicity is usually cheaper and more
> robust.

Yes and no.

YEs in that flexibility with fixed borders is indeed easier to grasp 
conceptually and easier to write configuration files for them, 
especially when addresses are a huge 128bit long.  A few rules of thumb 
and checking the validity can be done visually, no need of complex 
formal checkers.

No, in that we can still have flexibility, just that it is finer grain.

RFC1878 "Variable Length Subnet Table For IPv4" adviced for this by 
detailing tables of subnet masks, their effective subnets and effective 
number of Hosts.  At a time when the typical edge network subnet length 
was 8bit (today's typical 64bit Interface ID) this was a step forward 
for better detailing and subnetting space.

And yes, it may be that today 64bit is large enough and we dont have 
that IPv4 subnetting problem.

Alex

>
>> The only limitations I've seen are IPv6 ACLs on some Cisco
>> switches, where the 144 bit wide CAM cannot accomodate a 128 bit
>> IPv6 address *and* 2 x 16 bit port numbers.
>>
>> Steinar Haug, AS 2116
>>
>> --------------------------------------------------------------------
>>
>>
IETF IPv6 working group mailing list
>> ipv6@ietf.org Administrative Requests:
>> https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
>
>>
>



From benamar73@gmail.com  Tue Oct 29 03:22:04 2013
Return-Path: <benamar73@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B3B621E8119 for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 03:22:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, GB_I_INVITATION=-2, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pw8VPd9Tv3X6 for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 03:22:03 -0700 (PDT)
Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 772B521E8108 for <ipv6@ietf.org>; Tue, 29 Oct 2013 03:22:03 -0700 (PDT)
Received: by mail-ob0-f176.google.com with SMTP id uy5so4896508obc.7 for <ipv6@ietf.org>; Tue, 29 Oct 2013 03:22:02 -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 :cc:content-type; bh=OkkfKxxCJeRUQtN2jbmpmoxHNsQwZO+WLBjOJWKKwCI=; b=TrK5XxKNA8N795DdR/bDzliGMZKdL/uzD7g5GIdQLNyAMubnUQlHsUMBLGKrwtiufP KzUQH3InC7m+S3OoYQJrmen08Nup3GEc7efvaBHf85627v1Xyy1/8Q9EhEosiokMhiz5 QU8AawMKJcyvC/Ksjo/Eb2Y5OKDtW1GHv/sV/IR1+a7AlF0fIs/oKJVvsQ1xNxcQxyHM 4LVAwavtpLXRxVZKiP1kQV1q2PSZv+/iE3ws3/vqLkwwqNuRMML4GeLGZ3ocpPQpDBuo laMnxSElspovSVPrMBL6F9GiaRcYSo+KUA6F1MqMNFYJ3UWGHSzIUip/SKvfHrUVGZT0 4YwA==
MIME-Version: 1.0
X-Received: by 10.182.233.228 with SMTP id tz4mr5500544obc.56.1383042122639; Tue, 29 Oct 2013 03:22:02 -0700 (PDT)
Received: by 10.76.173.138 with HTTP; Tue, 29 Oct 2013 03:22:02 -0700 (PDT)
In-Reply-To: <526E3D7B.9030801@gmail.com>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <526E3D7B.9030801@gmail.com>
Date: Tue, 29 Oct 2013 10:22:02 +0000
Message-ID: <CAMugd_Wz-RH_GMzqe-AS5XffEj-dT+jG6GjWjHMpVVcSWkoiHg@mail.gmail.com>
Subject: Re: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification for draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
From: Nabil Benamar <benamar73@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c306006defea04e9de9683
Cc: Fernando Gont <fgont@si6networks.com>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 29 Oct 2013 10:22:04 -0000

--001a11c306006defea04e9de9683
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I agree with Alex!
Why not a new draft as a problem statement to explore and sum up all
relevant issues  ?

*Best wishes*
*nabilbenamar.com*

*
---------------------------------------------------------------------------=
-----
*


On Mon, Oct 28, 2013 at 10:33 AM, Alexandru Petrescu <
alexandru.petrescu@gmail.com> wrote:

> Le 25/10/2013 19:38, Fernando Gont a =E9crit :
>
>  On 10/25/2013 01:54 PM, Alexandru Petrescu wrote:
>>
>>> If we're again at deprecating things one aspect that I'd really like
>>> removed is this 64bit border for SLAAC over Ethernet.
>>>
>>> One should be able to do SLAAC over Ethernet (and all its backward
>>> compatible IEEE links) with Interface Identifiers optionally  shorter
>>> than 64bit.
>>>
>>
>> If there's something else that needs to be fixed, then please:
>>
>> 1) Write an I-D that analyzes the problem, and proposes a workaround, an=
d,
>>
>
> Thanks for the invitation.  Sounds like a good idea to write a problem
> statement about it.  I wouldn't put solutions in the same draft though.
>
> Alex
>
>
>
>
>> 2) start a new thread. :-)
>>
>> Let's keep this thread on-topic. ;-)
>>
>> Cheers,
>>
>>
>
> ------------------------------**------------------------------**--------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/**listinfo/ipv6<htt=
ps://www.ietf.org/mailman/listinfo/ipv6>
> ------------------------------**------------------------------**--------
>

--001a11c306006defea04e9de9683
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:verdana,=
sans-serif;font-size:large;color:#3d85c6">I agree with Alex!</div><div clas=
s=3D"gmail_default" style=3D"font-family:verdana,sans-serif;font-size:large=
;color:#3d85c6">
Why not a new draft as a problem statement to explore and sum up all releva=
nt issues =A0?</div></div><div class=3D"gmail_extra"><br clear=3D"all"><div=
><div dir=3D"ltr"><div><div><font face=3D"sans-serif" color=3D"#1F497D"><sp=
an style=3D"font-size:15px"><b>Best wishes</b></span></font></div>
<div></div><div style=3D"font-family:&#39;Times New Roman&#39;;font-size:me=
dium"><b><a href=3D"http://nabilbenamar.com" target=3D"_blank">nabilbenamar=
.com</a></b></div></div><div style=3D"font-family:&#39;Times New Roman&#39;=
;font-size:medium">
<span></span><span></span><br></div><div style=3D"font-family:&#39;Times Ne=
w Roman&#39;;font-size:medium"><div><b><span style=3D"font-weight:normal;fo=
nt-size:16px"><b><span style=3D"font-size:11pt;font-family:sans-serif;color=
:rgb(31,73,125)">----------------------------------------------------------=
----------------------</span></b></span></b></div>
</div></div></div>
<br><br><div class=3D"gmail_quote">On Mon, Oct 28, 2013 at 10:33 AM, Alexan=
dru Petrescu <span dir=3D"ltr">&lt;<a href=3D"mailto:alexandru.petrescu@gma=
il.com" target=3D"_blank">alexandru.petrescu@gmail.com</a>&gt;</span> wrote=
:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Le 25/10/2013 19:38, Fernando Gont a =E9crit=
 :<div class=3D"im"><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On 10/25/2013 01:54 PM, Alexandru Petrescu wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
If we&#39;re again at deprecating things one aspect that I&#39;d really lik=
e<br>
removed is this 64bit border for SLAAC over Ethernet.<br>
<br>
One should be able to do SLAAC over Ethernet (and all its backward<br>
compatible IEEE links) with Interface Identifiers optionally =A0shorter<br>
than 64bit.<br>
</blockquote>
<br>
If there&#39;s something else that needs to be fixed, then please:<br>
<br>
1) Write an I-D that analyzes the problem, and proposes a workaround, and,<=
br>
</blockquote>
<br></div>
Thanks for the invitation. =A0Sounds like a good idea to write a problem st=
atement about it. =A0I wouldn&#39;t put solutions in the same draft though.=
<br>
<br>
Alex<div class=3D"im HOEnZb"><br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
2) start a new thread. :-)<br>
<br>
Let&#39;s keep this thread on-topic. ;-)<br>
<br>
Cheers,<br>
<br>
</blockquote>
<br>
<br></div><div class=3D"HOEnZb"><div class=3D"h5">
------------------------------<u></u>------------------------------<u></u>-=
-------<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/<u></u>listinfo/ipv6</a=
><br>
------------------------------<u></u>------------------------------<u></u>-=
-------<br>
</div></div></blockquote></div><br></div>

--001a11c306006defea04e9de9683--

From pld@cs.luc.edu  Mon Oct 28 10:14:54 2013
Return-Path: <pld@cs.luc.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 356F711E8292 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 10:14:54 -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=-2.599, J_CHICKENPOX_51=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3a3tDN3AJZGo for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 10:14:47 -0700 (PDT)
Received: from lukasiewicz.cs.luc.edu (lukasiewicz.cs.luc.edu [147.126.65.57]) by ietfa.amsl.com (Postfix) with ESMTP id 48A0311E8282 for <ipv6@ietf.org>; Mon, 28 Oct 2013 10:14:41 -0700 (PDT)
Received: from [10.0.0.5] (ulam2 [147.126.65.47]) by lukasiewicz.cs.luc.edu (Postfix) with ESMTPA id EDF956A237; Mon, 28 Oct 2013 12:14:39 -0500 (CDT)
Message-ID: <526E9B7F.3020004@cs.luc.edu>
Date: Mon, 28 Oct 2013 12:14:39 -0500
From: Peter Dordal <pld@cs.luc.edu>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Jeroen Massar <jeroen@massar.ch>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<526AC8AF.4060608@si6networks.com>	<8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com>	<CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com>	<526CDC59.4070204@massar.ch>	<CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com>	<CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com>	<CAKFn1SG1PC_kA-pO5Or8VyeaOzvLfpmQe0LiiYkXU_HzNqGzCQ@mail.gmail.com>	<526E250E.5050607@massar.ch>	<CAKD1Yr1evbMf1pD4yBrZyvF2XLXGOre3bHDB0gOZTLme7vnh2A@mail.gmail.com>	<526E267E.2070705@massar.ch>	<CAKD1Yr1K+4H+Gq9dWK-tVJu_3_pw+q7Q1owGz69eg6jy--XN5A@mail.gmail.com>	<526E2A56.7070503@massar.ch>	<CAKD1Yr3quaLS8zmDuf301MHL_y+uLQg0UfAEU+Kk-hwfv0oqtw@mail.gmail.com> <526E2E0C.904@massar.ch>
In-Reply-To: <526E2E0C.904@massar.ch>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 29 Oct 2013 04:09:38 -0700
Cc: Peter Dordal <pld@cs.luc.edu>, "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Oct 2013 17:33:07 -0000

On 10/28/2013 04:27 AM, Jeroen Massar wrote:
> See my other messages: IPv6 Privacy addresses are a myth, they do not
> work. You can track people even when you just see IP addresses and
> ignore the upper layers. The upper layers just make it easier.
>
> Greets,
>   Jeroen
>
>
In what sense exactly is this claim meant?I agree that "privacy"
addresses are in many scenarios not all that private,
but I am not sure that makes them useless.

1. Suppose I connect both at work and home; each site has
a different /64 prefix. I do not want anyone to correlate my work
and home traffic. Assume I am either not using http, or I erase
cookies frequently; higher layers are not exposing me in any
"obvious" way.

If I use SLAAC at both sites, using the same EUI-64 identifier
as my low-order bits, then this gives me away.

How else can I avoid this besides using privacy addresses?

2. Suppose I connect to two different remote sites, A and B,
while at work. I don't want someone reviewing the logs at A and B
to know the same host made both these connections.

There are thousands of others at my same workplace using the
same /64 prefix; an outside observer will not be able to infer
that the same person connected to A and B from the prefix alone.

I want to choose different IPv6 addresses at my end
for each of these connections, differing of course only in the
low-order bits. Again I use SLAAC. How do I create
the second IPv6 address except by using privacy addresses?



Peter Dordal
Loyola University Chicago

From brian@innovationslab.net  Tue Oct 29 08:43:09 2013
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24A8111E8131 for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 08:43:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.567
X-Spam-Level: 
X-Spam-Status: No, score=-102.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3+m0DEsNyjU4 for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 08:43:02 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id C246611E817F for <ipv6@ietf.org>; Tue, 29 Oct 2013 08:42:47 -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 AB53C8809F; Tue, 29 Oct 2013 08:42:44 -0700 (PDT)
Received: from 102527254.rudm1.ra.johnshopkins.edu (addr16212925014.ippl.jhmi.edu [162.129.250.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 2B429130003; Tue, 29 Oct 2013 08:42:44 -0700 (PDT)
Message-ID: <526FD768.3070703@innovationslab.net>
Date: Tue, 29 Oct 2013 11:42:32 -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.0.1
MIME-Version: 1.0
To: draft-ietf-6man-stable-privacy-addresses@tools.ietf.org,  6man Chairs <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>
Subject: AD Evaluation: draft-ietf-6man-stable-privacy-addresses
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="IGOuA2QAQRLO3cgXKRbF1KJfpmED8bkw9"
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 29 Oct 2013 15:43:09 -0000

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

All,
     I have completed my AD evaluation for
draft-ietf-6man-stable-privacy-addresses and only have a few
comments/questions that I would like to get some feedback on...

1. It would be useful to include an *informative* reference or two for
candidate PRFs.

2. Given the opaque bits discussion in section 5, I think it would be
good to include a reference to the 6man-ug draft to provide the
justification.

3. Section 6 discusses the benefits of using the DAD_Counter in the PRF
call, but I think the draft should also mention the downsides to not
maintaining that variable in non-volatile memory over reboots.
Specifically, the scenario where a node used IDGEN_RETRIES attempts on
the previous boot to get a valid address and during the current boot
will fail if it needs IDGEN_RETRIES+1 tries and DAD_Counter info is not
stored.

4. I am agnostic on this one, but want some feedback.  Should the
reference to the address-generation-privacy draft be normative given
that it contains the necessary background info supporting this approach?


Once we agree on these points, we can move the draft along in the
publication process.

Regards,
Brian


--IGOuA2QAQRLO3cgXKRbF1KJfpmED8bkw9
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

iQEcBAEBCgAGBQJSb9dtAAoJEBOZRqCi7goqbT8H/0gAdzcRKix8zJVGDnWPYanx
RdeKg2lCReX4oOhJuEic3DZnlubfXJlw4dbzuc1FSzvhoXOcqvYZrdr1FJGO6Zt6
cSJr3AH9cVLM8vwOo/tN07TMEn80EPwka2ZX/6KmayV0XLN6xlQB4jc0Ga4P9cLI
sjecSLI7aqgehUaLKpPRjdB3UEZLAChFypMkmI+ir+qdWApkvwrDExXcEx2Voy95
1vpStUsdeixfQDV2l52CGC7eqkpIhpswGV3cc+TgG28oxWQCUQyHNKoiMsrkFBJ3
qeJyBcpUO0olivBxYMntI0uqnNApIn69nK4SOJHaYTfPfin8yeB0GE7cqnOJAeY=
=Af/Y
-----END PGP SIGNATURE-----

--IGOuA2QAQRLO3cgXKRbF1KJfpmED8bkw9--

From ietf-secretariat-reply@ietf.org  Tue Oct 29 08:43:47 2013
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8B1411E819D for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 08:43:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.381
X-Spam-Level: 
X-Spam-Status: No, score=-101.381 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, NO_RELAYS=-0.001, TVD_SPACE_RATIO=2.219, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DmpzjZnHpJUG; Tue, 29 Oct 2013 08:43:47 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F3B221E8154; Tue, 29 Oct 2013 08:43:46 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
To: 6man-chairs@tools.ietf.org, draft-ietf-6man-stable-privacy-addresses@tools.ietf.org, ipv6@ietf.org
Subject: ID Tracker State Update Notice: <draft-ietf-6man-stable-privacy-addresses-14.txt>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.81
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131029154346.8829.60774.idtracker@ietfa.amsl.com>
Date: Tue, 29 Oct 2013 08:43:46 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 29 Oct 2013 15:43:48 -0000

State changed to AD Evaluation::External Party from AD Evaluation
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-6man-stable-priv=
acy-addresses/


From fernando@gont.com.ar  Tue Oct 29 09:28:48 2013
Return-Path: <fernando@gont.com.ar>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C454111E8228 for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 09:28:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, GB_ABOUTYOU=0.5]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1MLGkhsgTLqD for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 09:28:44 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id BE0A411E8131 for <ipv6@ietf.org>; Tue, 29 Oct 2013 09:28:40 -0700 (PDT)
Received: from [190.112.245.66] (helo=[172.17.150.9]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fernando@gont.com.ar>) id 1VbC9f-00022w-L1; Tue, 29 Oct 2013 17:28:31 +0100
Message-ID: <526FE22C.6090502@gont.com.ar>
Date: Tue, 29 Oct 2013 12:28:28 -0400
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Hosnieh <ietf@rozanak.com>, Alissa Cooper <acooper@cdt.org>
Subject: Re: Deprecating EUI-64 Based IPv6 Addresses (Fwd: New Version Notification for draft-gont-6man-deprecate-eui64-based-addresses-00.txt)
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar> <001101ced0e5$fc380120$f4a80360$@rozanak.com> <526EEC30.6010709@gont.com.ar> <373361003.202110.1383033220363.open-xchange@email.1and1.com>
In-Reply-To: <373361003.202110.1383033220363.open-xchange@email.1and1.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 29 Oct 2013 16:28:48 -0000

On 10/29/2013 03:53 AM, Hosnieh wrote:
>  
>> So I'm rather curious about your suggestion of "plagiarism" on our side,
>> I should say.
>  
> That section of the draft in ra-privacy also says not to use EUI-64 as
> both temporary and public addresses. This section is not new and you can
> find it in early versions of ra-privacy as well because it was one of
> the problem of RFC 4941. 

Please re-read my earlier response: I authored an I-D that said that in
December 2011.



> Your draft expands this section and make it
> more general to deprecate EUI-64.

It's not "more general". There's a difference between a proposal that
provides an option, and a document that is meant to replace one thing
with another.

draft-ietf-6man-stable-privacy-addresses was originally meant to replace
Modified EUI-64. Then that document was change such that the mechanism
was specified as an option, without replacing the existing algorithms.

Your I-D ra-privacy means to do something similar to what stable-privacy
is doing: provide an alternative algorithm for generating IIDs.

draft-gont-6man-deprecate-eui64-based-addresses-00 does a different
thing: it recommends to replace the existing recommended algorithm
(Modifed EUI-64) with another (stable-privacy).


Suggesting that your document was plagiarized is, at best, inappropriate.



> What I can remember during and after IETF 87, there was also offlist
> discussion about this and I said, since this part is in this draft and
> already explained, I suggest to keep it as it is and nobody said
> otherwise. You were also includede in that discussion.

1) What your document says is different from what our says (please see
my explanation above)

2) Your document is, IMO, mixing different and unrelated issues -- I
don't think it could be progressed as such.

3) I don't understand how being listed in a recipient's list represents
some sort of agrement -- but this is a side comment. And while digging
into mail achives, it seems that your description of such mail exchange
is misleading.



> So, when you planned to have that section out of this draft and make it
> more general, at least you could mention it and discuss about this or
> refer to this draft.

Once again: please see my explanation above. Namely:

1) Your document provides an optional way to represent IIDs (in this
respect, stable-privacy has been doing this way before.. but the same
applies to CGAs and others)

2) draft-ietf-6man-stable-privacy-addresses did both options (firstly
trying to replace Modified EUI-64, and later (as does the current
version) simply providing an alternative algorithm to do so).
draft-ietf-6man-stable-privacy-addresses predates was published way
before your I-D.

P.S.: I would have preferred to explain this off-list. But since your
post was on-list, and I was asked to clarify this issue, that's why
ended up posting this an my previous note on-list.

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 alvarezp@alvarezp.ods.org  Tue Oct 29 10:34:25 2013
Return-Path: <alvarezp@alvarezp.ods.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D09D21F9D8D for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 10:34:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id laBrn2ZgHmm6 for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 10:34:10 -0700 (PDT)
Received: from sobre.alvarezp.com (sobre.alvarezp.com [IPv6:2600:3c01::f03c:91ff:fe96:8fec]) by ietfa.amsl.com (Postfix) with ESMTP id 49E0221F9BD5 for <ipv6@ietf.org>; Tue, 29 Oct 2013 10:32:17 -0700 (PDT)
Received: from [192.168.2.251] (189.220.45.207.cable.dyn.cableonline.com.mx [189.220.45.207]) by sobre.alvarezp.com (Postfix) with ESMTPSA id EB133613D; Tue, 29 Oct 2013 13:32:02 -0400 (EDT)
Message-ID: <526FF124.2030809@alvarezp.ods.org>
Date: Tue, 29 Oct 2013 10:32:20 -0700
From: Octavio Alvarez <alvarezp@alvarezp.ods.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130821 Icedove/17.0.8
MIME-Version: 1.0
To: Jeroen Massar <jeroen@massar.ch>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<526AC8AF.4060608@si6networks.com>	<8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com>	<CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com>	<526CDC59.4070204@massar.ch>	<CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com>	<CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com>	<CAKFn1SG1PC_kA-pO5Or8VyeaOzvLfpmQe0LiiYkXU_HzNqGzCQ@mail.gmail.com>	<526E250E.5050607@massar.ch>	<CAKD1Yr1evbMf1pD4yBrZyvF2XLXGOre3bHDB0gOZTLme7vnh2A@mail.gmail.com>	<526E267E.2070705@massar.ch>	<CAKD1Yr1K+4H+Gq9dWK-tVJu_3_pw+q7Q1owGz69eg6jy--XN5A@mail.gmail.com>	<526E2A56.7070503@massar.ch>	<CAKD1Yr3quaLS8zmDuf301MHL_y+uLQg0UfAEU+Kk-hwfv0oqtw@mail.gmail.com> <526E2E0C.904@massar.ch> <526E9B7F.3020004@cs.luc.e du> <526F831C.5080408@massar.ch>
In-Reply-To: <526F831C.5080408@massar.ch>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Peter Dordal <pld@cs.luc.edu>, "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 29 Oct 2013 17:34:25 -0000

On 10/29/2013 02:42 AM, Jeroen Massar wrote:
> Try this for the fun of it:
>  - keep your cookies that you have
>  - google for something common "how do you..."
>    and see how autocomplete answers (that is, if you still have that
> enabled). or if you do not (smart! but also makes you unique again)
>    just hit the search button and see which answers you get
> 
> now clear those cookies and change that IPv6 address of yours to
> something else random and try again. Gee, you say, same results!?

That has nothing to do with the issue at hand.

Whatever changes are done in IPv6 can not protect a user if the user
likes using an application designed to track him. The "problem" may not
lie on the application itself, but it certainly doesn't lie on IPv6
either (read: HTTP cokies...)

Writing a higher-layer protocol or application that tracks you is not
the fault of IPv6. It's like blaming Ethernet for allowing a site in
Australia to reach Europe given Ethernet was only designed for local
area networks.

The issue at hand is: what does IPv6 directly does to leak information
about the local machine? Is this a problem? If it is (at all) is it
possible to fix and how?




From scott.brim@gmail.com  Tue Oct 29 10:39:03 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97B9921F89A5 for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 10:39:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.592
X-Spam-Level: 
X-Spam-Status: No, score=-102.592 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qmJ-sCFwbIDN for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 10:39:01 -0700 (PDT)
Received: from mail-oa0-x230.google.com (mail-oa0-x230.google.com [IPv6:2607:f8b0:4003:c02::230]) by ietfa.amsl.com (Postfix) with ESMTP id 0521411E8137 for <ipv6@ietf.org>; Tue, 29 Oct 2013 10:38:56 -0700 (PDT)
Received: by mail-oa0-f48.google.com with SMTP id m17so220177oag.35 for <ipv6@ietf.org>; Tue, 29 Oct 2013 10:38:56 -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=JwE9JoG+WKT2ccafCIoF710vMOsVn6AXHN9BewX/kXg=; b=ZiXVEE4+t1s2FDnwFtg7rtlG1xPPYTVrFRZr62+Wg8xx17oztV8J4HbZWL1TBzAAfz aA+6MylyZmif5FbrH5gWQJYT8byzRxQIp9uj5tS/bJqf9q21pIE15T3oH4gGHPvF1icZ d6smPD79Kzl9F7uYgoEwfk2d8dmJr6m8+6qFGuWafS5QYPwW3hYb1T6azHdUeG41d0ax zrscfkzZX66WcWHpII/6eleOMWmEvQHv+qvN1O5EV8E+iKwq7pAom8Z7pPNhbQ/gDf41 tRIICFXDwcj/bBmvFDEO3Xi4KvXR+/old0VUv6k3LX+Flg4v3jlkBCpcpgKXRjvw2z6Q ix3A==
X-Received: by 10.60.103.106 with SMTP id fv10mr575702oeb.44.1383068336436; Tue, 29 Oct 2013 10:38:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.2.134 with HTTP; Tue, 29 Oct 2013 10:38:36 -0700 (PDT)
In-Reply-To: <526FF124.2030809@alvarezp.ods.org>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com> <CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com> <CAKFn1SG1PC_kA-pO5Or8VyeaOzvLfpmQe0LiiYkXU_HzNqGzCQ@mail.gmail.com> <526E250E.5050607@massar.ch> <CAKD1Yr1evbMf1pD4yBrZyvF2XLXGOre3bHDB0gOZTLme7vnh2A@mail.gmail.com> <526E267E.2070705@massar.ch> <CAKD1Yr1K+4H+Gq9dWK-tVJu_3_pw+q7Q1owGz69eg6jy--XN5A@mail.gmail.com> <526E2A56.7070503@massar.ch> <CAKD1Yr3quaLS8zmDuf301MHL_y+uLQg0UfAEU+Kk-hwfv0oqtw@mail.gmail.com> <526E2E0C.904@massar.ch> <526F831C.5080408@massar.ch> <526FF124.2030809@alvarezp.ods.org>
From: Scott Brim <scott.brim@gmail.com>
Date: Tue, 29 Oct 2013 13:38:36 -0400
Message-ID: <CAPv4CP9bUqWwJhe7orp0-uZMKLpt2uPLJg_omqgOaByvxvy=fg@mail.gmail.com>
Subject: Re: Why /64
To: Octavio Alvarez <alvarezp@alvarezp.ods.org>
Content-Type: multipart/alternative; boundary=089e012277b4e4bbc504e9e4b0f0
Cc: Peter Dordal <pld@cs.luc.edu>, "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 29 Oct 2013 17:39:03 -0000

--089e012277b4e4bbc504e9e4b0f0
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Oct 29, 2013 at 1:32 PM, Octavio Alvarez
<alvarezp@alvarezp.ods.org>wrote:

> Writing a higher-layer protocol or application that tracks you is not
> the fault of IPv6. It's like blaming Ethernet for allowing a site in
> Australia to reach Europe given Ethernet was only designed for local
> area networks.
>
> The issue at hand is: what does IPv6 directly does to leak information
> about the local machine? Is this a problem? If it is (at all) is it
> possible to fix and how?


Right, and: Avoid designing the fundamental protocols of the Internet such
that privacy is impossible, even if they fix the non-fundamental parts.

--089e012277b4e4bbc504e9e4b0f0
Content-Type: text/html; charset=ISO-8859-1

<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Oct 29, 2013 at 1:32 PM, Octavio Alvarez <span dir="ltr">&lt;<a href="mailto:alvarezp@alvarezp.ods.org" target="_blank">alvarezp@alvarezp.ods.org</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Writing a higher-layer protocol or application that tracks you is not<br>
the fault of IPv6. It&#39;s like blaming Ethernet for allowing a site in<br>
Australia to reach Europe given Ethernet was only designed for local<br>
area networks.<br>
<br>
The issue at hand is: what does IPv6 directly does to leak information<br>
about the local machine? Is this a problem? If it is (at all) is it<br>
possible to fix and how?</blockquote><div><br></div><div>Right, and: Avoid designing the fundamental protocols of the Internet such that privacy is impossible, even if they fix the non-fundamental parts.</div></div></div>

</div>

--089e012277b4e4bbc504e9e4b0f0--

From alvarezp@alvarezp.ods.org  Tue Oct 29 10:43:25 2013
Return-Path: <alvarezp@alvarezp.ods.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EB5411E818C for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 10:43:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3je0mdI22qT8 for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 10:42:56 -0700 (PDT)
Received: from sobre.alvarezp.com (sobre.alvarezp.com [173.230.155.94]) by ietfa.amsl.com (Postfix) with ESMTP id 86D5E11E8137 for <ipv6@ietf.org>; Tue, 29 Oct 2013 10:42:46 -0700 (PDT)
Received: from [192.168.2.251] (189.220.45.207.cable.dyn.cableonline.com.mx [189.220.45.207]) by sobre.alvarezp.com (Postfix) with ESMTPSA id 1EE9E613D; Tue, 29 Oct 2013 13:42:46 -0400 (EDT)
Message-ID: <526FF3A8.2040206@alvarezp.ods.org>
Date: Tue, 29 Oct 2013 10:43:04 -0700
From: Octavio Alvarez <alvarezp@alvarezp.ods.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130821 Icedove/17.0.8
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Subject: Re: Why /64
References: <526CF079.7030804@globis.net> <526E41BC.3080303@gmail.com>	<526E9735.8080708@alvarezp.ods.org> <20131028.184553.78794962.sthaug@nethelp.no> <1382988218.92574.YahooMailNeo@web142504.mail.bf1.yahoo.com> <526F8BC0.505@gmail.com>
In-Reply-To: <526F8BC0.505@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "v6ops@globis.net" <v6ops@globis.net>, "tjc@ecs.soton.ac.uk" <tjc@ecs.soton.ac.uk>, "fred@cisco.com" <fred@cisco.com>, "fgont@si6networks.com" <fgont@si6networks.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 29 Oct 2013 17:43:25 -0000

On 10/29/2013 03:19 AM, Alexandru Petrescu wrote:
> Le 28/10/2013 20:23, Mark ZZZ Smith a écrit :
>>
> Yes, I expect routing to work on larger-than-64 and bitwise boundaries.
> 
> But is also a matter of the subnet mask of the smallest possible subnet.
>  Can one have an IPv6 subnet comprising only 4 entities, on
> Ethernet-compatible, and using Stateless Address Auto-Configuration?

Why would you want to do that? ISPs could use this to give homes just 1
address, breaking innovation again and again, because of whatever lame
excuse, from misinformation to greed.

Public IP addresses, even if firewalled are useful to end devices.







From markzzzsmith@yahoo.com.au  Tue Oct 29 13:11:07 2013
Return-Path: <markzzzsmith@yahoo.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43FED11E8260 for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 13:11:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.942
X-Spam-Level: 
X-Spam-Status: No, score=-1.942 tagged_above=-999 required=5 tests=[AWL=0.157,  BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MYtrayJhRIpf for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 13:11:01 -0700 (PDT)
Received: from nm37.bullet.mail.ne1.yahoo.com (nm37.bullet.mail.ne1.yahoo.com [98.138.229.30]) by ietfa.amsl.com (Postfix) with ESMTP id 3FA9721F9FC7 for <ipv6@ietf.org>; Tue, 29 Oct 2013 13:11:01 -0700 (PDT)
Received: from [127.0.0.1] by nm37.bullet.mail.ne1.yahoo.com with NNFMP; 29 Oct 2013 20:11:00 -0000
Received: from [98.138.90.49] by nm37.bullet.mail.ne1.yahoo.com with NNFMP; 29 Oct 2013 20:08:09 -0000
Received: from [98.139.212.145] by tm2.bullet.mail.ne1.yahoo.com with NNFMP; 29 Oct 2013 20:08:09 -0000
Received: from [98.139.212.194] by tm2.bullet.mail.bf1.yahoo.com with NNFMP; 29 Oct 2013 20:08:09 -0000
Received: from [127.0.0.1] by omp1003.mail.bf1.yahoo.com with NNFMP; 29 Oct 2013 20:08:09 -0000
X-Yahoo-Newman-Property: ymail-4
X-Yahoo-Newman-Id: 578042.19976.bm@omp1003.mail.bf1.yahoo.com
Received: (qmail 11413 invoked by uid 60001); 29 Oct 2013 20:08:09 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s1024; t=1383077288; bh=PAZbxedCzXI6utAFKYjPaqGaqHp91rM1aFdwdfAjm/M=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=WPNQO6w+QwLNXl4+dxRybSsFRPsLVy+xbYpxBgfaDkGgYLFDVEiniiHyvl28lVpOZnj5HLp+JM72E5vN8YO4FKIK8Z7P/g2zeD5XJCF+IZ43jbgtIJs3JpPMylE43G/sKQfaAWGK8Ei2Og60Pj0DZhU+E9G2Vq4wumAofuEYYjg=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.au; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=ycy34+ULlc59J7NKKNjT1CJt4UdAVMqdVakr2wBMTsusb3Wz2JYQH6juHFyuvJPArRivPgcIs2TR9RwR29OlZrtCYZA+zh7q1ncr4XdPuTh2Q1pLHDSL53zgbZZt+Ivz8xzV39DRWHqgmvOvbAuNGXWSqf3x/EKIMTJBk6lEW/A=;
X-YMail-OSG: RhtsNwcVM1mRhQ8GpA1L0kqLPBn9AEaOZTc6BtKUQz0Tvft zAOKfCIIQLKb6enl37uwQ.i.owmJeYpe9tGaEz2I-
Received: from [150.101.221.237] by web142506.mail.bf1.yahoo.com via HTTP; Tue, 29 Oct 2013 13:08:08 PDT
X-Rocket-MIMEInfo: 002.001, CgoKCi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0KPiBGcm9tOiBBbGV4YW5kcnUgUGV0cmVzY3UgPGFsZXhhbmRydS5wZXRyZXNjdUBnbWFpbC5jb20.Cj4gVG86IE1hcmsgWlpaIFNtaXRoIDxtYXJrenp6c21pdGhAeWFob28uY29tLmF1PjsgInN0aGF1Z0BuZXRoZWxwLm5vIiA8c3RoYXVnQG5ldGhlbHAubm8.OyAiYWx2YXJlenBAYWx2YXJlenAub2RzLm9yZyIgPGFsdmFyZXpwQGFsdmFyZXpwLm9kcy5vcmc.Cj4gQ2M6ICJpcHY2QGlldGYub3JnIiA8aXB2NkBpZXRmLm9yZz47ICJ2Nm9wc0BnbG9iaXMBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.160.587
References: <526CF079.7030804@globis.net> <526E41BC.3080303@gmail.com>	<526E9735.8080708@alvarezp.ods.org> <20131028.184553.78794962.sthaug@nethelp.no> <1382988218.92574.YahooMailNeo@web142504.mail.bf1.yahoo.com> <526F8BC0.505@gmail.com>
Message-ID: <1383077288.10442.YahooMailNeo@web142506.mail.bf1.yahoo.com>
Date: Tue, 29 Oct 2013 13:08:08 -0700 (PDT)
From: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
Subject: Re: Why /64
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>, "sthaug@nethelp.no" <sthaug@nethelp.no>, "alvarezp@alvarezp.ods.org" <alvarezp@alvarezp.ods.org>
In-Reply-To: <526F8BC0.505@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "v6ops@globis.net" <v6ops@globis.net>, "tjc@ecs.soton.ac.uk" <tjc@ecs.soton.ac.uk>, "ipv6@ietf.org" <ipv6@ietf.org>, "fred@cisco.com" <fred@cisco.com>, "fgont@si6networks.com" <fgont@si6networks.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 29 Oct 2013 20:11:07 -0000

=0A=0A=0A=0A----- Original Message -----=0A> From: Alexandru Petrescu <alex=
andru.petrescu@gmail.com>=0A> To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au=
>; "sthaug@nethelp.no" <sthaug@nethelp.no>; "alvarezp@alvarezp.ods.org" <al=
varezp@alvarezp.ods.org>=0A> Cc: "ipv6@ietf.org" <ipv6@ietf.org>; "v6ops@gl=
obis.net" <v6ops@globis.net>; "tjc@ecs.soton.ac.uk" <tjc@ecs.soton.ac.uk>; =
"fred@cisco.com" <fred@cisco.com>; "fgont@si6networks.com" <fgont@si6networ=
ks.com>=0A> Sent: Tuesday, 29 October 2013 9:19 PM=0A> Subject: Re: Why /64=
=0A> =0A> Le 28/10/2013 20:23, Mark ZZZ Smith a =E9crit :=0A>> =0A>> =0A>> =
=0A>> =0A>>  ----- Original Message -----=0A>>>  From: "sthaug@nethelp.no" =
<sthaug@nethelp.no> To:=0A>>>  alvarezp@alvarezp.ods.org Cc: alexandru.petr=
escu@gmail.com;=0A>>>  ipv6@ietf.org; v6ops@globis.net; tjc@ecs.soton.ac.uk=
;=0A>>>  fred@cisco.com; fgont@si6networks.com Sent: Tuesday, 29 October=0A=
>>>  2013 4:45 AM Subject: Re: Why /64=0A>>> =0A>>>>>  The IPv4's CIDR conc=
ept (route based on bitwise borders,=0A>>>>>  instead=0A>>>  of=0A>>>>>  8b=
yte) seems to me a good clue for the discussion about the fix=0A>>>>>  64bi=
t limit in IPv6.=0A>>>> =0A>>>>  CIDR is already being used. /80s, /96s and=
 other arbitrary=0A>>>>  netmasks can be set on some devices and should wor=
k. Some of them=0A>>>>  may misbehave, though.=0A>>> =0A>>>  "Some devices"=
? They work on all devices I've tried. And =0A> I=0A>>>  certainly *expect*=
 normal longest prefix match based forwarding to=0A>>>  work, with no arbit=
rary /64 limitation.=0A>>> =0A>> =0A>>  I'd expect it to work too.=0A> =0A>=
 Yes, I expect routing to work on larger-than-64 and bitwise boundaries.=0A=
> =0A> But is also a matter of the subnet mask of the smallest possible sub=
net. =0A> =A0 Can one have an IPv6 subnet comprising only 4 entities, on =
=0A> Ethernet-compatible, and using Stateless Address Auto-Configuration?=
=0A> =0A=0A=0ACertainly. Use a /64. What is the problem with that?=0A=0AReg=
ards,=0AMark.

From brian.e.carpenter@gmail.com  Tue Oct 29 14:35:18 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C42811E8262 for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 14:35:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.469
X-Spam-Level: 
X-Spam-Status: No, score=-102.469 tagged_above=-999 required=5 tests=[AWL=0.130, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PCu7Kl7T6v3j for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 14:35:16 -0700 (PDT)
Received: from mail-pb0-x233.google.com (mail-pb0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 4A30511E827E for <ipv6@ietf.org>; Tue, 29 Oct 2013 14:35:05 -0700 (PDT)
Received: by mail-pb0-f51.google.com with SMTP id wz7so426952pbc.38 for <ipv6@ietf.org>; Tue, 29 Oct 2013 14:35:02 -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=+CxINZRBS+hFna5zJ0sK/EkDigxx0w/mY2hmU4vE3+Y=; b=YJ6Hm8nhxbKr5YRazIFNSvbnZxCIdQHeNjKu4C7ILt6JxFpAbwfUQE8OdfQBd8Z7v5 Bzc2XtSi3BKShw7o/BTGHUU/T4ObFRpGalCpl+9S9SV4P0uTSUmyMLq8qVSkufMTmwc8 zOT7Xejht4+fWHpmJ6mhcaS2JvPo74GHd163eA5YPB/ctDW+7HELjET+tOHAoC451DlR J8Egwx/Psx5yYCWEa3WGQ5T7jak5gnngChW4OnmjznxVeWSBrRD/IrJ+rTf2EydJBsvR 7DLRLw3P53FzHgZuam0WQPXztrPn5/OiK2LrabVXSww1u8fUORtHxiwqaMNIhOY8Iud0 LTWA==
X-Received: by 10.68.197.1 with SMTP id iq1mr1571479pbc.131.1383082502860; Tue, 29 Oct 2013 14:35:02 -0700 (PDT)
Received: from [130.216.38.108] ([130.216.38.108]) by mx.google.com with ESMTPSA id iu7sm36957074pbc.45.2013.10.29.14.34.58 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 29 Oct 2013 14:35:02 -0700 (PDT)
Message-ID: <52702A06.2040102@gmail.com>
Date: Wed, 30 Oct 2013 10:35:02 +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: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar>	<526AA24F.6010609@gmail.com>	<526AACA5.7090604@si6networks.com>	<E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<526AC8AF.4060608@si6networks.com>	<8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com>	<CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com>	<526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org>	<526E43E8.3080601@gmail.com> <526E91A3.8000807@alvarezp.ods.org> <526F888E.20609@gmail.com>
In-Reply-To: <526F888E.20609@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Fernando Gont <fgont@si6networks.com>, Tim Chown <tjc@ecs.soton.ac.uk>, 6man <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 29 Oct 2013 21:35:18 -0000

On 29/10/2013 23:06, Alexandru Petrescu wrote:
..
> Otherwise, the RFC4291 spec _could_ say this:
>> For all unicast addresses, except those that start with the binary
>> value 000, Interface IDs are required to be 64 bits long and MAY be
>> constructed in Modified EUI-64 format.
> 
> or it could say this:
>> For all unicast addresses, except those that start with the binary
>> value 000, Interface IDs MAY be formed using the 'Modified EUI-64'
>> format, in which case their length is 64 bits.

These are exactly the words we have already changed, via the approval
of  draft-ietf-6man-ug. As soon as that draft exits the RFC Editor queue,
they will read:

   "For all unicast addresses, except those that start with the binary
    value 000, Interface IDs are required to be 64 bits long. If derived
    from an IEEE MAC-layer address, they must be constructed in Modified
    EUI-64 format."

This thread is about changing the first sentence, which I think you will
find is a contentious proposal with many pros and cons.

   Brian

From albert.e.manfredi@boeing.com  Tue Oct 29 14:54:15 2013
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C52A11E8264 for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 14:54:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I5n-CmniNnxX for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 14:54:09 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) by ietfa.amsl.com (Postfix) with ESMTP id 0101C11E8214 for <ipv6@ietf.org>; Tue, 29 Oct 2013 14:54:08 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9TLs811012899 for <ipv6@ietf.org>; Tue, 29 Oct 2013 16:54:08 -0500
Received: from XCH-PHX-505.sw.nos.boeing.com (xch-phx-505.sw.nos.boeing.com [137.136.239.61]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9TLs7Lh012895 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Tue, 29 Oct 2013 16:54:08 -0500
Received: from XCH-PHX-503.sw.nos.boeing.com ([169.254.6.120]) by XCH-PHX-505.sw.nos.boeing.com ([169.254.4.133]) with mapi id 14.03.0158.001; Tue, 29 Oct 2013 14:54:07 -0700
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: Why /64
Thread-Topic: Why /64
Thread-Index: AQHO1I578MVVSD9SCUOfg4rMEy/JH5oMqa4A//+NVCA=
Date: Tue, 29 Oct 2013 21:54:06 +0000
Message-ID: <021E64FECA7E5A4699562F4E667164810B4AF4FE@XCH-PHX-503.sw.nos.boeing.com>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar>	<526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch>	<526D3706.5070409@alvarezp.ods.org> <526E43E8.3080601@gmail.com>	<526E91A3.8000807@alvarezp.ods.org> <526F888E.20609@gmail.com> <52702A06.2040102@gmail.com>
In-Reply-To: <52702A06.2040102@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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 29 Oct 2013 21:54:15 -0000

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of B=
rian
> E Carpenter

> These are exactly the words we have already changed, via the approval
> of  draft-ietf-6man-ug. As soon as that draft exits the RFC Editor queue,
> they will read:
>=20
>    "For all unicast addresses, except those that start with the binary
>     value 000, Interface IDs are required to be 64 bits long. If derived
>     from an IEEE MAC-layer address, they must be constructed in Modified
>     EUI-64 format."
>=20
> This thread is about changing the first sentence, which I think you will
> find is a contentious proposal with many pros and cons.

May I wax philosophic for a second?

I too object to the term "required." And I believe in more or less Darwinia=
n survival of the fittest too.

CIDR evolved for a reason: the old 32-bit classful scheme became inadequate=
 when the Internet moved from an academic/military net of a few 10s of thou=
sands, to something for the masses.

CIDR will re-evolve in IPv6, when the Internet evolves from something for t=
he masses to something for the masses of even tiny things.

The idea that any subset of IPv6 addresses MUST have 64 IIDs, let alone the=
 majority subset, is sure not to survive the test of time, in my opinion. N=
ot when you dramatically change the paradigm of what gets connected. Lucky =
for everyone, we do know how to apply CIDR ubiquitously. I hope we don't de=
sign ourselves out of that possibility.

Bert


From jinmei.tatuya@gmail.com  Tue Oct 29 20:09:28 2013
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D7B611E81F4 for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 20:09:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.222
X-Spam-Level: *
X-Spam-Status: No, score=1.222 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0cz6WrQH9B7g for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 20:09:28 -0700 (PDT)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 73AAF21F9C7D for <ipv6@ietf.org>; Tue, 29 Oct 2013 20:09:09 -0700 (PDT)
Received: by mail-wi0-f172.google.com with SMTP id ez12so6148404wid.17 for <ipv6@ietf.org>; Tue, 29 Oct 2013 20:09:08 -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=X7jFqwZBV17Fq4WflV2VQrWcOdXbTu64DGrvkSjKcu8=; b=M/v0j0K79aVjgapHVjIU3aTgRV+jX9DZEqnk/YK3GOiKMvQGkN86YoVYDYamoESCqA UET9DAoweDYOLWaFsOAJbryt0kx3z2PL5aN1tAt4HDZG6CKkFwdpuhSEI2t+WXU1BTZi uaoUpMD+AQJU/QpK12WCYPqDxxmxFzntrjXmtOgqLVJUpQS1ANpuSfvEHgsUUs1dWWY1 iT0qBn4aqpUpjTLa3YkbNAUm3egz9jniUxB6+Nwn/nheJhA69ZdVwejdmHsKDPUmjeva hsblic4UlZ+6AqyuN2++Tf/viZ+XGhb/uYF70AsVFlNeftKT+JEl1aR5q/vxwRUC1Whp c34w==
MIME-Version: 1.0
X-Received: by 10.194.1.139 with SMTP id 11mr2158780wjm.33.1383102548363; Tue, 29 Oct 2013 20:09:08 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.120.167 with HTTP; Tue, 29 Oct 2013 20:09:08 -0700 (PDT)
In-Reply-To: <8392F9BAC6AD5F47920216A6D7853F7E1D581938@BPXM02GP.gisp.nec.co.jp>
References: <8392F9BAC6AD5F47920216A6D7853F7E1D581938@BPXM02GP.gisp.nec.co.jp>
Date: Tue, 29 Oct 2013 20:09:08 -0700
X-Google-Sender-Auth: xUM3khQXC5W1lb2LUHZwiZ0Px-M
Message-ID: <CAJE_bqddRJYDfKg4M05MPhZi6TntmyFMRkjdTPg7-X6AY73kJw@mail.gmail.com>
Subject: Re: I-D Action: draft-kitamura-ipv6-zoneid-free-01.txt
From: =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>
To: Hiroshi Kitamura <kitamura@da.jp.nec.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "Ata, Shingo \(ata@info.eng.osaka-cu.ac.jp\)" <ata@info.eng.osaka-cu.ac.jp>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 30 Oct 2013 03:09:28 -0000

At Mon, 28 Oct 2013 10:43:06 +0000,
Hiroshi Kitamura <kitamura@da.jp.nec.com> wrote:

> > > I think Windows simply picks a default interface if you don't specify
> > > a Zone ID **.
>
> I understand.
>
> A default interface idea is one of methods to achieve not to accompany with "%<Zone-ID>".

<pedantic>
To be precise in this context, this should be a "default zone (ID)"
(and if we use a link-local address as an example, it should be a
"default link (ID)").
</pedantic>

Actually, RFC 4007 states the concept of default zone should be
implemented.  Maybe not many implementations follow that specification
(from a quick check at least FreeBSD supports the concept, although it
seems to be incomplete/buggy), but at least in terms of protocol
architecture we already gave this solution.

But in any case...

> In my I-D:
>  2. Problem Analysis and Goals  . . . . . . . . . . . . . . . . . .  3
>
>  I describe goals and targets as follows.
>
> -----------------------------------
>    Goals of this document are to make end users free from using Zone-
>    ID and to provide environment that they do not require to accompany
>    with %<Zone-ID> to their applications arguments.
>
>    (Non-Targets: people who have enough technical knowledge of
>    networks and do not feel any difficulties to accompany with %<Zone-
>    ID> information are not target. Also, a network environment that is
>    too complicated to deal with for normal end users is not target.)
>
> -----------------------------------

When we discussed the scope architecture, I thought we had an agreed
sense that users who might ever want to use link-local addresses
directly are "people who have enough technical knowledge" and that when
they play with link-local addresses, they know what they are doing and
they'd rather be explicit ("I want to confirm that this particular
router via this interface/link is reachable").  A default zone might
still be useful as it's still deterministic, but I suspect such users
would certainly avoid some magic choice of zones under the hood.

For other types of scopes, the story might be slightly different, but
these scopes are not really used anyway (at least not in a way where zone
boundaries matter), and, in fact, all examples in this draft use
link-locals.  I'd even doubt people who don't have enough technical
knowledge ever want to use any IPv6 addresses directly, let alone
(narrower) scoped ones.

Either my memory in the original discussion is wrong or it's now more
common that non-technical people want to play with scoped IPv6
addresses.  But if it's the latter, I think this draft should first
explain who (except the authors:-) really wants that.  Otherwise it
would be difficult to convince others, especially those who share my
memory of the original discussion, on the need for this trick.

And, in any case, from a quick look, this draft basically only talks
about implementation techniques, not a protocol modification.  So, you
might rather bring it to developer communities first and see if the
idea is accepted.

--
JINMEI, Tatuya

From fgont@si6networks.com  Tue Oct 29 23:57:09 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B975D21E80CC for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 23:57:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.556
X-Spam-Level: 
X-Spam-Status: No, score=-2.556 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VlGj73Hyl2PX for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 23:57:09 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id DE9CC21E80D5 for <ipv6@ietf.org>; Tue, 29 Oct 2013 23:57:05 -0700 (PDT)
Received: from [2001:5c0:1400:a::3b3] by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1VbPi2-0007Oq-A7; Wed, 30 Oct 2013 07:56:54 +0100
Message-ID: <52706F71.40902@si6networks.com>
Date: Tue, 29 Oct 2013 22:31:13 -0400
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>,  Octavio Alvarez <alvarezp@alvarezp.ods.org>, Jeroen Massar <jeroen@massar.ch>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com>	<526AACA5.7090604@si6networks.com>	<E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<526AC8AF.4060608@si6networks.com>	<8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org> <526E43E8.3080601@gmail.com>
In-Reply-To: <526E43E8.3080601@gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, "<ipv6@ietf.org>" <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 30 Oct 2013 06:57:09 -0000

On 10/28/2013 07:00 AM, Alexandru Petrescu wrote:
> 
> I think there is a problem in naming that draft.
> 
> I think the intention of it is not to deprecate EUI-64 altogether.  If
> I'm not wrong EUI-64 is an IEEE concept that IETF reuses, and thus 6man
> wouldn't have the prerogatives to 'deprecate EUI-64'.

Whaat we mean to deprecate is *Modified EUI-64 IIDs -- that is,
Interface identifiers based on the underlying hardware address.



> I think the draft _would_ allow to devise an IP address generation
> mechanism using an EUI-64 formed from something else which is not a
> hardware address.

Our I-D recommends draft-ietf-6man-stable-privacy-addresses.

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





From pld@cs.luc.edu  Tue Oct 29 12:57:44 2013
Return-Path: <pld@cs.luc.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DEC811E8255 for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 12:57:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.149
X-Spam-Level: 
X-Spam-Status: No, score=-2.149 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_51=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LEigmcZsG6fz for <ipv6@ietfa.amsl.com>; Tue, 29 Oct 2013 12:57:38 -0700 (PDT)
Received: from lukasiewicz.cs.luc.edu (lukasiewicz.cs.luc.edu [147.126.65.57]) by ietfa.amsl.com (Postfix) with ESMTP id 0E03211E8293 for <ipv6@ietf.org>; Tue, 29 Oct 2013 12:56:58 -0700 (PDT)
Received: from [10.213.119.4] (unknown [10.38.2.42]) by lukasiewicz.cs.luc.edu (Postfix) with ESMTPA id E3F0D6A237; Tue, 29 Oct 2013 14:56:56 -0500 (CDT)
Message-ID: <52701308.8050003@cs.luc.edu>
Date: Tue, 29 Oct 2013 14:56:56 -0500
From: Peter Dordal <pld@cs.luc.edu>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Jeroen Massar <jeroen@massar.ch>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<526AC8AF.4060608@si6networks.com>	<8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com>	<CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com>	<526CDC59.4070204@massar.ch>	<CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com>	<CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com>	<CAKFn1SG1PC_kA-pO5Or8VyeaOzvLfpmQe0LiiYkXU_HzNqGzCQ@mail.gmail.com>	<526E250E.5050607@massar.ch>	<CAKD1Yr1evbMf1pD4yBrZyvF2XLXGOre3bHDB0gOZTLme7vnh2A@mail.gmail.com>	<526E267E.2070705@massar.ch>	<CAKD1Yr1K+4H+Gq9dWK-tVJu_3_pw+q7Q1owGz69eg6jy--XN5A@mail.gmail.com>	<526E2A56.7070503@massar.ch>	<CAKD1Yr3quaLS8zmDuf301MHL_y+uLQg0UfAEU+Kk-hwfv0oqtw@mail.gmail.com> <526E2E0C.904@massar.ch> <526E9B7F.3020004@cs.luc.edu> <526F831C.5080408@massar.ch>
In-Reply-To: <526F831C.5080408@massar.ch>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 30 Oct 2013 00:32:29 -0700
Cc: Peter Dordal <pld@cs.luc.edu>, "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 29 Oct 2013 19:57:44 -0000

On 10/29/2013 04:42 AM, Jeroen Massar wrote:
> On 2013-10-28 18:14 , Peter Dordal wrote:
>> On 10/28/2013 04:27 AM, Jeroen Massar wrote:
>>> See my other messages: IPv6 Privacy addresses are a myth, they do not
>>> work. You can track people even when you just see IP addresses and
>>> ignore the upper layers. The upper layers just make it easier.
>>>
>>> Greets,
>>>    Jeroen
>>>
>>>
>> In what sense exactly is this claim meant?I agree that "privacy"
>> addresses are in many scenarios not all that private,
>> but I am not sure that makes them useless.
>>
>> 1. Suppose I connect both at work and home; each site has
>> a different /64 prefix. I do not want anyone to correlate my work
>> and home traffic.
> For different sites, not using the MAC-derived EUI-64 is indeed a great
> thing. But you could just as well use DHCPv6 or just pick random number
> like ::5 and use that insted.
I can't use ::5 because my office mate might also like 5.
Perhaps the issue though is that we should call them "random" addresses
rather than "privacy" addresses?

As for DHCPv6, the (one) advantage of SLAAC is that it lets me pick my own
low-order address bits.

> JM: The actual IPv6 Privacy address, including the randomization and
> expiration does not add much there in avoiding tracking.
>
> ....
>
> (If you want to hide on the IP level, use mixnet...)
And if I am going to use tor from the office, I might want to be
particularly sure that I don't use the same IP address I use for my
everyday work.

Ok, privacy addresses are more like window curtains than Faraday cages.
But they still protect against some correlations. (In this they are not
unlike so-called "private browsing")
>
> pld: 2. Suppose I connect to two different remote sites, A and B,
> while at work. I don't want someone reviewing the logs at A and B
> to know the same host made both these connections.
>
> > JM: But they can make a pretty good guess. There will be a lot of meta data
> > in those connections, much of it that will make you unique.
This depends very much on the protocol. Http is not a good example here;
http has scary tons of metadata.

I can easily envision situations where identity "guesses" would be 
pretty flimsy,
**at least if the attacker had access only to the remote endpoint**.
> JM: Try this for the fun of it:
>   - keep your cookies that you have
>   - google for something common "how do you..."
>     and see how autocomplete answers (that is, if you still have that
> enabled). or if you do not (smart! but also makes you unique again)
>     just hit the search button and see which answers you get
>
> now clear those cookies and change that IPv6 address of yours to
> something else random and try again. Gee, you say, same results!?
>
> Now ask a colleague to repeat the same thing on a different host and
> he/she will be getting different results. Gee, why? There is more meta
> information than that...
For the record, I got the *same* result on every machine:
How do you take a screenshot on a mac
            get rid of bedbugs
            divide fractions
            get bed bugs

(Some of these may be local to Chicago. Now I am worried about bedbugs.)


> JM: And HTTP is not the only way to detect things, every protocol has meta
> data.
Client-side smtp? ssh? More to the point, people who are more concerned 
about
privacy may pay more attention to these things than I do, and choose "safer"
protocols.
>> pld: I want to choose different IPv6 addresses at my end
>> for each of these connections, differing of course only in the
>> low-order bits. Again I use SLAAC. How do I create
>> the second IPv6 address except by using privacy addresses?
> JM: The privacy extensions are not per-application and neither
> per-connection. They are time-based instead and thus if you make
> connections during a certain bucket of time they all are coming at the
> same time.
I don't believe this is a "MUST", though I agree that concurrent use of
multiple IPv6 addresses is not quite in the spirit of rfc4941.

I'm back to my earlier point: privacy addresses are like private browsing:
imperfect, possibly even to the point of being misleading, but worth having.
I've been watching your [that is, Jeroen Massar's] _How the Internet 
Sees You_
presentation, but I am not (yet) convinced that privacy addresses
have no value in any circumstances.

Peter Dordal
Loyola University Chicago


From jeroen@massar.ch  Wed Oct 30 01:50:39 2013
Return-Path: <jeroen@massar.ch>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B660711E8118 for <ipv6@ietfa.amsl.com>; Wed, 30 Oct 2013 01:50:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.383
X-Spam-Level: 
X-Spam-Status: No, score=-4.383 tagged_above=-999 required=5 tests=[AWL=1.216,  BAYES_00=-2.599, J_BACKHAIR_55=1, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8JN2WO50OxHW for <ipv6@ietfa.amsl.com>; Wed, 30 Oct 2013 01:50:33 -0700 (PDT)
Received: from icaras.de.unfix.org (icaras.de.unfix.org [78.47.209.234]) by ietfa.amsl.com (Postfix) with ESMTP id 46E2811E81F8 for <ipv6@ietf.org>; Wed, 30 Oct 2013 01:50:25 -0700 (PDT)
Received: from kami.ch.unfix.org (84-73-144-213.dclient.hispeed.ch [84.73.144.213]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeroen) by icaras.de.unfix.org (Postfix) with ESMTPSA id 3C74D801C2A2; Wed, 30 Oct 2013 09:50:15 +0100 (CET)
Message-ID: <5270C819.7000209@massar.ch>
Date: Wed, 30 Oct 2013 09:49:29 +0100
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar
MIME-Version: 1.0
To: Octavio Alvarez <alvarezp@alvarezp.ods.org>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<526AC8AF.4060608@si6networks.com>	<8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com>	<CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com>	<526CDC59.4070204@massar.ch>	<CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com>	<CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com>	<CAKFn1SG1PC_kA-pO5Or8VyeaOzvLfpmQe0LiiYkXU_HzNqGzCQ@mail.gmail.com>	<526E250E.5050607@massar.ch>	<CAKD1Yr1evbMf1pD4yBrZyvF2XLXGOre3bHDB0gOZTLme7vnh2A@mail.gmail.com>	<526E267E.2070705@massar.ch>	<CAKD1Yr1K+4H+Gq9dWK-tVJu_3_pw+q7Q1owGz69eg6jy--XN5A@mail.gmail.com>	<526E2A56.7070503@massar.ch>	<CAKD1Yr3quaLS8zmDuf301MHL_y+uLQg0UfAEU+Kk-hwfv0oqtw@mail.gmail.com> <526E2E0C.904@massar.ch> <526E9B7F.3020004@cs.luc.e du> <526F831C.5080408@massar.ch> <526FF124.2030809@alvarezp.ods.org>
In-Reply-To: <526FF124.2030809@alvarezp.ods.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 30 Oct 2013 08:50:39 -0000

[merging multiple emails in one thread, thus a nice long one;
 TLDR: IP does not make you private in any way]

On 2013-10-28 20:41, Octavio Alvarez wrote:
[..]
>> Please explain this "anti-privacy" concept.
>
> Made up word, as in "explicitly not privacy". It's not the same "this
> address will not make it as easy for a tracker to track me at least in
> some applications but it is possible if you try hard enough and it
> will cost some more resources to the tracker" than "here you go, it's
> me and you even know what brand of NIC I'm using".

If you do not want to expose that randomize the bits a bit. Microsoft
does this for the various Windows implementations exactly for this reason.

> Also, Web != Internet.

I am only using HTTP as an example as it is one of many easy ways to get
extra details.

Note that even if you do not want to use HTTP various "automatic update"
tools will do it for you (the Internet is HTTP after all), and generate
an even bigger signature as it effectively shows which tools you have on
your machine that are able to do these updates.

One only has to look at the SrcIP<->DstIP combo to see who you are
contacting, the lowest port used (if any and if you have it) indicates
the server thus you can automatically learn these, use reverse/asn/whois
lookup to figure out who it is, and keep on correlating with other
connections. If you don't have a port then that is just a bit less info,
just keep a count of 'occurrences' on each side and you can figure out
that a user has less connections than a server. (statistically at least)

Even if your SrcIP changes, you will at one point connect to DstIP again
(or something in that /48) as the update tool wants more updates. If you
are the only Jitsi user, the only one without Adobe updates, etc,
gotcha, you are special...

And no, the population size does not matter, you are special. If you
like it or not: On the Internet you are a very unique snowflake.

[..]
>> As it states 'more difficult'. Since 2001 (RFC3041 which has the same
>> wording and intent) this kind of tracking tech and the compute power has
>> advanced enough though that the difficulty is futile.
>
> Under that logic, punching a hole on my house roof with a drill is
> just more difficult than opening a door, and given a drill is easy to
> buy and not so expensive for people that want, let's all leave our
> doors unlocked and open.

If your house is from the 1800s and still build of wood, then yes, if
you did not bother to upgrade your security and go along with the times
you will be vulnerable.

Instead of your 'leave all doors unlocked', you can realize that that
wooden roof is the bad part thus acknowledge that problem, be aware of
it and stop spreading the myth that a wooden roof is any good.

But that is where your analogy stops, as in the 21st century we would
just make a stone/concrete/multilayered roof and such a roofing problem
would be resolved. (And hopefully you put proper locks on doors, close
the windows etc etc etc)

The multilayered roof though might be relevant in this analogy: use a
mix-net like Tor and voila, you are anonymous and nobody can peek in
through the roof anymore what you are doing in your bedroom....


> I *also think*, however, that changing address without restarting all
> connections just nullifies the effect of any changing-address privacy
> extension.

Restarting *all* connections with the new IP will just demonstrate that
you changed IP and are reconnecting to all previous sites.


> I'm not a pro-removing-EUI-64-device-IDs, I'm just saying that
> randomizing bits does something helpful.

If you think it is helpful, giving the hints I give above and in other
mails, how exactly is it "helpful" at all?


Note, I am against removing /64 length. And I am just stating that the
privacy addresses are nothing special and are not a bonus one is getting
because one has /64 bits of randomness.

Note also that if one choses to do so with the help of DHCPv6 one can
already use longer than /64 prefixes in a network.



On 2013-10-29 18:32, Octavio Alvarez wrote:
> On 10/29/2013 02:42 AM, Jeroen Massar wrote:
>> Try this for the fun of it:
>>  - keep your cookies that you have
>>  - google for something common "how do you..."
>>    and see how autocomplete answers (that is, if you still have that
>> enabled). or if you do not (smart! but also makes you unique again)
>>    just hit the search button and see which answers you get
>>
>> now clear those cookies and change that IPv6 address of yours to
>> something else random and try again. Gee, you say, same results!?
> 
> That has nothing to do with the issue at hand.

It has, it shows that without ('reset' at least) upper level protocol
details various companies easily show that they can know who you are
based on other bits.

Note also that IP is nothing without an application, it is needed.

The issue I raised for this privacy-extensions-subthread of 'why /64' is
that an IP address is easily tracked and that the so called 'privacy
extensions' do not help there. Tools and techniques exist to easily
track you. It does not matter how large the subnet is you are living in,
as the adversary can estimate that size and estimate how many people are
using that subnet (be that a /128, a /64 or a /48).

Note that that tracking is *independent* of the upper protocols. Just
the mere fact that some people connect to X and others connect to Y
makes them easy correlated to each other.

> Whatever changes are done in IPv6 can not protect a user if the user
> likes using an application designed to track him. The "problem" may not
> lie on the application itself, but it certainly doesn't lie on IPv6
> either (read: HTTP cokies...)

You are forgetting that IP is always used in combination with TCP and
UDP (and rarely with something like SCTP or something else). Rarely (but
hopefully more often) folks will use IPSEC to protect the lower layer
bits; but if one can see those bits crypto analysis can be done to
assign an identity too.

IP (be that IPv4 or IPv6) will never ever make you 'private' or
'anonymous'. And no, it does not really matter how much you randomize
those bits.

> Writing a higher-layer protocol or application that tracks you is not
> the fault of IPv6. It's like blaming Ethernet for allowing a site in
> Australia to reach Europe given Ethernet was only designed for local
> area networks.

But as I stated, only seeing IP is good enough for this 'tracking'.

As a small hint, most of this tracking (or better 'correlation') today
happens simply with NetFlow; which just sees src/dst IP and the protocol
and port numbers there are just extra details.

They don't even have to bother looking inside the packets; though it
would make it much easier for many correlations especially with so many
people giving too many details away, hence the well-known and easily
demonstrated HTTP method I mentioned.

> The issue at hand is: what does IPv6 directly does to leak information
> about the local machine? Is this a problem? If it is (at all) is it
> possible to fix and how?

The IPv6 specification itself does not leak anything. Unless you think
it is a problem that the world knows that you are yet another Mac user
based on your NIC. Hence why Microsoft one-time randomizes the EUI-64
portion, that "solve" that part.

It is the way that IP and its underlying protocols (TCP, UDP, SCTP, etc)
are implemented that leak details.

If they did not nmap or even passive fingerprints would not be possible.
Note that these are typically miniscule differences in the stacks.

Very little that can be done by the IETF to resolve these kind of things.

On 2013-10-29 18:38, Scott Brim wrote:
> Right, and: Avoid designing the fundamental protocols of the Internet
> such that privacy is impossible, even if they fix the non-fundamental
> parts.

IP is not made for Privacy. It never has and never will. It is an
end-to-end communications protocol. Hence unless you use a mixnet (eg
Tor) which end-middle-middle-middle-end you are not going to private.

Our add-on friend IPSEC (which is supposed to be in the base IPv6
specification but has been silently ignored by everybody but Microsoft
(Direct Access and Xbox One) only hides&/auths your payload.

The IP layer will still reveal who you are talking to and thus
adversaries that look at connections will know who you are and who you
are talking to and will correlate and will figure you out even when
changing IP addresses all the time or heck prefixes in many cases.

Greets,
 Jeroen


From jeroen@massar.ch  Wed Oct 30 02:02:15 2013
Return-Path: <jeroen@massar.ch>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD85F11E828B for <ipv6@ietfa.amsl.com>; Wed, 30 Oct 2013 02:02:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.056
X-Spam-Level: 
X-Spam-Status: No, score=-5.056 tagged_above=-999 required=5 tests=[AWL=1.543,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X399bqV-D7Ci for <ipv6@ietfa.amsl.com>; Wed, 30 Oct 2013 02:02:09 -0700 (PDT)
Received: from icaras.de.unfix.org (icaras.de.unfix.org [78.47.209.234]) by ietfa.amsl.com (Postfix) with ESMTP id ED08711E8321 for <ipv6@ietf.org>; Wed, 30 Oct 2013 02:02:04 -0700 (PDT)
Received: from kami.ch.unfix.org (84-73-144-213.dclient.hispeed.ch [84.73.144.213]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeroen) by icaras.de.unfix.org (Postfix) with ESMTPSA id 2A7C5801C2A2; Wed, 30 Oct 2013 10:01:57 +0100 (CET)
Message-ID: <5270CAD7.4020300@massar.ch>
Date: Wed, 30 Oct 2013 10:01:11 +0100
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar
MIME-Version: 1.0
To: Peter Dordal <pld@cs.luc.edu>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<526AC8AF.4060608@si6networks.com>	<8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com>	<CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com>	<526CDC59.4070204@massar.ch>	<CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com>	<CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com>	<CAKFn1SG1PC_kA-pO5Or8VyeaOzvLfpmQe0LiiYkXU_HzNqGzCQ@mail.gmail.com>	<526E250E.5050607@massar.ch>	<CAKD1Yr1evbMf1pD4yBrZyvF2XLXGOre3bHDB0gOZTLme7vnh2A@mail.gmail.com>	<526E267E.2070705@massar.ch>	<CAKD1Yr1K+4H+Gq9dWK-tVJu_3_pw+q7Q1owGz69eg6jy--XN5A@mail.gmail.com>	<526E2A56.7070503@massar.ch>	<CAKD1Yr3quaLS8zmDuf301MHL_y+uLQg0UfAEU+Kk-hwfv0oqtw@mail.gmail.com> <526E2E0C.904@massar.ch> <526E9B7F.3020004@cs.luc.edu> <526F831C.5080408@massar.ch> <52701308.8050003@cs.l uc.edu>
In-Reply-To: <52701308.8050003@cs.luc.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 30 Oct 2013 09:02:15 -0000

On 2013-10-29 20:56, Peter Dordal wrote:
> On 10/29/2013 04:42 AM, Jeroen Massar wrote:
[..big snip..]
>>> 1. Suppose I connect both at work and home; each site has
>>> a different /64 prefix. I do not want anyone to correlate my work
>>> and home traffic.
>> For different sites, not using the MAC-derived EUI-64 is indeed a great
>> thing. But you could just as well use DHCPv6 or just pick random number
>> like ::5 and use that insted.
>
> I can't use ::5 because my office mate might also like 5.

That can be a problem in that scheme yes. Hence why DHCPv6 exists.

> Perhaps the issue though is that we should call them "random" addresses
> rather than "privacy" addresses?

That would help yes. They definitely are not private indeed.

[..]
>> (If you want to hide on the IP level, use mixnet...)
> And if I am going to use tor from the office, I might want to be
> particularly sure that I don't use the same IP address I use for my
> everyday work.

Depends on where your adversary is. If he can see you talking to the
first Tor hop, then yes; but otherwise it should not be a problem.

> Ok, privacy addresses are more like window curtains than Faraday cages.

That analogy works for me.

> But they still protect against some correlations. (In this they are not
> unlike so-called "private browsing")

Quite. As even if your cookies are gone, if you connect in the same time
frame from the same IP address, with the same browser User-Agent and
other factors (try EFF panopticlick in private browsing, lots of fun);
you will be the same person for most sites which are a bit good at
correlation.

[..]
> I can easily envision situations where identity "guesses" would be
> pretty flimsy,
> **at least if the attacker had access only to the remote endpoint**.

If I am looking for 1 person out of a million and I can narrow it down
to 200, quite a few adversaries would be quite happy already.

[..]
> For the record, I got the *same* result on every machine:

How many people are using your IP address/prefix? ;)
Does the IP address you use change often?

Note also that you tried the autocomplete, which gives relevant search
queries for you / your area. It is typically better test to check for a
search query that you regularly do (as the way you type it and if you
have autocomplete=on the speed and typos you make is what helps them
identify you).

[..]
>> JM: And HTTP is not the only way to detect things, every protocol has
>> meta data.
> Client-side smtp? ssh? More to the point, people who are more concerned
> about privacy may pay more attention to these things than I do, and choose
> "safer" protocols.

Depends all on what you are protecting against.


>>> pld: I want to choose different IPv6 addresses at my end
>>> for each of these connections, differing of course only in the
>>> low-order bits. Again I use SLAAC. How do I create
>>> the second IPv6 address except by using privacy addresses?
>>>
>> JM: The privacy extensions are not per-application and neither
>> per-connection. They are time-based instead and thus if you make
>> connections during a certain bucket of time they all are coming at the
>> same time.
>>
> I don't believe this is a "MUST", though I agree that concurrent use of
> multiple IPv6 addresses is not quite in the spirit of rfc4941.

Ack.

> I'm back to my earlier point: privacy addresses are like private browsing:
> imperfect, possibly even to the point of being misleading, but worth
> having.

IMHO they are very misleading. In 2001 when they where 'invented' it was
reasonable to call them 'privacy'. In 2013 far from with all the things
learned and tech that has evolved.

> I've been watching your [that is, Jeroen Massar's] _How the Internet
> Sees You_
> presentation, but I am not (yet) convinced that privacy addresses
> have no value in any circumstances.

Trust me, they do not have any value whatsoever.

The above suggestion about an IP per connection/app would only allow the
adversary to count how many connections you made or how many apps you
have running on your host. And thus make it easier to figure out which
one of many you are. Yes, it would explode the database a bit, but
wh00p, big-data is definitely there in 2013.

Greets,
 Jeroen


From lorenzo@google.com  Wed Oct 30 05:27:59 2013
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F8AB21F9E43 for <ipv6@ietfa.amsl.com>; Wed, 30 Oct 2013 05:27:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.886
X-Spam-Level: 
X-Spam-Status: No, score=-1.886 tagged_above=-999 required=5 tests=[AWL=0.091,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7oNeMqd+p7Jd for <ipv6@ietfa.amsl.com>; Wed, 30 Oct 2013 05:27:59 -0700 (PDT)
Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 21ACF11E80FA for <ipv6@ietf.org>; Wed, 30 Oct 2013 05:27:58 -0700 (PDT)
Received: by mail-ie0-f172.google.com with SMTP id tp5so2104358ieb.31 for <ipv6@ietf.org>; Wed, 30 Oct 2013 05:27:58 -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=1sXOrs5quQzVXmJcU61230ZVZMxeYf5akd4K5IZLp7w=; b=INh8xiMX7U6bfKHLOnXRI/XHaDFJ/WWcltgt2oPQRNBxhHg9nUfIQgqo/tZMWhL2Ie WwivQ6HeMFMeZknnr4zCa1jdhdN0Q8bfm7yDVpO4vD003BWQLpu+HSUeGb0tb1FAyi+f MIx2INe1UZVlewX/BBPF6l4Ze07p5h44riPHYS26XPfO59NbdHtve0k23OuRWuab7Vcv JIX14NKLv6chZe2C7/MzFSOwYk4x+/6fiuW32srlwIwNmWZqeuzfi7ITokC36VlMn7j7 7RWCv1PTyhVuPWxXYi0vUtqUQgWWPDFfMvBXnEt3YSMKKrxy3Ghm7Q18S4dniY6gyJZe voZQ==
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=1sXOrs5quQzVXmJcU61230ZVZMxeYf5akd4K5IZLp7w=; b=hHgYU+l+cQ2XKb7XSQ5MHbHXamYvhlwvNhLhHCF/gBZGuZAqJen/L7QctQlze+0Rqo YEFDZ+WX9ggV/Ksi6NmxpadKjiJRXqVMahRJ7VH2m76XbYVe2EV5pi5CzA4lEYWjbAWz qiw9OhrMhurxYqFY3MLkqNgWYjOrJaxLqFBHKXql4qSzlX2BrtTKpshY8gyNrTpZvb/0 +78vGdo5jr92kAOa4qrJlCtgj6vJabDRfEvpaKN23ysh0EaxFDlPpplZ0q4CFniKjsW0 NeA38fOgX3WXuEC+pihwO9UwbXmuGh8j7X3vDBiMhuGsYDIYIaUqc3pvbIzOfExKz7Et LuEg==
X-Gm-Message-State: ALoCoQk4TnhzKdACMSxnnCorI/gA9I6yJxhRQfHUFNx+IlcCAmjF0U9FDDD4nwucIBmEx73ms2vJbWRzCliAjZIDkiP/y8/AoaOVt4pf7nkKErlIjqs39m4P7I5GVomWRqyROp4G2X3As9G8MVF6DnkCq26yyP8zgsQGJCvmY72eB6QkSGBh2t3TGkiQfWSAsIUUR+k0u+fo
X-Received: by 10.50.66.163 with SMTP id g3mr2219285igt.20.1383136078354; Wed, 30 Oct 2013 05:27:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.86.106 with HTTP; Wed, 30 Oct 2013 05:27:38 -0700 (PDT)
In-Reply-To: <021E64FECA7E5A4699562F4E667164810B4AF4FE@XCH-PHX-503.sw.nos.boeing.com>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org> <526E43E8.3080601@gmail.com> <526E91A3.8000807@alvarezp.ods.org> <526F888E.20609@gmail.com> <52702A06.2040102@gmail.com> <021E64FECA7E5A4699562F4E667164810B4AF4FE@XCH-PHX-503.sw.nos.boeing.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 30 Oct 2013 21:27:38 +0900
Message-ID: <CAKD1Yr23LUD-tj0hErFvQo0dHFaJk4BqLc-zVtcFxJ7_+jmwuQ@mail.gmail.com>
Subject: Re: Why /64
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Content-Type: multipart/alternative; boundary=047d7bdca31ca0779604e9f4763d
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 30 Oct 2013 12:27:59 -0000

--047d7bdca31ca0779604e9f4763d
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Oct 30, 2013 at 6:54 AM, Manfredi, Albert E <
albert.e.manfredi@boeing.com> wrote:

> CIDR evolved for a reason: the old 32-bit classful scheme became
> inadequate when the Internet moved from an academic/military net of a few
> 10s of thousands, to something for the masses.
>

Yes, CIDR evolved for a reason: we were running out of IPv4 address space.

We don't have that problem in IPv6 at the moment, and various people have
gone through the math showing that we won't have that problem for decades.

--047d7bdca31ca0779604e9f4763d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Wed, Oct 30, 2013 at 6:54 AM, Manfredi, Albert E <span =
dir=3D"ltr">&lt;<a href=3D"mailto:albert.e.manfredi@boeing.com" target=3D"_=
blank">albert.e.manfredi@boeing.com</a>&gt;</span> wrote:<br><div class=3D"=
gmail_extra">

<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"im"=
><span style=3D"color:rgb(34,34,34)">CIDR evolved for a reason: the old 32-=
bit classful scheme became inadequate when the Internet moved from an acade=
mic/military net of a few 10s of thousands, to something for the masses.</s=
pan></div>

</blockquote><div><br></div><div>Yes, CIDR evolved for a reason: we were ru=
nning out of IPv4 address space.</div><div><br></div><div>We don&#39;t have=
 that problem in IPv6 at the moment, and various people have gone through t=
he math showing that we won&#39;t have that problem for decades.</div>

</div></div></div>

--047d7bdca31ca0779604e9f4763d--

From jmh@joelhalpern.com  Wed Oct 30 05:47:03 2013
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89CD311E8196 for <ipv6@ietfa.amsl.com>; Wed, 30 Oct 2013 05:47:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qcad-aLFWF-0 for <ipv6@ietfa.amsl.com>; Wed, 30 Oct 2013 05:46:58 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by ietfa.amsl.com (Postfix) with ESMTP id B036411E818F for <ipv6@ietf.org>; Wed, 30 Oct 2013 05:46:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 946661C0467; Wed, 30 Oct 2013 05:46:56 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (unknown [192.165.183.201]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id BB83D1C0555; Wed, 30 Oct 2013 05:46:55 -0700 (PDT)
Message-ID: <5270FFBD.7010206@joelhalpern.com>
Date: Wed, 30 Oct 2013 08:46:53 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org> <526E43E8.3080601@gmail.com> <526E91A3.8000807@alvarezp.ods.org> <526F888E.20609@gmail.com> <52702A06.2040102@gmail.com> <021E64FECA7E5A4699562F4E667164810B4AF4FE@XCH-PHX-503.sw.nos.boeing.com> <CAKD1Yr23LUD-tj0hErFvQo0dHFaJk4BqLc-zVtcFxJ7_+jmwuQ@mail.gmail.com>
In-Reply-To: <CAKD1Yr23LUD-tj0hErFvQo0dHFaJk4BqLc-zVtcFxJ7_+jmwuQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 30 Oct 2013 12:47:03 -0000

And we do have classless aggregation and delegation within the upper 64 
bits.

Yours,
Joel

On 10/30/13 8:27 AM, Lorenzo Colitti wrote:
> On Wed, Oct 30, 2013 at 6:54 AM, Manfredi, Albert E
> <albert.e.manfredi@boeing.com <mailto:albert.e.manfredi@boeing.com>> wrote:
>
>     CIDR evolved for a reason: the old 32-bit classful scheme became
>     inadequate when the Internet moved from an academic/military net of
>     a few 10s of thousands, to something for the masses.
>
>
> Yes, CIDR evolved for a reason: we were running out of IPv4 address space.
>
> We don't have that problem in IPv6 at the moment, and various people
> have gone through the math showing that we won't have that problem for
> decades.
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

From brian@innovationslab.net  Wed Oct 30 06:00:36 2013
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4547211E8171 for <ipv6@ietfa.amsl.com>; Wed, 30 Oct 2013 06:00:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.741
X-Spam-Level: 
X-Spam-Status: No, score=-102.741 tagged_above=-999 required=5 tests=[AWL=-0.142, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rpVFjenYS5lo for <ipv6@ietfa.amsl.com>; Wed, 30 Oct 2013 06:00:22 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id EB8EA11E81A4 for <ipv6@ietf.org>; Wed, 30 Oct 2013 06:00:17 -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 EFE188809F for <ipv6@ietf.org>; Wed, 30 Oct 2013 06:00:16 -0700 (PDT)
Received: from 102527254.rudm1.ra.johnshopkins.edu (addr16212925014.ippl.jhmi.edu [162.129.250.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id ACC5C130003 for <ipv6@ietf.org>; Wed, 30 Oct 2013 06:00:16 -0700 (PDT)
Message-ID: <527102DF.90309@innovationslab.net>
Date: Wed, 30 Oct 2013 09:00:15 -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.0.1
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: I-D Action: draft-kitamura-ipv6-zoneid-free-01.txt
References: <8392F9BAC6AD5F47920216A6D7853F7E1D581938@BPXM02GP.gisp.nec.co.jp> <CAJE_bqddRJYDfKg4M05MPhZi6TntmyFMRkjdTPg7-X6AY73kJw@mail.gmail.com>
In-Reply-To: <CAJE_bqddRJYDfKg4M05MPhZi6TntmyFMRkjdTPg7-X6AY73kJw@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Wsej7NdvqfM6MHjBglx6abvigFDRa4ov4"
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 30 Oct 2013 13:00:36 -0000

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

Hi Tatuya,

On 10/29/13 11:09 PM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 wrote:
> At Mon, 28 Oct 2013 10:43:06 +0000,
> Hiroshi Kitamura <kitamura@da.jp.nec.com> wrote:
>=20
>>>> I think Windows simply picks a default interface if you don't specif=
y
>>>> a Zone ID **.
>>
>> I understand.
>>
>> A default interface idea is one of methods to achieve not to accompany=
 with "%<Zone-ID>".
>=20
> <pedantic>
> To be precise in this context, this should be a "default zone (ID)"
> (and if we use a link-local address as an example, it should be a
> "default link (ID)").
> </pedantic>
>=20
> Actually, RFC 4007 states the concept of default zone should be
> implemented.  Maybe not many implementations follow that specification
> (from a quick check at least FreeBSD supports the concept, although it
> seems to be incomplete/buggy), but at least in terms of protocol
> architecture we already gave this solution.
>=20

Yes.

> But in any case...
>=20
>> In my I-D:
>>  2. Problem Analysis and Goals  . . . . . . . . . . . . . . . . . .  3=

>>
>>  I describe goals and targets as follows.
>>
>> -----------------------------------
>>    Goals of this document are to make end users free from using Zone-
>>    ID and to provide environment that they do not require to accompany=

>>    with %<Zone-ID> to their applications arguments.
>>
>>    (Non-Targets: people who have enough technical knowledge of
>>    networks and do not feel any difficulties to accompany with %<Zone-=

>>    ID> information are not target. Also, a network environment that is=

>>    too complicated to deal with for normal end users is not target.)
>>
>> -----------------------------------
>=20
> When we discussed the scope architecture, I thought we had an agreed
> sense that users who might ever want to use link-local addresses
> directly are "people who have enough technical knowledge" and that when=

> they play with link-local addresses, they know what they are doing and
> they'd rather be explicit ("I want to confirm that this particular
> router via this interface/link is reachable").  A default zone might
> still be useful as it's still deterministic, but I suspect such users
> would certainly avoid some magic choice of zones under the hood.
>=20
> For other types of scopes, the story might be slightly different, but
> these scopes are not really used anyway (at least not in a way where zo=
ne
> boundaries matter), and, in fact, all examples in this draft use
> link-locals.  I'd even doubt people who don't have enough technical
> knowledge ever want to use any IPv6 addresses directly, let alone
> (narrower) scoped ones.
>=20
> Either my memory in the original discussion is wrong or it's now more
> common that non-technical people want to play with scoped IPv6
> addresses.  But if it's the latter, I think this draft should first
> explain who (except the authors:-) really wants that.  Otherwise it
> would be difficult to convince others, especially those who share my
> memory of the original discussion, on the need for this trick.

Having been deeply involved in those conversations, I agree with your
recollection of history.  Link-local addresses were not designed to be
used by everyday users.  I don't see the benefit of this draft.

Regards,
Brian



--Wsej7NdvqfM6MHjBglx6abvigFDRa4ov4
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

iQEcBAEBCgAGBQJScQLfAAoJEBOZRqCi7goqm2QH/1cKusvNuMY+eT0Y6CEA9y3F
/VXxba1RwwqFETsGdXWJcIfXEI2QFT70fXKWvKor6irb0uB9YnLNYHF04tt3uq+Z
NbHHTRUgD1lG6onzDZdXcpXjJiElk6+1I64xUko/Yrboz9hN5YRx7HP6lSu4os5a
onvnBYIhPHvJzZpmqzjFVj/0vXGXQGcUTpYmjD5QXH++StgBynjywjtrVR3zCO0A
IT/VR9Imgrudb1Itgc6RKDJ/h57gbOBj4SjLS+jwHRGwsNXZLSNS953hK60F24wH
YZeSF0W6A6Zspmu4QbywO3vZQ4RQlUBRcKC98XqmMdqGQDwF81cEzUXAvZtClEg=
=vzDk
-----END PGP SIGNATURE-----

--Wsej7NdvqfM6MHjBglx6abvigFDRa4ov4--

From alexandru.petrescu@gmail.com  Wed Oct 30 13:33:38 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0225821F9DF1 for <ipv6@ietfa.amsl.com>; Wed, 30 Oct 2013 13:33:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.281
X-Spam-Level: 
X-Spam-Status: No, score=-10.281 tagged_above=-999 required=5 tests=[AWL=-0.032, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LrAg5jMa8jNy for <ipv6@ietfa.amsl.com>; Wed, 30 Oct 2013 13:33:31 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) by ietfa.amsl.com (Postfix) with ESMTP id A911E21F9DDE for <ipv6@ietf.org>; Wed, 30 Oct 2013 13:33:26 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r9UKWtGt005881; Wed, 30 Oct 2013 21:32:55 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 8CED8201E5C; Wed, 30 Oct 2013 21:32:55 +0100 (CET)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 75049201E33; Wed, 30 Oct 2013 21:32:55 +0100 (CET)
Received: from [127.0.0.1] ([132.166.86.1]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id r9UKWnEX025651; Wed, 30 Oct 2013 21:32:54 +0100
Message-ID: <52716CF0.2030503@gmail.com>
Date: Wed, 30 Oct 2013 21:32:48 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>, "sthaug@nethelp.no" <sthaug@nethelp.no>, "alvarezp@alvarezp.ods.org" <alvarezp@alvarezp.ods.org>
Subject: Re: Why /64
References: <526CF079.7030804@globis.net> <526E41BC.3080303@gmail.com>	<526E9735.8080708@alvarezp.ods.org> <20131028.184553.78794962.sthaug@nethelp.no> <1382988218.92574.YahooMailNeo@web142504.mail.bf1.yahoo.com> <526F8BC0.505@gmail.com> <1383077288.10442.YahooMailNeo@web142506.mail.bf1.yahoo.com>
In-Reply-To: <1383077288.10442.YahooMailNeo@web142506.mail.bf1.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "v6ops@globis.net" <v6ops@globis.net>, "tjc@ecs.soton.ac.uk" <tjc@ecs.soton.ac.uk>, "ipv6@ietf.org" <ipv6@ietf.org>, "fred@cisco.com" <fred@cisco.com>, "fgont@si6networks.com" <fgont@si6networks.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 30 Oct 2013 20:33:38 -0000

Le 29/10/2013 21:08, Mark ZZZ Smith a écrit :
>
>
>
>
> ----- Original Message -----
>> From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
>> To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>; "sthaug@nethelp.no" <sthaug@nethelp.no>; "alvarezp@alvarezp.ods.org" <alvarezp@alvarezp.ods.org>
>> Cc: "ipv6@ietf.org" <ipv6@ietf.org>; "v6ops@globis.net" <v6ops@globis.net>; "tjc@ecs.soton.ac.uk" <tjc@ecs.soton.ac.uk>; "fred@cisco.com" <fred@cisco.com>; "fgont@si6networks.com" <fgont@si6networks.com>
>> Sent: Tuesday, 29 October 2013 9:19 PM
>> Subject: Re: Why /64
>>
>> Le 28/10/2013 20:23, Mark ZZZ Smith a écrit :
>>>
>>>
>>>
>>>
>>>   ----- Original Message -----
>>>>   From: "sthaug@nethelp.no" <sthaug@nethelp.no> To:
>>>>   alvarezp@alvarezp.ods.org Cc: alexandru.petrescu@gmail.com;
>>>>   ipv6@ietf.org; v6ops@globis.net; tjc@ecs.soton.ac.uk;
>>>>   fred@cisco.com; fgont@si6networks.com Sent: Tuesday, 29 October
>>>>   2013 4:45 AM Subject: Re: Why /64
>>>>
>>>>>>   The IPv4's CIDR concept (route based on bitwise borders,
>>>>>>   instead
>>>>   of
>>>>>>   8byte) seems to me a good clue for the discussion about the fix
>>>>>>   64bit limit in IPv6.
>>>>>
>>>>>   CIDR is already being used. /80s, /96s and other arbitrary
>>>>>   netmasks can be set on some devices and should work. Some of them
>>>>>   may misbehave, though.
>>>>
>>>>   "Some devices"? They work on all devices I've tried. And
>> I
>>>>   certainly *expect* normal longest prefix match based forwarding to
>>>>   work, with no arbitrary /64 limitation.
>>>>
>>>
>>>   I'd expect it to work too.
>>
>> Yes, I expect routing to work on larger-than-64 and bitwise boundaries.
>>
>> But is also a matter of the subnet mask of the smallest possible subnet.
>>    Can one have an IPv6 subnet comprising only 4 entities, on
>> Ethernet-compatible, and using Stateless Address Auto-Configuration?
>>
>
>
> Certainly. Use a /64. What is the problem with that?

As I see it the problem is that /64 supports more than 4 entities; I 
would like a link that only has 4 entities.  Maybe DAD would be safe to 
assume to take shorter time?

Alex

>
> Regards,
> Mark.
>
>



From alexandru.petrescu@gmail.com  Wed Oct 30 13:37:51 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 198BF11E8143 for <ipv6@ietfa.amsl.com>; Wed, 30 Oct 2013 13:37:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.28
X-Spam-Level: 
X-Spam-Status: No, score=-10.28 tagged_above=-999 required=5 tests=[AWL=-0.031, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dEsA3jJqPXwM for <ipv6@ietfa.amsl.com>; Wed, 30 Oct 2013 13:37:44 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) by ietfa.amsl.com (Postfix) with ESMTP id 7121F21E8097 for <ipv6@ietf.org>; Wed, 30 Oct 2013 13:37:41 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r9UKbYV6007400; Wed, 30 Oct 2013 21:37:34 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id C8912201DCF; Wed, 30 Oct 2013 21:37:34 +0100 (CET)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id B4C0B200DA1; Wed, 30 Oct 2013 21:37:34 +0100 (CET)
Received: from [127.0.0.1] ([132.166.86.1]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id r9UKbXa7026839; Wed, 30 Oct 2013 21:37:34 +0100
Message-ID: <52716E0D.2090602@gmail.com>
Date: Wed, 30 Oct 2013 21:37:33 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar>	<526AA24F.6010609@gmail.com>	<526AACA5.7090604@si6networks.com>	<E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<526AC8AF.4060608@si6networks.com>	<8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com>	<CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com>	<526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org>	<526E43E8.3080601@gmail.com> <526E91A3.8000807@alvarezp.ods.org> <526F888E.20609@gmail.com> <52702A06.2040102@gmail.com>
In-Reply-To: <52702A06.2040102@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Fernando Gont <fgont@si6networks.com>, Tim Chown <tjc@ecs.soton.ac.uk>, 6man <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 30 Oct 2013 20:37:51 -0000

Le 29/10/2013 22:35, Brian E Carpenter a Ã©crit :
> On 29/10/2013 23:06, Alexandru Petrescu wrote:
> ..
>> Otherwise, the RFC4291 spec _could_ say this:
>>> For all unicast addresses, except those that start with the binary
>>> value 000, Interface IDs are required to be 64 bits long and MAY be
>>> constructed in Modified EUI-64 format.
>>
>> or it could say this:
>>> For all unicast addresses, except those that start with the binary
>>> value 000, Interface IDs MAY be formed using the 'Modified EUI-64'
>>> format, in which case their length is 64 bits.
>
> These are exactly the words we have already changed, via the approval
> of  draft-ietf-6man-ug. As soon as that draft exits the RFC Editor queue,
> they will read:
>
>     "For all unicast addresses, except those that start with the binary
>      value 000, Interface IDs are required to be 64 bits long. If derived
>      from an IEEE MAC-layer address, they must be constructed in Modified
>      EUI-64 format."

Sounds reasonable.  It compares favorably IMHO to RFC4291:
>   For all unicast addresses, except those that start with the binary
>    value 000, Interface IDs are required to be 64 bits long and to be
>    constructed in Modified EUI-64 format.
 >
> This thread is about changing the first sentence, which I think you will
> find is a contentious proposal with many pros and cons.

Yes it is.

Alex

>
>     Brian
>
>



From alexandru.petrescu@gmail.com  Wed Oct 30 13:46:23 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77A8811E8136 for <ipv6@ietfa.amsl.com>; Wed, 30 Oct 2013 13:46:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.28
X-Spam-Level: 
X-Spam-Status: No, score=-10.28 tagged_above=-999 required=5 tests=[AWL=-0.031, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mykbWKBdynee for <ipv6@ietfa.amsl.com>; Wed, 30 Oct 2013 13:46:17 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) by ietfa.amsl.com (Postfix) with ESMTP id 0C94821E8097 for <ipv6@ietf.org>; Wed, 30 Oct 2013 13:46:11 -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 r9UKk3Xq027574 for <ipv6@ietf.org>; Wed, 30 Oct 2013 21:46:03 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 511E8201EE0 for <ipv6@ietf.org>; Wed, 30 Oct 2013 21:46:03 +0100 (CET)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 4A052201DCF for <ipv6@ietf.org>; Wed, 30 Oct 2013 21:46:03 +0100 (CET)
Received: from [127.0.0.1] ([132.166.86.1]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id r9UKjw7m029038 for <ipv6@ietf.org>; Wed, 30 Oct 2013 21:46:02 +0100
Message-ID: <52717006.5000806@gmail.com>
Date: Wed, 30 Oct 2013 21:45:58 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com>	<526AACA5.7090604@si6networks.com>	<E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk>	<526AC8AF.4060608@si6networks.com>	<8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com>	<CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com>	<526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org>	<526E43E8.3080601@gmail.com> <526E91A3.8000807@alvarezp.ods.org>	<526F888E.20609@gmail.com> <52702A06.2040102@gmail.com>	<021E64FECA7E5A4699562F4E667164810B4AF4FE@XCH-PHX-503.sw.nos.boeing.com> <CAKD1Yr23LUD-tj0hErFvQo0dHFaJk4BqLc-zVtcFxJ7_+jmwuQ@mail.gmail.com>
In-Reply-To: <CAKD1Yr23LUD-tj0hErFvQo0dHFaJk4BqLc-zVtcFxJ7_+jmwuQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 30 Oct 2013 20:46:23 -0000

Le 30/10/2013 13:27, Lorenzo Colitti a écrit :
> On Wed, Oct 30, 2013 at 6:54 AM, Manfredi, Albert E
> <albert.e.manfredi@boeing.com <mailto:albert.e.manfredi@boeing.com>> wrote:
>
>     CIDR evolved for a reason: the old 32-bit classful scheme became
>     inadequate when the Internet moved from an academic/military net of
>     a few 10s of thousands, to something for the masses.
>
>
> Yes, CIDR evolved for a reason: we were running out of IPv4 address space.
>
> We don't have that problem in IPv6 at the moment, and various people
> have gone through the math showing that we won't have that problem for
> decades.

I guess we could live through the same decades, and more, if we didnt 
have that 64 limit.

Alex

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



From ek@google.com  Wed Oct 30 20:46:03 2013
Return-Path: <ek@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E34411E8309 for <ipv6@ietfa.amsl.com>; Wed, 30 Oct 2013 20:46:02 -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=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id us7XRtDGNFCL for <ipv6@ietfa.amsl.com>; Wed, 30 Oct 2013 20:45:57 -0700 (PDT)
Received: from mail-qe0-x22a.google.com (mail-qe0-x22a.google.com [IPv6:2607:f8b0:400d:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 5BC4D11E8306 for <ipv6@ietf.org>; Wed, 30 Oct 2013 20:45:56 -0700 (PDT)
Received: by mail-qe0-f42.google.com with SMTP id gc15so1435740qeb.29 for <ipv6@ietf.org>; Wed, 30 Oct 2013 20:45:55 -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:content-transfer-encoding; bh=y+dHQ08mHqSqXFu1MHOSIlOUTMT/1mv5vfGrtOeo/bw=; b=K8RLtLuN+j39ChTdRb8P64woaIG/Cv20SIn1KS/i50fol71BlNtNGobxu71pUhz5xb pYWgjzy9T/SEdeB/dajDwORV7E9Ms3KyQzkUANpShnPpf0WL/Lkt15hE982ylPNUJGJK 5qBVfJURHCtY5n7+KWtr8NXrlt+d5LhyklJ8CX45KrchlUCGkbYwsTt41KyOAWFHMqWD RWf1QgZtHUxyNs8ylwy7khF0r+jFzFzyE/+OG4tYTFc3M+zpreo5m2h/jVNvpQCDiYfv WB7R7BBvNwANYnrb/A6+3qAAnwcV56w+HcYh1TeyyY0MGmbC0NZokiDack4q43dMX5Tc oBiA==
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:content-transfer-encoding; bh=y+dHQ08mHqSqXFu1MHOSIlOUTMT/1mv5vfGrtOeo/bw=; b=T918yDHAdRA2YC/vTKFH6f27ZCXsiDhlmqfrCnIviCVooo+YrWV+Q9N0gs5APFBVk8 QS059DCgB8Ab03QEUbNvA9g5VEgFxBF1ApK4cpUr6jlekUPXtqp+jvp1ftX/hI+94ok7 jlzf2Y/7QhgUYFFUvVNtcGQLqGxXYkzCxZ9VRhmZdhZfy0Wk6KiBc9WGKHqOjy4FdeDf PWYJnK/8k2wWkI8BxsAPCefYcXwgSlO3UWxnVBwWae+POH/tsQfrFkPbbajGTXsuQmYu ylb2h/qQL2TS7wBoQRMpTlmBhjcVMg5BhCSqB90Y1QegwbYp+ykSRFokiu3jEpg8egxb 57qg==
X-Gm-Message-State: ALoCoQnmFG4C1yatuXD1XdMjXrgbwG+gRu9RGHP3u9S7CM0FlSS251Lh2HIDEPu1/NFwavDW7/uZ+7aRJ/QRZ+HXfmNn9HiAHAKg7WjGeEi4XsBlrQGp4z7Hj7BENPQjMBVm0ZEka4j7FBHt+MBlGcvXrr2udzEytX8vNYamfkZRZt6AGKly1ALBprr8Qrvwr4nE9bQqRNPD
X-Received: by 10.224.55.80 with SMTP id t16mr2239382qag.106.1383191155420; Wed, 30 Oct 2013 20:45:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.36.198 with HTTP; Wed, 30 Oct 2013 20:45:35 -0700 (PDT)
In-Reply-To: <52717006.5000806@gmail.com>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org> <526E43E8.3080601@gmail.com> <526E91A3.8000807@alvarezp.ods.org> <526F888E.20609@gmail.com> <52702A06.2040102@gmail.com> <021E64FECA7E5A4699562F4E667164810B4AF4FE@XCH-PHX-503.sw.nos.boeing.com> <CAKD1Yr23LUD-tj0hErFvQo0dHFaJk4BqLc-zVtcFxJ7_+jmwuQ@mail.gmail.com> <52717006.5000806@gmail.com>
From: Erik Kline <ek@google.com>
Date: Wed, 30 Oct 2013 20:45:35 -0700
Message-ID: <CAAedzxro3Y_DwScfk9KE_uGP-XAxsTQ0TKgi0X8PL7dRwbTYJQ@mail.gmail.com>
Subject: Re: Why /64
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 31 Oct 2013 03:46:03 -0000

On 30 October 2013 13:45, Alexandru Petrescu
<alexandru.petrescu@gmail.com> wrote:
> Le 30/10/2013 13:27, Lorenzo Colitti a =C3=A9crit :
>>
>> On Wed, Oct 30, 2013 at 6:54 AM, Manfredi, Albert E
>> <albert.e.manfredi@boeing.com <mailto:albert.e.manfredi@boeing.com>>
>> wrote:
>>
>>     CIDR evolved for a reason: the old 32-bit classful scheme became
>>     inadequate when the Internet moved from an academic/military net of
>>     a few 10s of thousands, to something for the masses.
>>
>>
>> Yes, CIDR evolved for a reason: we were running out of IPv4 address spac=
e.
>>
>> We don't have that problem in IPv6 at the moment, and various people
>> have gone through the math showing that we won't have that problem for
>> decades.
>
>
> I guess we could live through the same decades, and more, if we didnt hav=
e
> that 64 limit.

I don't think we should be designing a "solution" for a problem that
we don't actually have.

From alexandru.petrescu@gmail.com  Wed Oct 30 22:51:32 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1431C11E81CB for <ipv6@ietfa.amsl.com>; Wed, 30 Oct 2013 22:51:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.278
X-Spam-Level: 
X-Spam-Status: No, score=-10.278 tagged_above=-999 required=5 tests=[AWL=-0.029, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kat2WeQjbjqO for <ipv6@ietfa.amsl.com>; Wed, 30 Oct 2013 22:51:25 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) by ietfa.amsl.com (Postfix) with ESMTP id 7BF6811E80E4 for <ipv6@ietf.org>; Wed, 30 Oct 2013 22:51: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 r9V5pKkY019150; Thu, 31 Oct 2013 06:51:20 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 07368201673; Thu, 31 Oct 2013 06:51:21 +0100 (CET)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id F0428201610; Thu, 31 Oct 2013 06:51:20 +0100 (CET)
Received: from [127.0.0.1] ([132.166.86.4]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id r9V5pBPL001841; Thu, 31 Oct 2013 06:51:20 +0100
Message-ID: <5271EFCF.6000101@gmail.com>
Date: Thu, 31 Oct 2013 06:51:11 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Erik Kline <ek@google.com>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org> <526E43E8.3080601@gmail.com> <526E91A3.8000807@alvarezp.ods.org> <526F888E.20609@gmail.com> <52702A06.2040102@gmail.com> <021E64FECA7E5A4699562F4E667164810B4AF4FE@XCH-PHX-503.sw.nos.boeing.com> <CAKD1Yr23LUD-tj0hErFvQo0dHFaJk4BqLc-zVtcFxJ7_+jmwuQ@mail.gmail.com> <52717006.5000806@gmail.com> <CAAedzxro3Y_DwScfk9KE_uGP-XAxsTQ0TKgi0X8PL7dRwbTYJQ@mail.gmail.com>
In-Reply-To: <CAAedzxro3Y_DwScfk9KE_uGP-XAxsTQ0TKgi0X8PL7dRwbTYJQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 31 Oct 2013 05:51:32 -0000

Le 31/10/2013 04:45, Erik Kline a Ã©crit :
> On 30 October 2013 13:45, Alexandru Petrescu
> <alexandru.petrescu@gmail.com> wrote:
>> Le 30/10/2013 13:27, Lorenzo Colitti a Ã©crit :
>>>
>>> On Wed, Oct 30, 2013 at 6:54 AM, Manfredi, Albert E
>>> <albert.e.manfredi@boeing.com <mailto:albert.e.manfredi@boeing.com>>
>>> wrote:
>>>
>>>      CIDR evolved for a reason: the old 32-bit classful scheme became
>>>      inadequate when the Internet moved from an academic/military net of
>>>      a few 10s of thousands, to something for the masses.
>>>
>>>
>>> Yes, CIDR evolved for a reason: we were running out of IPv4 address space.
>>>
>>> We don't have that problem in IPv6 at the moment, and various people
>>> have gone through the math showing that we won't have that problem for
>>> decades.
>>
>>
>> I guess we could live through the same decades, and more, if we didnt have
>> that 64 limit.
>
> I don't think we should be designing a "solution" for a problem that
> we don't actually have.

The 64 limit problem is there in the inherent design.

One easy way to observe it is to connect to numerous operators and be 
surprised to only obtain a 64 and be unable to further extend one's 
Ethernet network.

Other ways that may be more difficult to need and observe is with 
smaller subnets (4-max node).

Alex

>
>



From markzzzsmith@yahoo.com.au  Thu Oct 31 04:52:58 2013
Return-Path: <markzzzsmith@yahoo.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E55311E8327 for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 04:52:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.642
X-Spam-Level: 
X-Spam-Status: No, score=-1.642 tagged_above=-999 required=5 tests=[AWL=-0.162, BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7gqEoCxYI2Lr for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 04:52:52 -0700 (PDT)
Received: from nm1-vm1.bullet.mail.bf1.yahoo.com (nm1-vm1.bullet.mail.bf1.yahoo.com [98.139.213.163]) by ietfa.amsl.com (Postfix) with ESMTP id 4FFD411E815B for <ipv6@ietf.org>; Thu, 31 Oct 2013 04:52:52 -0700 (PDT)
Received: from [98.139.212.150] by nm1.bullet.mail.bf1.yahoo.com with NNFMP; 31 Oct 2013 11:52:51 -0000
Received: from [98.139.212.248] by tm7.bullet.mail.bf1.yahoo.com with NNFMP; 31 Oct 2013 11:52:51 -0000
Received: from [127.0.0.1] by omp1057.mail.bf1.yahoo.com with NNFMP; 31 Oct 2013 11:52:51 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 705149.81766.bm@omp1057.mail.bf1.yahoo.com
Received: (qmail 40935 invoked by uid 60001); 31 Oct 2013 11:52:51 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s1024; t=1383220371; bh=ETNX84oT35PrWuAdYntYADUv1gaJ1UPhdDv8CxLWyao=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=ed/GC3yHhvs6cCZgTH0pguzs5HW5uYhq+j3W2kMng0J4fo1GjxmLQb/4SWW4ndDgr0YJJvjdvhXLlp+MBclXvkFNRqwnmButsXMqpOYLymVPSoDr792wcpzkzRZBqZJSF8VqAjd3VYJ7B4GRVGg3Ow9pDAWnRQyn1rzjr2GXLO4=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.au; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=uHW2HwA33WartgoHEDUOo5XY+us590dhO2GTWGYfmJKAjI0JfglNt9lbB/EGFF6fT06zPwDkqhJ1z+HoOHwQDABr5j+Tam2pCYI44HDiQFW4Vgy/DpBPOwjZBZXk1777OoA6J/OHc97s7iIaNRgi6wW7ld+pRS/DEl/etWOjaaw=;
X-YMail-OSG: OeIn88wVM1k4zkoyal5E90yKETNLNY0krCKSXhRuvxvVQDY wVB_wwAJ0sqfzwhBSO4ouhmLz_t1liIAM6tqHRiZ9Psc19utCWdunyLhxevL Nn7Hcaz4XwDXBRpfY5newSt0s3d9s8a9AELu0mwN1fNzKfl64CQjBip8claX jjDprwBKjg.m6b635UVKh6JEAcFpBNvg2TapQUiqU8QuN3QL88D_A2SIc.za c6dL0Ffaz4yjmym3hfRafDx8P2H99Ot9_lCUMqp5BFkXYTsV7akBu45yu2lf L0oOG9CFotuo6IiocPVfe2DKII5demeExKdWlLbU.vXccRDRwgSflJxT_cML hazDBxczeVJFU0z.bNLS0i_GJ3bAl_o7KIhvLyaVIzWRhP_WEQ95II3t3h0B hqDR44JZxJfVxIRJhuv0oY.pn3NNONY4Ec_9mCR6AZrrVFg0qSi6gVTcROkM 8LkbC6.6GG9O4et_KXTh_VSxfhbnwHlV1U1h2XqP5TBGX2q0nVQSHeXBXyRh K7jouhnCD7DxKY8047WApBSWymP3NgqAz7_6uA.Wb5aliJBJnDGlKDNInS48 TT8yftlV02fIQgVn9fellH7pmMbar2owEQM_gxadkHEo-
Received: from [150.101.221.237] by web142504.mail.bf1.yahoo.com via HTTP; Thu, 31 Oct 2013 04:52:51 PDT
X-Rocket-MIMEInfo: 002.001, CgoKCi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0KPiBGcm9tOiBBbGV4YW5kcnUgUGV0cmVzY3UgPGFsZXhhbmRydS5wZXRyZXNjdUBnbWFpbC5jb20.Cj4gVG86IE1hcmsgWlpaIFNtaXRoIDxtYXJrenp6c21pdGhAeWFob28uY29tLmF1PjsgInN0aGF1Z0BuZXRoZWxwLm5vIiA8c3RoYXVnQG5ldGhlbHAubm8.OyAiYWx2YXJlenBAYWx2YXJlenAub2RzLm9yZyIgPGFsdmFyZXpwQGFsdmFyZXpwLm9kcy5vcmc.Cj4gQ2M6ICJpcHY2QGlldGYub3JnIiA8aXB2NkBpZXRmLm9yZz47ICJ2Nm9wc0BnbG9iaXMBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.161.596
References: <526CF079.7030804@globis.net> <526E41BC.3080303@gmail.com>	<526E9735.8080708@alvarezp.ods.org> <20131028.184553.78794962.sthaug@nethelp.no> <1382988218.92574.YahooMailNeo@web142504.mail.bf1.yahoo.com> <526F8BC0.505@gmail.com> <1383077288.10442.YahooMailNeo@web142506.mail.bf1.yahoo.com> <52716CF0.2030503@gmail.com>
Message-ID: <1383220371.40823.YahooMailNeo@web142504.mail.bf1.yahoo.com>
Date: Thu, 31 Oct 2013 04:52:51 -0700 (PDT)
From: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
Subject: Re: Why /64
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>, "sthaug@nethelp.no" <sthaug@nethelp.no>, "alvarezp@alvarezp.ods.org" <alvarezp@alvarezp.ods.org>
In-Reply-To: <52716CF0.2030503@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "v6ops@globis.net" <v6ops@globis.net>, "tjc@ecs.soton.ac.uk" <tjc@ecs.soton.ac.uk>, "ipv6@ietf.org" <ipv6@ietf.org>, "fred@cisco.com" <fred@cisco.com>, "fgont@si6networks.com" <fgont@si6networks.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 31 Oct 2013 11:52:58 -0000

=0A=0A=0A=0A----- Original Message -----=0A> From: Alexandru Petrescu <alex=
andru.petrescu@gmail.com>=0A> To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au=
>; "sthaug@nethelp.no" <sthaug@nethelp.no>; "alvarezp@alvarezp.ods.org" <al=
varezp@alvarezp.ods.org>=0A> Cc: "ipv6@ietf.org" <ipv6@ietf.org>; "v6ops@gl=
obis.net" <v6ops@globis.net>; "tjc@ecs.soton.ac.uk" <tjc@ecs.soton.ac.uk>; =
"fred@cisco.com" <fred@cisco.com>; "fgont@si6networks.com" <fgont@si6networ=
ks.com>=0A> Sent: Thursday, 31 October 2013 7:32 AM=0A> Subject: Re: Why /6=
4=0A> =0A> Le 29/10/2013 21:08, Mark ZZZ Smith a =E9crit :=0A>> =0A>> =0A<s=
nip>=0A>>>  But is also a matter of the subnet mask of the smallest possibl=
e =0A> subnet.=0A>>> =A0 =A0 Can one have an IPv6 subnet comprising only 4 =
entities, on=0A>>>  Ethernet-compatible, and using Stateless Address Auto-C=
onfiguration?=0A>>> =0A>> =0A>> =0A>>  Certainly. Use a /64. What is the pr=
oblem with that?=0A> =0A> As I see it the problem is that /64 supports more=
 than 4 entities; I =0A> would like a link that only has 4 entities.=A0=0A=
=0AHow would you automate growing the subnet to accommodate adding a 5th de=
vice?=0A=0AIt is quite painful to grow a public addressed IPv4 subnet, alth=
ough NAT has suppressed that cost in residential cases because allows "exce=
ssively large" subnets to be used too (how many houses have 254 devices, "n=
eeding" a 192.168.0/24 subnet on the LAN interface?).=0A=0APublic IPv6 with=
 "right sized" subnets would expose that task and cost to people who haven'=
t experienced it before (or rather, more likely expose it to technical rela=
tives like us if we're available), and it is likely that CPE vendors would =
react by resorting to using IPv6 NAT and a nice large /64 on the LAN interf=
ace to again hide it.=0A=0A> Maybe DAD would be safe to=A0=0A=0A> assume to=
 take shorter time?=0A>=A0=0A=0AHow would that allow DAD to be performed in=
 a shorter time? The DAD process isn't proportional to the number of addres=
ses on the subnet.=0A=0AUsing ARIN XX-Small fees ($500 p/a, /22 for IPv4, /=
40 for IPv6), as IPv4 addresses cost $0.48 each per annum, and IPv6 address=
es cost $1.62E-024 each per annum, there is no need to spend any effort and=
 time trying to develop mechanisms that would "right size" an IPv6 subnet t=
o save IP address costs, and that is the only reason I can think of as to w=
hy somebody would want to do that.=0A=0ARegards,=0AMark.

From ek@google.com  Thu Oct 31 14:08:18 2013
Return-Path: <ek@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BB7F21E8088 for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 14:08:18 -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=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FrKLqXt9nfgz for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 14:08:02 -0700 (PDT)
Received: from mail-qe0-x232.google.com (mail-qe0-x232.google.com [IPv6:2607:f8b0:400d:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id 6080611E8231 for <ipv6@ietf.org>; Thu, 31 Oct 2013 14:07:44 -0700 (PDT)
Received: by mail-qe0-f50.google.com with SMTP id 1so2079136qee.23 for <ipv6@ietf.org>; Thu, 31 Oct 2013 14:07:43 -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=mjHx+kqjrlbGuO/0h3PFdnh1RFIIdRG8i9SaCzVDJo4=; b=Vb3cYhJKw2xoiSkOsu6njNhj4DQ7ZpPaXQ3HWsQqRf4iJg0zLW8G+t7B9BGfNkvoO9 7b1Jr3VCr+Myaczc6y74Q8sBdNSwN+teNKDQ91bnKUGASQoFm1jCZBgotP3AptJTzagB pUGlcrxb8KzzbYEjX2cIogGN6RWD/Vov7XCgP4bXawLbkzJ7mADAoEe7CqDqq2uMu981 GcjuCnci/yWe1h1Ux/GZFjCReiKN4gZmhtNKT8RwhUqRcGyUeoM5NJvinMgM+hriCBUU zR9z+7OA+byUjTR1UokupdSBFXZOV0VvqYosnEfRuWqrKt5nU2FgxgFwfPg7p+jRJHZ3 S8nA==
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=mjHx+kqjrlbGuO/0h3PFdnh1RFIIdRG8i9SaCzVDJo4=; b=B2fgHy6HMY+75nHknJl7vVCrXe4k1Kk4Mwa/8igcgIOm72lxYL5fJtYhhbzyzzMmWp rc584krIdF2fdIrj/xBZVIzHCU8Z1UiskM+lw6tSv06VGpN3Rk17jjNs9VS6Oq5OFXKV 8q3TtFOkrn8ZUS61sObKRY+HfFapcTn/s4Bqz9c6m3LCJVA8XzMGuNBAuXn/KZXGzbX8 tUcv/BNXDERVVINJjFPbqD4Lp+/qIKMkAxT93WVl0850m9qQWSXJXqg6bQa7xm5LNF/j wNWIRShwue9B3IV6UK5G5YkGadLb+gF94Mu9Ug4OG9LWyQkGBrtw5x9ZboDxiN+5JHzA TeaA==
X-Gm-Message-State: ALoCoQk0P3ebs2NSdzVftMQnQtEdATo45kqYpDX2qV08z93fdzUK8UKHrj039iPkb2RzkExJnf5ZR3Kgnt8Y8wg/NpgFy98DQGSqnVEG2GUHMSht2ZRQChmlx9JQd1/C2JsUzNzqw2/WyectE6OEClyVSruuN6DXkMel1201ioFz/gxzWNoVQY053J8XTLkjlEfhyn3gFx7H
X-Received: by 10.49.26.6 with SMTP id h6mr6956563qeg.75.1383253663842; Thu, 31 Oct 2013 14:07:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.36.198 with HTTP; Thu, 31 Oct 2013 14:07:22 -0700 (PDT)
In-Reply-To: <5271EFCF.6000101@gmail.com>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org> <526E43E8.3080601@gmail.com> <526E91A3.8000807@alvarezp.ods.org> <526F888E.20609@gmail.com> <52702A06.2040102@gmail.com> <021E64FECA7E5A4699562F4E667164810B4AF4FE@XCH-PHX-503.sw.nos.boeing.com> <CAKD1Yr23LUD-tj0hErFvQo0dHFaJk4BqLc-zVtcFxJ7_+jmwuQ@mail.gmail.com> <52717006.5000806@gmail.com> <CAAedzxro3Y_DwScfk9KE_uGP-XAxsTQ0TKgi0X8PL7dRwbTYJQ@mail.gmail.com> <5271EFCF.6000101@gmail.com>
From: Erik Kline <ek@google.com>
Date: Thu, 31 Oct 2013 14:07:22 -0700
Message-ID: <CAAedzxo3UpF57DEEWfT7M2evX8nPrevXqTENKif0z5ANR1eLZA@mail.gmail.com>
Subject: Re: Why /64
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Content-Type: text/plain; charset=UTF-8
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 31 Oct 2013 21:08:19 -0000

>>>> Yes, CIDR evolved for a reason: we were running out of IPv4 address
>>>> space.
>>>>
>>>> We don't have that problem in IPv6 at the moment, and various people
>>>> have gone through the math showing that we won't have that problem for
>>>> decades.
>>>
>>>
>>>
>>> I guess we could live through the same decades, and more, if we didnt
>>> have
>>> that 64 limit.
>>
>>
>> I don't think we should be designing a "solution" for a problem that
>> we don't actually have.
>
>
> The 64 limit problem is there in the inherent design.
>
> One easy way to observe it is to connect to numerous operators and be
> surprised to only obtain a 64 and be unable to further extend one's Ethernet
> network.
>
> Other ways that may be more difficult to need and observe is with smaller
> subnets (4-max node).

Sounds like you need a problem statement draft, since subtending a /64
network is not necessarily trivial (even if you can do autoconf for
something like a /80), i.e. you have routing issues to solve as well.

From albert.e.manfredi@boeing.com  Thu Oct 31 14:14:23 2013
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CC6B21E80CE for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 14:14:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6O9s7JNGQ6MN for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 14:14:16 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (stl-mbsout-01.boeing.com [130.76.96.169]) by ietfa.amsl.com (Postfix) with ESMTP id D423521E80FF for <ipv6@ietf.org>; Thu, 31 Oct 2013 14:14:15 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9VLEE1j020908 for <ipv6@ietf.org>; Thu, 31 Oct 2013 16:14:15 -0500
Received: from XCH-PHX-106.sw.nos.boeing.com (xch-phx-106.sw.nos.boeing.com [137.136.238.9]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9VLEDx7020872 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Thu, 31 Oct 2013 16:14:14 -0500
Received: from XCH-PHX-503.sw.nos.boeing.com ([169.254.6.120]) by XCH-PHX-106.sw.nos.boeing.com ([169.254.3.217]) with mapi id 14.03.0158.001; Thu, 31 Oct 2013 14:14:14 -0700
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Erik Kline <ek@google.com>
Subject: RE: Why /64
Thread-Topic: Why /64
Thread-Index: AQHO1evCP1peZUHD+EaY3A+mPyO0EZoOw+iAgAD/+wD//4t9kA==
Date: Thu, 31 Oct 2013 21:14:13 +0000
Message-ID: <021E64FECA7E5A4699562F4E667164810B4AFB99@XCH-PHX-503.sw.nos.boeing.com>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org> <526E43E8.3080601@gmail.com> <526E91A3.8000807@alvarezp.ods.org> <526F888E.20609@gmail.com> <52702A06.2040102@gmail.com> <021E64FECA7E5A4699562F4E667164810B4AF4FE@XCH-PHX-503.sw.nos.boeing.com> <CAKD1Yr23LUD-tj0hErFvQo0dHFaJk4BqLc-zVtcFxJ7_+jmwuQ@mail.gmail.com> <52717006.5000806@gmail.com> <CAAedzxro3Y_DwScfk9KE_uGP-XAxsTQ0TKgi0X8PL7dRwbTYJQ@mail.gmail.com> <5271EFCF.6000101@gmail.com> <CAAedzxo3UpF57DEEWfT7M2evX8nPrevXqTENKif0z5ANR1eLZA@mail.gmail.com>
In-Reply-To: <CAAedzxo3UpF57DEEWfT7M2evX8nPrevXqTENKif0z5ANR1eLZA@mail.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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 31 Oct 2013 21:14:23 -0000

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of E=
rik
> Kline

> Sounds like you need a problem statement draft, since subtending a /64
> network is not necessarily trivial (even if you can do autoconf for
> something like a /80), i.e. you have routing issues to solve as well.

What routing issues? I'm curious.

If a residence, or an automobile, is assigned a /64, presumably any routing=
 from the WAN will be aggregated to that home or vehicle already. Then insi=
de, your gateway takes care of the rest, no?

I think any prediction that 64-bit prefixes are the most we could ever want=
 "for decades to come" is only as good as the assumptions made to reach tha=
t predictions. These assumptions are notoriously poor.

Bert


From ek@google.com  Thu Oct 31 14:20:05 2013
Return-Path: <ek@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E3B011E8153 for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 14:20:05 -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=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ufg6AvlC6Tnc for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 14:20:04 -0700 (PDT)
Received: from mail-qa0-x230.google.com (mail-qa0-x230.google.com [IPv6:2607:f8b0:400d:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id B74E111E80E9 for <ipv6@ietf.org>; Thu, 31 Oct 2013 14:20:03 -0700 (PDT)
Received: by mail-qa0-f48.google.com with SMTP id k4so188499qaq.7 for <ipv6@ietf.org>; Thu, 31 Oct 2013 14:20: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=I8psTq4MCq3XUUzr1n1T2s844q7mYrOWxIn2UmCU2dg=; b=Kq91Yfyg/g+FBZf3iQXD5xAfBdtwTqe3z0XK6i6OJLjYaPqWmEBislZ+jKN0GO0I0I v2PvsajXSSMxqaYS93fxUoaJqlv6HCcWTBvI3n+0Z1LcBWrLSO8ETOYqmpAdzQnRrXOf cj+jqzQqipUt92hbhRtdgRK7mnwS2NqTN5g+u0i9Vh6S6GLwfPcisVx8n1c2NKVps5Yi OsEcRfmf88+/E6x0CrWaTpqVU/sUUL0QHdHlzY2FEEOMxEQnlVciNhaIf3y4/KxCJbGA SleiSL5BP5w2wFlDhq/FkqfDl8IfRx5VjQgMPoBdU0rMx41YuAslBOuo2hMz7v27KLdk 7RTg==
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=I8psTq4MCq3XUUzr1n1T2s844q7mYrOWxIn2UmCU2dg=; b=GGkcLs3jJcu2EAWOtEeTB1YWLVp84Xg9AG07IrljIyZlTW0PNNTfEWFr89V0gMTCK2 GxUfRxcwIHbK+ys4fhkpnCX85nQJdHg8W9Q7J27WTc2qjtxcZhct1pId6bwPil2ADtPY r4YC7ltEbHOM6g+5G6zSeBzwqL1eV4bnweidWBQSXqvmtwAgoGtkc1iu/KLe+SkjXWA5 dzHgOSVjFvQ2FT2ZJOb5iQCEQbLoDUqzsELKARIONSBj3V/ET7yQBVr/5tr1h22Tdn/8 6m7stHG5VChGAUE4n30mueSFBPfO3kpa5snOlYNf3qRKoC5gNFqyrZr/dEdCDV7aQQE1 k/uA==
X-Gm-Message-State: ALoCoQmERHqUVYBxp0+ZlxCB7GxuRmt+ONm20hZiVSzkv/UbkDBRVriRHGRo64BgqKI2Cb5X7b2tqpFLpuuzLOhj5J9f3COc6T9JOHeFz8ijYCXSKafYvrvUhCJwpTO1Pa/1vfCvMb1mP/zFPoQjm/mAYoFC4p7SMhVPrrgQ6j6WK/5URhp06FJQSs7+iELnApnWauF+NfKP
X-Received: by 10.224.54.129 with SMTP id q1mr7985038qag.19.1383254403086; Thu, 31 Oct 2013 14:20:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.36.198 with HTTP; Thu, 31 Oct 2013 14:19:42 -0700 (PDT)
In-Reply-To: <021E64FECA7E5A4699562F4E667164810B4AFB99@XCH-PHX-503.sw.nos.boeing.com>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org> <526E43E8.3080601@gmail.com> <526E91A3.8000807@alvarezp.ods.org> <526F888E.20609@gmail.com> <52702A06.2040102@gmail.com> <021E64FECA7E5A4699562F4E667164810B4AF4FE@XCH-PHX-503.sw.nos.boeing.com> <CAKD1Yr23LUD-tj0hErFvQo0dHFaJk4BqLc-zVtcFxJ7_+jmwuQ@mail.gmail.com> <52717006.5000806@gmail.com> <CAAedzxro3Y_DwScfk9KE_uGP-XAxsTQ0TKgi0X8PL7dRwbTYJQ@mail.gmail.com> <5271EFCF.6000101@gmail.com> <CAAedzxo3UpF57DEEWfT7M2evX8nPrevXqTENKif0z5ANR1eLZA@mail.gmail.com> <021E64FECA7E5A4699562F4E667164810B4AFB99@XCH-PHX-503.sw.nos.boeing.com>
From: Erik Kline <ek@google.com>
Date: Thu, 31 Oct 2013 14:19:42 -0700
Message-ID: <CAAedzxpq1Hn-5vAG6xkmC_qh-N=aFA+ZaLtAYz=CA=ijmra8_w@mail.gmail.com>
Subject: Re: Why /64
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Content-Type: text/plain; charset=UTF-8
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 31 Oct 2013 21:20:05 -0000

> If a residence, or an automobile, is assigned a /64, presumably any routing from the WAN will be aggregated to that home or vehicle already. Then inside, your gateway takes care of the rest, no?

No gateway currently does this, i.e. it will not "just work" today.

Furthermore, I would argue that no home gateway currently expects that
it should do this, since it hasn't been documented as a requirement.

That's the kind of stuff to which I was referring.

From albert.e.manfredi@boeing.com  Thu Oct 31 14:24:22 2013
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1122E11E8256 for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 14:24:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08E+1vFNE12v for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 14:24:15 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) by ietfa.amsl.com (Postfix) with ESMTP id A170111E8110 for <ipv6@ietf.org>; Thu, 31 Oct 2013 14:24:13 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9VLOD1D012994 for <ipv6@ietf.org>; Thu, 31 Oct 2013 14:24:13 -0700
Received: from XCH-PHX-501.sw.nos.boeing.com (xch-phx-501.sw.nos.boeing.com [137.136.239.53]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9VLOC7V012989 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Thu, 31 Oct 2013 14:24:12 -0700
Received: from XCH-PHX-503.sw.nos.boeing.com ([169.254.6.120]) by XCH-PHX-501.sw.nos.boeing.com ([169.254.8.198]) with mapi id 14.03.0158.001; Thu, 31 Oct 2013 14:24:12 -0700
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Erik Kline <ek@google.com>
Subject: RE: Why /64
Thread-Topic: Why /64
Thread-Index: AQHO1evCP1peZUHD+EaY3A+mPyO0EZoOw+iAgAD/+wD//4t9kIAAd/UA//+K4OA=
Date: Thu, 31 Oct 2013 21:24:12 +0000
Message-ID: <021E64FECA7E5A4699562F4E667164810B4AFBC7@XCH-PHX-503.sw.nos.boeing.com>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org> <526E43E8.3080601@gmail.com> <526E91A3.8000807@alvarezp.ods.org> <526F888E.20609@gmail.com> <52702A06.2040102@gmail.com> <021E64FECA7E5A4699562F4E667164810B4AF4FE@XCH-PHX-503.sw.nos.boeing.com> <CAKD1Yr23LUD-tj0hErFvQo0dHFaJk4BqLc-zVtcFxJ7_+jmwuQ@mail.gmail.com> <52717006.5000806@gmail.com> <CAAedzxro3Y_DwScfk9KE_uGP-XAxsTQ0TKgi0X8PL7dRwbTYJQ@mail.gmail.com> <5271EFCF.6000101@gmail.com> <CAAedzxo3UpF57DEEWfT7M2evX8nPrevXqTENKif0z5ANR1eLZA@mail.gmail.com> <021E64FECA7E5A4699562F4E667164810B4AFB99@XCH-PHX-503.sw.nos.boeing.com> <CAAedzxpq1Hn-5vAG6xkmC_qh-N=aFA+ZaLtAYz=CA=ijmra8_w@mail.gmail.com>
In-Reply-To: <CAAedzxpq1Hn-5vAG6xkmC_qh-N=aFA+ZaLtAYz=CA=ijmra8_w@mail.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
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 31 Oct 2013 21:24:22 -0000

PiBGcm9tOiBFcmlrIEtsaW5lIFttYWlsdG86ZWtAZ29vZ2xlLmNvbV0NCj4gU2VudDogVGh1cnNk
YXksIE9jdG9iZXIgMzEsIDIwMTMgNToyMCBQTQ0KPiBUbzogTWFuZnJlZGksIEFsYmVydCBFDQo+
IENjOiBJRVRGIElQdjYgTWFpbGluZyBMaXN0DQo+IFN1YmplY3Q6IFJlOiBXaHkgLzY0DQo+IA0K
PiA+IElmIGEgcmVzaWRlbmNlLCBvciBhbiBhdXRvbW9iaWxlLCBpcyBhc3NpZ25lZCBhIC82NCwg
cHJlc3VtYWJseSBhbnkgcm91dGluZw0KPiBmcm9tIHRoZSBXQU4gd2lsbCBiZSBhZ2dyZWdhdGVk
IHRvIHRoYXQgaG9tZSBvciB2ZWhpY2xlIGFscmVhZHkuIFRoZW4gaW5zaWRlLA0KPiB5b3VyIGdh
dGV3YXkgdGFrZXMgY2FyZSBvZiB0aGUgcmVzdCwgbm8/DQo+IA0KPiBObyBnYXRld2F5IGN1cnJl
bnRseSBkb2VzIHRoaXMsIGkuZS4gaXQgd2lsbCBub3QgImp1c3Qgd29yayIgdG9kYXkuDQo+IA0K
PiBGdXJ0aGVybW9yZSwgSSB3b3VsZCBhcmd1ZSB0aGF0IG5vIGhvbWUgZ2F0ZXdheSBjdXJyZW50
bHkgZXhwZWN0cyB0aGF0DQo+IGl0IHNob3VsZCBkbyB0aGlzLCBzaW5jZSBpdCBoYXNuJ3QgYmVl
biBkb2N1bWVudGVkIGFzIGEgcmVxdWlyZW1lbnQuDQo+IA0KPiBUaGF0J3MgdGhlIGtpbmQgb2Yg
c3R1ZmYgdG8gd2hpY2ggSSB3YXMgcmVmZXJyaW5nLg0KDQpVbmRlcnN0b29kLiBBbmQgSSBmaW5k
IHRoaXMgdHJvdWJsaW5nIGFuZCB1bm5lY2Vzc2FyeS4gVGhhdCdzIG15IHBvaW50LiBXZSBoYXZl
IHRoaXMgaHVnZSAxMjgtYml0IGFkZHJlc3Mgc3BhY2UsIGFuZCB3ZSBhcmUgcHV0dGluZyBvdXJz
ZWx2ZXMgaW4gYSBwb3NpdGlvbiB3aGVyZSB3ZSBhY3R1YWxseSBvbmx5IGhhdmUgbWF5YmUgNDgg
b3IgYXQgbW9zdCA1NiBiaXRzIG9mICJkaXN0cmlidXRpb24gcG90ZW50aWFsLCIgbWVhbmluZyAi
dG8gZGlmZmVyZW50IHNpdGVzLiIgV2hlcmUgSVB2NCB3aXRoIENJRFIgaGFzIGVzc2VudGlhbGx5
IDMyLiBIb3cgY29tZSB0aGlzIGlzbid0IHRyb3VibGluZz8NCg0KQmVydA0KDQo=

From brian.e.carpenter@gmail.com  Thu Oct 31 14:50:17 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6535611E814C for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 14:50:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.527
X-Spam-Level: 
X-Spam-Status: No, score=-102.527 tagged_above=-999 required=5 tests=[AWL=0.072, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sJyHN3PAu+bL for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 14:50:16 -0700 (PDT)
Received: from mail-pd0-x22f.google.com (mail-pd0-x22f.google.com [IPv6:2607:f8b0:400e:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id D5BF421F9E36 for <ipv6@ietf.org>; Thu, 31 Oct 2013 14:50:13 -0700 (PDT)
Received: by mail-pd0-f175.google.com with SMTP id g10so2968540pdj.34 for <ipv6@ietf.org>; Thu, 31 Oct 2013 14:50:13 -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=9MAbL3W0CcKtNnvvXoqQJ02dgCOy4ReNiTg2DgFptzQ=; b=nSNog5lbvToqKMdp4oyQ0bMyNn5ZMkjPmT4HZyq5F8ae7pEH3IMm4e0j4TsdRlIJjI Ow2j9cfqCGhbo51a28NNJl7yOSLAicwDdMCVZVtGe2MqI/jFPfINW2xwPsZfo0EO1uhD YsjJ4BGVrDRvs8uplIzcdS3L/Vcnp60M6i/63nAp4/uVvPs6WwdCac/XmdkJNMmOaqzw AKxBF/lpCSXs20lfJ/naNxnk/EEgTPHU4FuxcOM9AwMgk598KiCasHrnsrNM6YYXRw8s l+udI86fl1q9y/4XH4SPXJA5ooxZGr9vXozBGFoIrLpLDhQdmm+aSGtXDvG6vqfs7puE 9xow==
X-Received: by 10.66.119.136 with SMTP id ku8mr4131881pab.121.1383256213586; Thu, 31 Oct 2013 14:50:13 -0700 (PDT)
Received: from [192.168.178.20] (11.201.69.111.dynamic.snap.net.nz. [111.69.201.11]) by mx.google.com with ESMTPSA id xe9sm7969030pab.0.2013.10.31.14.50.11 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 31 Oct 2013 14:50:12 -0700 (PDT)
Message-ID: <5272D09C.8040909@gmail.com>
Date: Fri, 01 Nov 2013 10:50: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: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<526AC8AF.4060608@si6networks.com>	<8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com>	<CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com>	<526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org>	<526E43E8.3080601@gmail.com> <526E91A3.8000807@alvarezp.ods.org>	<526F888E.20609@gmail.com> <52702A06.2040102@gmail.com>	<021E64FECA7E5A4699562F4E667164810B4AF4FE@XCH-PHX-503.sw.nos.boeing.com>	<CAKD1Yr23LUD-tj0hErFvQo0dHFaJk4BqLc-zVtcFxJ7_+jmwuQ@mail.gmail.com>	<52717006.5000806@gmail.com>	<CAAedzxro3Y_DwScfk9KE_uGP-XAxsTQ0TKgi0X8PL7dRwbTYJQ@mail.gmail.com>	<5271EFCF.6000101@gmail.com>	<CAAedzxo3UpF57DEEWfT7M2evX8nPrevXqTENKif0z5ANR1eLZA@mail.gmail.com>	<021E64FECA7E5A4699562F4E667164810B4AFB99@XCH-PHX-503.sw.nos.boeing.com>	<CAAedzxpq1Hn-5vAG6xkmC_qh-N=aFA+ZaLtAYz=CA=ijmra8_w@mail.gmail.com> <021E64FECA7E5A4699562F4E667164810B4AFBC7@XCH-PHX-503.sw.nos.boeing.com>
In-Reply-To: <021E64FECA7E5A4699562F4E667164810B4AFBC7@XCH-PHX-503.sw.nos.boeing.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 31 Oct 2013 21:50:17 -0000

On 01/11/2013 10:24, Manfredi, Albert E wrote:
>> From: Erik Kline [mailto:ek@google.com]
>> Sent: Thursday, October 31, 2013 5:20 PM
>> To: Manfredi, Albert E
>> Cc: IETF IPv6 Mailing List
>> Subject: Re: Why /64
>>
>>> If a residence, or an automobile, is assigned a /64, presumably any routing
>> from the WAN will be aggregated to that home or vehicle already. Then inside,
>> your gateway takes care of the rest, no?
>>
>> No gateway currently does this, i.e. it will not "just work" today.
>>
>> Furthermore, I would argue that no home gateway currently expects that
>> it should do this, since it hasn't been documented as a requirement.
>>
>> That's the kind of stuff to which I was referring.
> 
> Understood. And I find this troubling and unnecessary. That's my point. We have this huge 128-bit address space, and we are putting ourselves in a position where we actually only have maybe 48 or at most 56 bits of "distribution potential," meaning "to different sites." Where IPv4 with CIDR has essentially 32. How come this isn't troubling?

Because there are trillions of /48s.

   Brian

From albert.e.manfredi@boeing.com  Thu Oct 31 15:06:17 2013
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3911021F9C99 for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 15:06:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d9MNIGfXO1qU for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 15:06:10 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) by ietfa.amsl.com (Postfix) with ESMTP id 6A49011E8178 for <ipv6@ietf.org>; Thu, 31 Oct 2013 15:06:02 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9VM61Uu004138 for <ipv6@ietf.org>; Thu, 31 Oct 2013 15:06:02 -0700
Received: from XCH-PHX-407.sw.nos.boeing.com (xch-phx-407.sw.nos.boeing.com [137.136.239.48]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9VM61Us004128 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Thu, 31 Oct 2013 15:06:01 -0700
Received: from XCH-PHX-503.sw.nos.boeing.com ([169.254.6.120]) by XCH-PHX-407.sw.nos.boeing.com ([169.254.3.233]) with mapi id 14.03.0158.001; Thu, 31 Oct 2013 15:06:01 -0700
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: Why /64
Thread-Topic: Why /64
Thread-Index: AQHO1evCP1peZUHD+EaY3A+mPyO0EZoOw+iAgAD/+wD//4t9kIAAd/UA//+K4OCAAH2vAP//jGqQ
Date: Thu, 31 Oct 2013 22:06:00 +0000
Message-ID: <021E64FECA7E5A4699562F4E667164810B4AFC01@XCH-PHX-503.sw.nos.boeing.com>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org> <526E43E8.3080601@gmail.com> <526E91A3.8000807@alvarezp.ods.org> <526F888E.20609@gmail.com> <52702A06.2040102@gmail.com> <021E64FECA7E5A4699562F4E667164810B4AF4FE@XCH-PHX-503.sw.nos.boeing.com> <CAKD1Yr23LUD-tj0hErFvQo0dHFaJk4BqLc-zVtcFxJ7_+jmwuQ@mail.gmail.com> <52717006.5000806@gmail.com> <CAAedzxro3Y_DwScfk9KE_uGP-XAxsTQ0TKgi0X8PL7dRwbTYJQ@mail.gmail.com> <5271EFCF.6000101@gmail.com> <CAAedzxo3UpF57DEEWfT7M2evX8nPrevXqTENKif0z5ANR1eLZA@mail.gmail.com> <021E64FECA7E5A4699562F4E667164810B4AFB99@XCH-PHX-503.sw.nos.boeing.com> <CAAedzxpq1Hn-5vAG6xkmC_qh-N=aFA+ZaLtAYz=CA=ijmra8_w@mail.gmail.com> <021E64FECA7E5A4699562F4E667164810B4AFBC7@XCH-PHX-503.sw.nos.boeing.com> <5272D09C.8040909@gmail.com>
In-Reply-To: <5272D09C.8040909@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
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 31 Oct 2013 22:06:17 -0000

PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBCcmlhbiBFIENhcnBlbnRlciBb
bWFpbHRvOmJyaWFuLmUuY2FycGVudGVyQGdtYWlsLmNvbV0NCg0KPiBCZWNhdXNlIHRoZXJlIGFy
ZSB0cmlsbGlvbnMgb2YgLzQ4cy4NCg0KQW5kIHdlIHRoaW5rIHRoYXQgaXMgd2F5IG1vcmUgdGhh
biBhZGVxdWF0ZSwgdG9kYXkuIFVudGlsIHRoZSBwYXJhZGlnbSBjaGFuZ2VzLCBhbmQgZXZlcnkg
dmVoaWNsZSwgZXZlcnkgc3RyZWV0LCBldmVyeSBidWlsZGluZywgZXZlcnkgcGVyc29uLCB3aWxs
IG5lZWQgaXRzIG93biBpbnRlcm5hbCBzdWJuZXQgc3RydWN0dXJlLiBGb3IgdGhpbmdzIGxpa2Ug
dmVoaWNsZS10by1pbmZyYXN0cnVjdHVyZSBjb21tcywgdmVoaWNsZS10by12ZWhpY2xlIGNvbW1z
LCBpbnRlcm5hbCB2ZWhpY2xlIGNvbnRyb2xzIGFuZCBkaWFnbm9zdGljcyAoc2VwYXJhdGVkIGlu
dG8gbXVsdGlwbGUgc3Vic3lzdGVtcyBvZiBjb3Vyc2UpLCB3ZWFyYWJsZSBtZWRpY2FsIHNlbnNv
cnMsIGFuZCB3aG8ga25vd3Mgd2hhdCBlbHNlLiBBbmQgc3BhY2UuDQoNCkknbSBqdXN0IHNheWlu
ZywgY2xhc3NmdWwgSVB2NCBhbHNvIHNlZW1lZCBsaWtlIHBsZW50eSBhdCBmaXJzdC4gSXQgd2Fz
IGEgbWVyZSBkZWNhZGUgYmVmb3JlIHdlIGtuZXcgZGlmZmVyZW50bHkuDQoNCkJlcnQNCg0K

From Fred.L.Templin@boeing.com  Thu Oct 31 15:26:31 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2CCC11E8243 for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 15:26:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.522
X-Spam-Level: 
X-Spam-Status: No, score=-6.522 tagged_above=-999 required=5 tests=[AWL=0.077,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D5C7nJXMexoq for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 15:26:19 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (stl-mbsout-01.boeing.com [130.76.96.169]) by ietfa.amsl.com (Postfix) with ESMTP id 8219D11E8182 for <ipv6@ietf.org>; Thu, 31 Oct 2013 15:26:19 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9VMQJZT003273 for <ipv6@ietf.org>; Thu, 31 Oct 2013 17:26:19 -0500
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9VMQIwf003248 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK) for <ipv6@ietf.org>; Thu, 31 Oct 2013 17:26:18 -0500
Received: from XCH-BLV-302.nw.nos.boeing.com (130.247.25.214) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Thu, 31 Oct 2013 15:26:18 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-BLV-302.nw.nos.boeing.com ([169.254.2.227]) with mapi id 14.03.0158.001; Thu, 31 Oct 2013 15:26:18 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: RE: Why /64
Thread-Topic: Why /64
Thread-Index: AQHO1oNBhA9VOxeEw02Oq+EmllMqyJoPYBSQ
Date: Thu, 31 Oct 2013 22:26:17 +0000
Message-ID: <2134F8430051B64F815C691A62D98318145077@XCH-BLV-504.nw.nos.boeing.com>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch>	<526D3706.5070409@alvarezp.ods.org> <526E43E8.3080601@gmail.com>	<526E91A3.8000807@alvarezp.ods.org> <526F888E.20609@gmail.com>	<52702A06.2040102@gmail.com> <021E64FECA7E5A4699562F4E667164810B4AF4FE@XCH-PHX-503.sw.nos.boeing.com> <CAKD1Yr23LUD-tj0hErFvQo0dHFaJk4BqLc-zVtcFxJ7_+jmwuQ@mail.gmail.com> <52717006.5000806@gmail.com> <CAAedzxro3Y_DwScfk9KE_uGP-XAxsTQ0TKgi0X8PL7dRwbTYJQ@mail.gmail.com> <5271EFCF.6000101@gmail.com> <CAAedzxo3UpF57DEEWfT7M2evX8nPrevXqTENKif0z5ANR1eLZA@mail.gmail.com> <021E64FECA7E5A4699562F4E667164810B4AFB99@XCH-PHX-503.sw.nos.boeing.com> <CAAedzxpq1Hn-5vAG6xkmC_qh-N=aFA+ZaLtAYz=CA=ijmra8_w@mail.gmail.com> <021E64FECA7E5A4699562F4E667164810B4AFBC7@XCH-PHX-503.sw.nos.boeing.com> <5272D09C.8040909@gmail.com>
In-Reply-To: <5272D09C.8040909@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 31 Oct 2013 22:26:32 -0000

Hi, I have a whacky idea on why /64 is already a good number.
Routers on a link are identified by their link-local address;
always beginning with fe80. But, the interface identifier bits
are essentially wasted by including the EUI-64 encoding of the
MAC address while the MAC address is already available in the
L2 header.

But, since we delegate routable IPv6 prefixes to routers, why
not include the IPv6 prefix in the router's link-local IPv6
address?

For example, suppose the prefix 2001:db8:foo:baa::/64 were
delegated to a router then the router could configure the
IPv6 link-local address "fe80::2001:db8:foo:baa". This then
provides a useful router ID to other nodes on the link so
that the prefixes reachable through the router can be
gleaned by looking at the 64-bit interface identifier.

It would then be a configuration option on a link-by-link
basis as to whether the link supports this new "IPv6 prefix
embedded link local address" format. Then, legacy links can
continue to use good old EUI-64-based link-locals and new
links can use this new format. Just a thought.

Fred
fred.l.templin@boeing.com


From osmankh@yahoo.com  Thu Oct 31 15:31:40 2013
Return-Path: <osmankh@yahoo.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EED1C11E8182 for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 15:31:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.212
X-Spam-Level: *
X-Spam-Status: No, score=1.212 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TQy1Uutlzymu for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 15:31:33 -0700 (PDT)
Received: from nm29-vm3.bullet.mail.ne1.yahoo.com (nm29-vm3.bullet.mail.ne1.yahoo.com [98.138.91.159]) by ietfa.amsl.com (Postfix) with ESMTP id 63A0E11E8244 for <ipv6@ietf.org>; Thu, 31 Oct 2013 15:31:33 -0700 (PDT)
Received: from [98.138.90.57] by nm29.bullet.mail.ne1.yahoo.com with NNFMP; 31 Oct 2013 22:31:32 -0000
Received: from [98.138.226.126] by tm10.bullet.mail.ne1.yahoo.com with NNFMP; 31 Oct 2013 22:31:32 -0000
Received: from [127.0.0.1] by smtp205.mail.ne1.yahoo.com with NNFMP; 31 Oct 2013 22:31:32 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1383258692; bh=NzE/rFppxSsdR1c36/tUaVP8i1AN1xPKGbuBraIQj+0=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:Subject:From:Content-Type:X-Mailer:Message-Id:Date:To:Content-Transfer-Encoding:Mime-Version; b=q9X/g2rklvg6xQSLAIabjE2yQSstS7XhqpW8Iosdtv+fdlkPEigAYoc343ANimABrSyp0C3KPOYUCXpxIFQUdYCaqUOBlgi5GgREnmXSC5MxNsIrKf5dSC7ZJiksgEGSbzp7KywC7mWdG9eYoboqMoy4NHzBeA3yGDMR3iiy2Zk=
X-Yahoo-Newman-Id: 641529.28153.bm@smtp205.mail.ne1.yahoo.com
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: Qwg2W3QVM1lfQX6eCaKUYvQq7IiEb9Zo3o3hFzlug._39ZM QOnSY1Ctb5lypAovgPA0Rg5D8rD9vqHpoYKSF0dx_kMsT6rFneoEM7IvO8Gg HQSz.2jDkNloeCNyH53UXhCmzsOMGScVyti27FCr9xeIUXsMNgVcp3lRtwLs dKkzjxK_ULE59DKbI9uZly7AEtGNHjnYb4.9dSwzTgnklhuixtEBsh6aHRFq 7IlzwMmdlmy6txzwIZ6dA5U3QEWSHxhNKVtCWAGwgdShED07s6JQNZwXo7cr yjsbhZmQKr1OFRwHHY9d2UqS2Yi5AcrQwiqrggAntumdDnRU._X_GZdMKI.Q 7aNoiRyPkt1Sz2G2xCqZcxutdHR_pARXHsa_EPD8o9EvlW2BDmJ.OrtOFEkz XKQj_LiApfTIqX_4Ju945p7bYa5._bykfJd7sjdIkue3ik_sguvW5MQAmBaC T.Xc9bmuaIaPHsd6A8L3Fd8.luzHnM_sKPktDgcYnVcMRLl5zBSlp0kDlfLd _KnrI.PkGX5m3H4EXYK6Ht3FC4Qu9UU1Ycu0JhGAJQaMohvFo
X-Yahoo-SMTP: RUL5CFuswBD02LFE5KfPCwZifSs-
X-Rocket-Received: from [10.170.157.82] (osmankh@101.170.15.144 with ) by smtp205.mail.ne1.yahoo.com with SMTP; 31 Oct 2013 15:31:32 -0700 PDT
Subject: RE: Why /64
From: Usman Latif <osmankh@yahoo.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-F767E726-C836-49EE-9C97-D6188A24FE5A
X-Mailer: iPhone Mail (10B329)
Message-Id: <ADE72492-94FB-4BDE-9341-10AA72BFC2DE@yahoo.com>
Date: Fri, 1 Nov 2013 09:31:29 +1100
To: "ipv6@ietf.org" <ipv6@ietf.org>
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 31 Oct 2013 22:31:40 -0000

--Apple-Mail-F767E726-C836-49EE-9C97-D6188A24FE5A
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Guys, I think we has this debate many times already
The only conclusion I could draw was that the current IPv6 addressing archit=
ecture (with network/host boundaries at /64 or allocations/assignments at /4=
8s) is to address the IP address exhaustion for the near future (say < 100 y=
ears?)and we only care about near future
What happens two to three hundred years from now - who cares ?? :)

Regards,
Usman
=20

Date: Thu, 31 Oct 2013 22:06:00 +0000
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: RE: Why /64
Message-ID:
   <021E64FECA7E5A4699562F4E667164810B4AFC01@XCH-PHX-503.sw.nos.boeing.com>
  =20
Content-Type: text/plain; charset=3D"utf-8"

> -----Original Message-----
> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]

> Because there are trillions of /48s.

And we think that is way more than adequate, today. Until the paradigm chang=
es, and every vehicle, every street, every building, every person, will need=
 its own internal subnet structure. For things like vehicle-to-infrastructur=
e comms, vehicle-to-vehicle comms, internal vehicle controls and diagnostics=
 (separated into multiple subsystems of course), wearable medical sensors, a=
nd who knows what else. And space.

I'm just saying, classful IPv4 also seemed like plenty at first. It was a me=
re decade before we knew differently.

Bert

--Apple-Mail-F767E726-C836-49EE-9C97-D6188A24FE5A
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto">Guys, I think we has this debate many times=
 already<div>The only conclusion I could draw was that the current IPv6 addr=
essing architecture (with network/host boundaries at /64 or allocations/assi=
gnments at /48s) is to address the IP address exhaustion for the near future=
 (say &lt; 100 years?)and we only care about near future</div><div>What happ=
ens two to three hundred years from now - who cares ?? :)</div><div><br></di=
v><div>Regards,</div><div>Usman</div><div>&nbsp;<br><div><br><span style=3D"=
-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">D=
ate: Thu, 31 Oct 2013 22:06:00 +0000<br>From: "Manfredi, Albert E" &lt;<a hr=
ef=3D"mailto:albert.e.manfredi@boeing.com" x-apple-data-detectors=3D"true" x=
-apple-data-detectors-type=3D"link" x-apple-data-detectors-result=3D"38">alb=
ert.e.manfredi@boeing.com</a>&gt;<br>To: Brian E Carpenter &lt;<a href=3D"ma=
ilto:brian.e.carpenter@gmail.com" x-apple-data-detectors=3D"true" x-apple-da=
ta-detectors-type=3D"link" x-apple-data-detectors-result=3D"39">brian.e.carp=
enter@gmail.com</a>&gt;<br>Cc: IETF IPv6 Mailing List &lt;<a href=3D"mailto:=
ipv6@ietf.org" x-apple-data-detectors=3D"true" x-apple-data-detectors-type=3D=
"link" x-apple-data-detectors-result=3D"40">ipv6@ietf.org</a>&gt;<br>Subject=
: RE: Why /64<br>Message-ID:<br>&nbsp; &nbsp;&lt;<a href=3D"mailto:021E64FEC=
A7E5A4699562F4E667164810B4AFC01@XCH-PHX-503.sw.nos.boeing.com" x-apple-data-=
detectors=3D"true" x-apple-data-detectors-type=3D"link" x-apple-data-detecto=
rs-result=3D"41">021E64FECA7E5A4699562F4E667164810B4AFC01@XCH-PHX-503.sw.nos=
.boeing.com</a>&gt;<br>&nbsp; &nbsp;<br>Content-Type: text/plain; charset=3D=
"utf-8"<br><br></span><blockquote type=3D"cite"><font color=3D"#000000"><spa=
n style=3D"-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 2=
55, 0);">-----Original Message-----<br></span></font></blockquote><blockquot=
e type=3D"cite"><font color=3D"#000000"><span style=3D"-webkit-text-size-adj=
ust: auto; background-color: rgba(255, 255, 255, 0);">From: Brian E Carpente=
r [<a href=3D"mailto:brian.e.carpenter@gmail.com" x-apple-data-detectors=3D"=
true" x-apple-data-detectors-type=3D"link" x-apple-data-detectors-result=3D"=
42">mailto:brian.e.carpenter@gmail.com</a>]</span></font></blockquote><span s=
tyle=3D"-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255=
, 0);"><br></span><blockquote type=3D"cite"><font color=3D"#000000"><span st=
yle=3D"-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255,=
 0);">Because there are trillions of /48s.</span></font></blockquote><span s=
tyle=3D"-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255=
, 0);"><br>And we think that is way more than adequate, today. Until the par=
adigm changes, and every vehicle, every street, every building, every person=
, will need its own internal subnet structure. For things like vehicle-to-in=
frastructure comms, vehicle-to-vehicle comms, internal vehicle controls and d=
iagnostics (separated into multiple subsystems of course), wearable medical s=
ensors, and who knows what else. And space.<br><br>I'm just saying, classful=
 IPv4 also seemed like plenty at first. It was a mere decade before we knew d=
ifferently.<br><br>Bert</span><br style=3D"-webkit-tap-highlight-color: rgba=
(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0=
.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); "><=
/div></div></body></html>=

--Apple-Mail-F767E726-C836-49EE-9C97-D6188A24FE5A--

From marka@isc.org  Thu Oct 31 15:36:24 2013
Return-Path: <marka@isc.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B8C311E81E2 for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 15:36:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.572
X-Spam-Level: 
X-Spam-Status: No, score=-6.572 tagged_above=-999 required=5 tests=[AWL=4.027,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JkVw5etfV0Rq for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 15:36:17 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) by ietfa.amsl.com (Postfix) with ESMTP id 3281111E8254 for <ipv6@ietf.org>; Thu, 31 Oct 2013 15:36:11 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.ams1.isc.org (Postfix) with ESMTP id DB5082383DA; Thu, 31 Oct 2013 22:35:55 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id D0FA0160482; Thu, 31 Oct 2013 22:41:17 +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 A08BB160459; Thu, 31 Oct 2013 22:41:17 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 7FA479651F2; Fri,  1 Nov 2013 09:35:52 +1100 (EST)
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
From: Mark Andrews <marka@isc.org>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org> <526E43E8.3080601@gmail.com> <526E91A3.8000807@alvarezp.ods.org> <526F888E.20609@gmail.com> <52702A06.2040102@gmail.com> <021E64FECA7E5A4699562F4E667164810B4AF4FE@XCH-PHX-503.sw.nos.boeing.com> <CAKD1Yr23LUD-tj0hErFvQo0dHFaJk4BqLc-zVtcFxJ7_+jmwuQ@mail.gmail.com> <52717006.5000806@gmail.com> <CAAedzxro3Y_DwScfk9KE_uGP-XAxsTQ0TKgi0X8PL7dRwbTYJQ@mail.gmail.com> <5271EFCF.6000101@gmail.com> <CAAedzxo3UpF57DEEWfT7M2evX8nPrevXqTENKif0z5ANR1eLZA@mail.gmail.com> <021E64FECA7E5A4699562F4E667164810B4AFB99@XCH-PHX-503.sw.nos.boeing.com> <CAAedzxpq1Hn-5vAG6xkmC_qh-N=aFA+ZaLtAYz=CA=ijmra8_w@mail.gmail.com> <021E64FECA7E5A4699562F4E667164810B4AFBC7@XCH-PHX-503.sw.nos.boeing.com> <5272D09C.8040909@ gmail.co m> <021E64FECA7E5A4699562F4E667164810B4AFC01@XCH-PHX-503.sw.nos.boeing.com>
Subject: Re: Why /64
In-reply-to: Your message of "Thu, 31 Oct 2013 22:06:00 -0000." <021E64FECA7E5A4699562F4E667164810B4AFC01@XCH-PHX-503.sw.nos.boeing.com>
Date: Fri, 01 Nov 2013 09:35:52 +1100
Message-Id: <20131031223552.7FA479651F2@rock.dv.isc.org>
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 31 Oct 2013 22:36:24 -0000

In message <021E64FECA7E5A4699562F4E667164810B4AFC01@XCH-PHX-503.sw.nos.boeing.com>, "Manfredi, Albert E" writes:
> > -----Original Message-----
> > From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
> 
> > Because there are trillions of /48s.
> 
> And we think that is way more than adequate, today. Until the paradigm changes, and every vehicle, every street, e
> very building, every person, will need its own internal subnet structure. For things like vehicle-to-infrastructur
> e comms, vehicle-to-vehicle comms, internal vehicle controls and diagnostics (separated into multiple subsystems o
> f course), wearable medical sensors, and who knows what else. And space.
> 
> I'm just saying, classful IPv4 also seemed like plenty at first. It was a mere decade before we knew differently.

No classful IPv4 was *known* to not scale from the very beginning.

There are 72057594037927936 /56's which are what most ISP are
planning to hand out to residential customers.

If you really want to be miserly you can request /64's on a needs
basis with PD which is what internal home routers will need to do
so the code to support this will exist if we ever need to got to
that level when talking to ISP's.

> Bert
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From marka@isc.org  Thu Oct 31 17:40:03 2013
Return-Path: <marka@isc.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84D5811E8277 for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 17:40:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.832
X-Spam-Level: 
X-Spam-Status: No, score=-6.832 tagged_above=-999 required=5 tests=[AWL=3.767,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q-8UkIgwdgcN for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 17:39:58 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) by ietfa.amsl.com (Postfix) with ESMTP id 12D0911E827B for <ipv6@ietf.org>; Thu, 31 Oct 2013 17:39:55 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.ams1.isc.org (Postfix) with ESMTP id 912E92383E0; Fri,  1 Nov 2013 00:39:33 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id E3A0C160470; Fri,  1 Nov 2013 00:44:25 +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 B2348160459; Fri,  1 Nov 2013 00:44:25 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id A95A1966953; Fri,  1 Nov 2013 11:39:00 +1100 (EST)
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
From: Mark Andrews <marka@isc.org>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org> <526E43E8.3080601@gmail.com> <526E91A3.8000807@alvarezp.ods.org> <526F888E.20609@gmail.com> <52702A06.2040102@gmail.com> <021E64FECA7E5A4699562F4E667164810B4AF4FE@XCH-PHX-503.sw.nos.boeing.com> <CAKD1Yr23LUD-tj0hErFvQo0dHFaJk4BqLc-zVtcFxJ7_+jmwuQ@mail.gmail.com> <52717006.5000806@gmail.com> <CAAedzxro3Y_DwScfk9KE_uGP-XAxsTQ0TKgi0X8PL7dRwbTYJQ@mail.gmail.com> <5271EFCF.6000101@gmail.com> <CAAedzxo3UpF57DEEWfT7M2evX8nPrev XqTENKif 0z5ANR1eLZA@mail.gmail.com> <021E64FECA7E5A4699562F4E667164810B4AFB99@XCH-PHX-503.sw.nos.boeing.com> <CAAedzxpq1Hn-5vAG6xkmC_qh-N=aFA+ZaLtAYz=CA=ijmra8_w@mail.gmail.com> <021E64FECA7E5A4699562F4E667164810B4AFBC7@XCH-PHX-503.sw.nos.boeing.com>
Subject: Re: Why /64
In-reply-to: Your message of "Thu, 31 Oct 2013 21:24:12 -0000." <021E64FECA7E5A4699562F4E667164810B4AFBC7@XCH-PHX-503.sw.nos.boeing.com>
Date: Fri, 01 Nov 2013 11:39:00 +1100
Message-Id: <20131101003900.A95A1966953@rock.dv.isc.org>
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Nov 2013 00:40:03 -0000

In message <021E64FECA7E5A4699562F4E667164810B4AFBC7@XCH-PHX-503.sw.nos.boeing.
com>, "Manfredi, Albert E" writes:
> > From: Erik Kline [mailto:ek@google.com]
> > Sent: Thursday, October 31, 2013 5:20 PM
> > To: Manfredi, Albert E
> > Cc: IETF IPv6 Mailing List
> > Subject: Re: Why /64
> > 
> > > If a residence, or an automobile, is assigned a /64, presumably any routi
> ng
> > from the WAN will be aggregated to that home or vehicle already. Then insid
> e,
> > your gateway takes care of the rest, no?
> > 
> > No gateway currently does this, i.e. it will not "just work" today.
> > 
> > Furthermore, I would argue that no home gateway currently expects that
> > it should do this, since it hasn't been documented as a requirement.
> > 
> > That's the kind of stuff to which I was referring.
> 
> Understood. And I find this troubling and unnecessary. That's my point. We ha
> ve this huge 128-bit address space, and we are putting ourselves in a positio
> n where we actually only have maybe 48 or at most 56 bits of "distribution po
> tential," meaning "to different sites." Where IPv4 with CIDR has essentially 
> 32. How come this isn't troubling?

Because at 20 billion people you have 3 million networks per person with /56's.

		(2^56)/(2*10^10) = 3602879

Mark

> Bert
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From albert.e.manfredi@boeing.com  Thu Oct 31 17:59:44 2013
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 029FE21E8141 for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 17:59:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pIWWOK8oTxqb for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 17:59:29 -0700 (PDT)
Received: from blv-mbsout-01.boeing.com (blv-mbsout-01.boeing.com [130.76.32.231]) by ietfa.amsl.com (Postfix) with ESMTP id B7CD821E813F for <ipv6@ietf.org>; Thu, 31 Oct 2013 17:59:25 -0700 (PDT)
Received: from blv-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id rA10xO3g009356 for <ipv6@ietf.org>; Thu, 31 Oct 2013 17:59:24 -0700
Received: from XCH-PHX-502.sw.nos.boeing.com (xch-phx-502.sw.nos.boeing.com [137.136.239.55]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id rA10xNZ7009352 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Thu, 31 Oct 2013 17:59:24 -0700
Received: from XCH-PHX-503.sw.nos.boeing.com ([169.254.6.120]) by XCH-PHX-502.sw.nos.boeing.com ([169.254.7.227]) with mapi id 14.03.0158.001; Thu, 31 Oct 2013 17:59:23 -0700
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Mark Andrews <marka@isc.org>
Subject: RE: Why /64
Thread-Topic: Why /64
Thread-Index: AQHO1evCP1peZUHD+EaY3A+mPyO0EZoOw+iAgAD/+wD//4t9kIAAd/UA//+K4OCAADe2nYAAANew
Date: Fri, 1 Nov 2013 00:59:22 +0000
Message-ID: <021E64FECA7E5A4699562F4E667164810B4AFCAF@XCH-PHX-503.sw.nos.boeing.com>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org> <526E43E8.3080601@gmail.com> <526E91A3.8000807@alvarezp.ods.org> <526F888E.20609@gmail.com> <52702A06.2040102@gmail.com> <021E64FECA7E5A4699562F4E667164810B4AF4FE@XCH-PHX-503.sw.nos.boeing.com> <CAKD1Yr23LUD-tj0hErFvQo0dHFaJk4BqLc-zVtcFxJ7_+jmwuQ@mail.gmail.com> <52717006.5000806@gmail.com> <CAAedzxro3Y_DwScfk9KE_uGP-XAxsTQ0TKgi0X8PL7dRwbTYJQ@mail.gmail.com> <5271EFCF.6000101@gmail.com> <CAAedzxo3UpF57DEEWfT7M2evX8nPre! vXqTENKif 0z5ANR1eLZA@mail.gmail.com> <021E64FECA7E5A4699562F4E667164810B4AFB99@XCH-PHX-503.sw.nos.boeing.com> <CAAedzxpq1Hn-5vAG6xkmC_qh-N=aFA+ZaLtAYz=CA=ijmra8_w@mail.gmail.com> <021E64FECA7E5A4699562F4E667164810B4AFBC7@XCH-PHX-503.sw.nos.boeing.com> <20131101003900.A95A1966953@rock.dv.isc.org>
In-Reply-To: <20131101003900.A95A1966953@rock.dv.isc.org>
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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Nov 2013 00:59:44 -0000

> -----Original Message-----
> From: Mark Andrews [mailto:marka@isc.org]


> Because at 20 billion people you have 3 million networks per person with
> /56's.
>=20
> 		(2^56)/(2*10^10) =3D 3602879

But this continues to miss the point. It used to be mainframes at organizat=
ions. Then it became PCs in homes and offices. Then it became PCs and cell =
phones and tablets and printers and scanners and ...

Now think of beacons at road edges, potholes, road signals, street lights, =
crosswalks, yield signs, lane merge, nature trail, bike path, shipping lane=
, buoys, and so on, in addition to what you might have now associated with =
people, homes, offices. It's not just associated with people anymore.

All of these need organizational networks. Not all of these networks need a=
nywhere close to 2^64 hosts apiece. Why would you need 2^64 IIDs for a subn=
et of neighborhood streetlights, for instance?

Bert


From jeroen@massar.ch  Thu Oct 31 18:00:01 2013
Return-Path: <jeroen@massar.ch>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FDD421E8142 for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 18:00:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[AWL=-0.650, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UVq07EbakkXB for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 18:00:00 -0700 (PDT)
Received: from icaras.de.unfix.org (icaras.de.unfix.org [IPv6:2a01:4f8:130:74c1:5054:ff:fec4:f7d4]) by ietfa.amsl.com (Postfix) with ESMTP id B077821E8140 for <ipv6@ietf.org>; Thu, 31 Oct 2013 17:59:59 -0700 (PDT)
Received: from kami.ch.unfix.org (84-73-144-213.dclient.hispeed.ch [84.73.144.213]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeroen) by icaras.de.unfix.org (Postfix) with ESMTPSA id 2AC64801C2A2; Fri,  1 Nov 2013 01:59:51 +0100 (CET)
Message-ID: <5272FD0D.9060705@massar.ch>
Date: Fri, 01 Nov 2013 01:59:57 +0100
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>,  "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com>	<CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com>	<526CDC59.4070204@massar.ch>	<526D3706.5070409@alvarezp.ods.org>	<526E43E8.3080601@gmail.com>	<526E91A3.8000807@alvarezp.ods.org>	<526F888E.20609@gmail.com>	<52702A06.2040102@gmail.com>	<021E64FECA7E5A4699562F4E667164810B4AF4FE@XCH-PHX-503.sw.nos.boeing.com>	<CAKD1Yr23LUD-tj0hErFvQo0dHFaJk4BqLc-zVtcFxJ7_+jmwuQ@mail.gmail.com>	<52717006.5000806@gmail.com>	<CAAedzxro3Y_DwScfk9KE_uGP-XAxsTQ0TKgi0X8PL7dRwbTYJQ@mail.gmail.com>	<5271EFCF.6000101@gmail.com>	<CAAedzxo3UpF57DEEWfT7M2evX8nPrevXqTENKif0z5ANR1eLZA@mail.gmail.com>	<021E64FECA7E5A4699562F4E667164810B4AFB99@XCH-PHX-503.sw.nos.boeing.com>	<CAAedzxpq1Hn-5vAG6xkmC_qh-N=aFA+ZaLtAYz=CA=ijmra8_w@mail.gmail.com>	<021E64FECA7E5A4699562F4E667164810B4AFBC7@XCH-PHX-503.sw.nos.boeing.com> <5272D09C.8040909@gmail.com>
In-Reply-To: <5272D09C.8040909@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Nov 2013 01:00:01 -0000

On 2013-10-31 22:50, Brian E Carpenter wrote:
> On 01/11/2013 10:24, Manfredi, Albert E wrote:
>>> From: Erik Kline [mailto:ek@google.com]
>>> Sent: Thursday, October 31, 2013 5:20 PM
>>> To: Manfredi, Albert E
>>> Cc: IETF IPv6 Mailing List
>>> Subject: Re: Why /64
>>>
>>>> If a residence, or an automobile, is assigned a /64, presumably any routing
>>> from the WAN will be aggregated to that home or vehicle already. Then inside,
>>> your gateway takes care of the rest, no?
>>>
>>> No gateway currently does this, i.e. it will not "just work" today.
>>>
>>> Furthermore, I would argue that no home gateway currently expects that
>>> it should do this, since it hasn't been documented as a requirement.
>>>
>>> That's the kind of stuff to which I was referring.
>>
>> Understood. And I find this troubling and unnecessary. That's my point. We have this huge 128-bit address space, and we are putting ourselves in a position where we actually only have maybe 48 or at most 56 bits of "distribution potential," meaning "to different sites." Where IPv4 with CIDR has essentially 32. How come this isn't troubling?
> 
> Because there are trillions of /48s.

And because every such site gets a /48 (or /56) and then can do whatever
they want with that. ;)

Greets,
 Jeroen



From otroan@employees.org  Thu Oct 31 18:04:49 2013
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C650F21E813E for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 18:04:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.513
X-Spam-Level: 
X-Spam-Status: No, score=-2.513 tagged_above=-999 required=5 tests=[AWL=0.086,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pa+7YMYINprw for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 18:04:43 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [198.137.202.19]) by ietfa.amsl.com (Postfix) with ESMTP id 50EB321E813A for <ipv6@ietf.org>; Thu, 31 Oct 2013 18:04:39 -0700 (PDT)
Received: from dhcp-10-61-111-247.cisco.com (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 4953A5F62; Thu, 31 Oct 2013 18:04:35 -0700 (PDT)
From: Ole Troan <otroan@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_392F1435-1777-4460-A017-0B8A959C5031"; protocol="application/pgp-signature"; micalg=pgp-sha512
Subject: Note taker and jabber scribe - Volunteers?
Date: Fri, 1 Nov 2013 02:04:24 +0100
Message-Id: <797FB816-ED20-4167-89C9-5DA5146BC83C@employees.org>
To: 6man WG <ipv6@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
X-Mailer: Apple Mail (2.1816)
Cc: Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Nov 2013 01:04:49 -0000

--Apple-Mail=_392F1435-1777-4460-A017-0B8A959C5031
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Hi,

We need note takers and jabber scribe for Monday's 6man meeting.
Please let Bob or me know.

Best regards,
Ole

--Apple-Mail=_392F1435-1777-4460-A017-0B8A959C5031
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

iQEcBAEBCgAGBQJScv4YAAoJEFuJXizso86gwaYIAMEzyD9hf88GLGh6hLLIskxK
yZmI2fY78AUGW8BgB0Zphqr89AsQ3FBqsrirFsVpZN6/Ef7Z9sgyX/Rj60aFozYT
EuLg5P5rveTYr5UXAlZMcXGN5syov2yhHH4qe6Go1DjbF1Epl+oe9Fe0P2UM4B3V
aSfeK24H43TfnZ1nOekQ0Ft9V01ciEkL5dbwL9RyCFTVPIsatxkyToaDjP7Ai8Nc
Bzc4QaY+AjiuchdgQqeZeb8HDrcQS4mXbaEIcDxamNGIOB8CxlhtlDfrayuddELG
sZvEIhisXGZvVVOxhnh2i0CllcICLrBvpNyQWlhAjothURD+k8VShsifMTT1djs=
=NBvw
-----END PGP SIGNATURE-----

--Apple-Mail=_392F1435-1777-4460-A017-0B8A959C5031--

From brian.e.carpenter@gmail.com  Thu Oct 31 18:48:17 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F77211E81AF for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 18:48:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.528
X-Spam-Level: 
X-Spam-Status: No, score=-102.528 tagged_above=-999 required=5 tests=[AWL=0.071, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CWl555WpAsHV for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 18:48:12 -0700 (PDT)
Received: from mail-pd0-x233.google.com (mail-pd0-x233.google.com [IPv6:2607:f8b0:400e:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 7385511E8291 for <ipv6@ietf.org>; Thu, 31 Oct 2013 18:48:12 -0700 (PDT)
Received: by mail-pd0-f179.google.com with SMTP id y10so3163488pdj.24 for <ipv6@ietf.org>; Thu, 31 Oct 2013 18:48:12 -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=pM21cgmK5TbrURQrm3oAUxSmS0WhngBbr2KHVCN242M=; b=UWU/A6loV7exmatIkq8zScdKpCrSUF0XEzDX9Q6XB8aji/bLPoJ901V9BbGjjIsEuM GJEpQ1TbtCxPjyF7iOYz4ea5KBImg0lV1bUyWvBqY2rVrEiIi84eosY0m8Ulul99+l8h blM+2MjkVe5jlbE0HTnQiiEQAjuQPcIOETvqpDRMCYSjfXiwJrra6DJKNEpD13Noh+VX pIJIwRKbo+gFG9fF3eOPzrE9nGKOkz+PZ5WmSED6C5GfvEaJh/WRhevBZgPZxyb0hXRl /Vwx5IOfrsNkEJxLkC+SDFOK7SDYybBpxi4hWJPLAKgDhhW48NORgqY5IBMs+0zB25xc dw0Q==
X-Received: by 10.67.1.203 with SMTP id bi11mr640294pad.137.1383270492166; Thu, 31 Oct 2013 18:48:12 -0700 (PDT)
Received: from [192.168.178.20] (11.201.69.111.dynamic.snap.net.nz. [111.69.201.11]) by mx.google.com with ESMTPSA id at4sm7163716pbc.30.2013.10.31.18.48.09 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 31 Oct 2013 18:48:11 -0700 (PDT)
Message-ID: <52730863.7080206@gmail.com>
Date: Fri, 01 Nov 2013 14:48: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: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com>	<CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com>	<526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org>	<526E43E8.3080601@gmail.com> <526E91A3.8000807@alvarezp.ods.org>	<526F888E.20609@gmail.com> <52702A06.2040102@gmail.com>	<021E64FECA7E5A4699562F4E667164810B4AF4FE@XCH-PHX-503.sw.nos.boeing.com>	<CAKD1Yr23LUD-tj0hErFvQo0dHFaJk4BqLc-zVtcFxJ7_+jmwuQ@mail.gmail.com>	<52717006.5000806@gmail.com>	<CAAedzxro3Y_DwScfk9KE_uGP-XAxsTQ0TKgi0X8PL7dRwbTYJQ@mail.gmail.com>	<5271EFCF.6000101@gmail.com> <CAAedzxo3UpF57DEEWfT7M2evX8nPre!	vXqTENKif 0z5ANR1eLZA@mail.gmail.com>	<021E64FECA7E5A4699562F4E667164810B4AFB99@XCH-PHX-503.sw.nos.boeing.com>	<CAAedzxpq1Hn-5vAG6xkmC_qh-N=aFA+ZaLtAYz=CA=ijmra8_w@mail.gmail.com>	<021E64FECA7E5A4699562F4E667164810B4AFBC7@XCH-PHX-503.sw.nos.boeing.com>	<20131101003900.A95A1966953@rock.dv.isc.org> <021E64FECA7E5A4699562F4E667164810B4AFCAF@XCH-PHX-503.sw.nos.boeing. com>
In-Reply-To: <021E64FECA7E5A4699562F4E667164810B4AFCAF@XCH-PHX-503.sw.nos.boeing.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>, Mark Andrews <marka@isc.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Nov 2013 01:48:17 -0000

>  Why would you need 2^64 IIDs for a subnet of neighborhood streetlights, for instance?

Unguessable IIDs, for example, unless you would like Stuxnet 3.0
flashing your city's streetlights like a Christmas tree,
or PRISM 2.0 keeping a close eye on you.

Structured IIDs, if you'd like to put semantics into them
(which I think is a terrible idea, but maybe opinions will be
different in 2113).

ILNP.

If we'd just wanted to do IPv4.1, we'd have picked 64 bits
instead of 128. As it is, we have 64 bits for CIDR and 64 bits
for new ideas.

   Brian

From marka@isc.org  Thu Oct 31 18:56:46 2013
Return-Path: <marka@isc.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9338711E829C for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 18:56:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.949
X-Spam-Level: 
X-Spam-Status: No, score=-2.949 tagged_above=-999 required=5 tests=[AWL=-0.350, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GkLN1QxKJBcx for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 18:56:36 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 39AEB11E8291 for <ipv6@ietf.org>; Thu, 31 Oct 2013 18:56:30 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.ams1.isc.org (Postfix) with ESMTP id A0A412383D7; Fri,  1 Nov 2013 01:56:14 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 3D692160470; Fri,  1 Nov 2013 02:01:37 +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 C8595160459; Fri,  1 Nov 2013 02:01:36 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 3A12D9670E5; Fri,  1 Nov 2013 12:56:11 +1100 (EST)
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
From: Mark Andrews <marka@isc.org>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org> <526E43E8.3080601@gmail.com> <526E91A3.8000807@alvarezp.ods.org> <526F888E.20609@gmail.com> <52702A06.2040102@gmail.com> <021E64FECA7E5A4699562F4E667164810B4AF4FE@XCH-PHX-503.sw.nos.boeing.com> <CAKD1Yr23LUD-tj0hErFvQo0dHFaJk4BqLc-zVtcFxJ7_+jmwuQ@mail.gmail.com> <52717006.5000806@gmail.com> <CAAedzxro3Y_DwScfk9KE_uGP-XAxsTQ0TKgi0X8PL7dRwbTYJQ@mail.gmail.com> <5271EFCF.6000101@gmail.com> <CAAedzxo3UpF57DEEWfT7M2evX8nPre! vXqTENK if 0z5ANR1eLZA@mail.gmail.com> <021E64FECA7E5A4699562F4E667164810B4AFB99@XCH-PHX-503.sw.nos.boeing.com> <CAAedzxpq1Hn-5vAG6xkmC_qh-N=aFA+ZaLtAYz=CA=ijmra8_w@mail.gmail.com> <021E64FECA7E5A4699562F4E667164810B4AFBC7@XCH-PHX-503.sw.nos.boeing.com> <20131101003900.A95A1966953@rock.dv.isc.org> <021E64FECA7E5A4699562F4E667164810B4AFCAF@XCH-PHX-503.sw.nos.boeing.com>
Subject: Re: Why /64
In-reply-to: Your message of "Fri, 01 Nov 2013 00:59:22 -0000." <021E64FECA7E5A4699562F4E667164810B4AFCAF@XCH-PHX-503.sw.nos.boeing.com>
Date: Fri, 01 Nov 2013 12:56:11 +1100
Message-Id: <20131101015611.3A12D9670E5@rock.dv.isc.org>
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Nov 2013 01:56:46 -0000

In message <021E64FECA7E5A4699562F4E667164810B4AFCAF@XCH-PHX-503.sw.nos.boeing.
com>, "Manfredi, Albert E" writes:
> > -----Original Message-----
> > From: Mark Andrews [mailto:marka@isc.org]
> 
> 
> > Because at 20 billion people you have 3 million networks per person with
> > /56's.
> > 
> > 		(2^56)/(2*10^10) = 3602879
> 
> But this continues to miss the point. It used to be mainframes at organizatio
> ns. Then it became PCs in homes and offices. Then it became PCs and cell phon
> es and tablets and printers and scanners and ...

And you think it will get to 3 million things per person that need
their own network?  Printers, scanners and phones attach to networks.
Phone that are tethering can request /64's as required from upstream.

> Now think of beacons at road edges, potholes, road signals, street lights, cr
> osswalks, yield signs, lane merge, nature trail, bike path, shipping lane, bu
> oys, and so on, in addition to what you might have now associated with people
> , homes, offices. It's not just associated with people anymore.

Again how many of them will need their own network rather than
connect to a network?   The network count is orders of magnitude
smaller than the device count.

> All of these need organizational networks. Not all of these networks need any
> where close to 2^64 hosts apiece. Why would you need 2^64 IIDs for a subnet o
> f neighborhood streetlights, for instance?

You don't and and the electricity company / council can configure
the network to use something smaller if they want.  Nobody is
forcing people to use large networks if they don't want to.  They
can always stand up a stateful DHCP server and send approptiate RA's.

They could cover a whole country out of a /64 if they wanted to.

You however seem to want everyone to stand up a stateful DHCP server
when there is no need to do so.  Device configuration doesn't need
a stateful DHCP server.  Only address assignment needs a stateful
DHCP server.

Mark

> Bert
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From kauer@biplane.com.au  Thu Oct 31 19:53:21 2013
Return-Path: <kauer@biplane.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70E3E11E82AE for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 19:53:21 -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=-2.599, J_CHICKENPOX_21=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j0dVrk-SLHLx for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 19:53:20 -0700 (PDT)
Received: from ipmail07.adl2.internode.on.net (ipmail07.adl2.internode.on.net [IPv6:2001:44b8:8060:ff02:300:1:2:7]) by ietfa.amsl.com (Postfix) with ESMTP id DFA6911E82B3 for <ipv6@ietf.org>; Thu, 31 Oct 2013 19:53:17 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqIBALcWc1KWZX+7/2dsb2JhbAANTIM/Tr9kgTmDGQEBAQSBCQsYLlcZiA+pKJNIjhCBRoQuA4kIkDGLJohugVQ
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; 01 Nov 2013 13:23:08 +1030
Message-ID: <1383274385.3347.35.camel@karl>
Subject: RE: Why /64
From: Karl Auer <kauer@biplane.com.au>
To: ipv6@ietf.org
Date: Fri, 01 Nov 2013 13:53:05 +1100
In-Reply-To: <021E64FECA7E5A4699562F4E667164810B4AFCAF@XCH-PHX-503.sw.nos.boeing.com>
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org> <526E43E8.3080601@gmail.com> <526E91A3.8000807@alvarezp.ods.org> <526F888E.20609@gmail.com> <52702A06.2040102@gmail.com> <021E64FECA7E5A4699562F4E667164810B4AF4FE@XCH-PHX-503.sw.nos.boeing.com> <CAKD1Yr23LUD-tj0hErFvQo0dHFaJk4BqLc-zVtcFxJ7_+jmwuQ@mail.gmail.com> <52717006.5000806@gmail.com> <CAAedzxro3Y_DwScfk9KE_uGP-XAxsTQ0TKgi0X8PL7dRwbTYJQ@mail.gmail.com> <5271EFCF.6000101@gmail.com> <CAAedzxo3UpF57DEEWfT7M2evX8nPre! vXqTENKif 0z5ANR1eLZA@mail.gmail.com> <021E64FECA7E5A4699562F4E667164810B4AFB99@XCH-PHX-503.sw.nos.boeing.com> <CAAedzxpq1Hn-5vAG6xkmC_qh-N=aFA+ZaLtAYz=CA=ijmra8_w@mail.gmail.com> <021E64FECA7E5A4699562F4E667164810B4AFBC7@XCH-PHX-503.sw.nos.boeing.com> <20131101003900.A95A1966953@rock.dv.isc.org> <021E64FECA7E5A4699562F4E667164810B4AFCAF@XCH-PHX-503.sw.nos.boeing.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-Mailer: Evolution 3.2.3-0ubuntu6 
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Nov 2013 02:53:21 -0000

On Fri, 2013-11-01 at 00:59 +0000, Manfredi, Albert E wrote:
> Why would you need 2^64 IIDs for a subnet of neighborhood streetlights, for instance?

I don't know. But the key thing is that I don't need to. When I ask for
a glass of water at a restaurant, I do not know or care how many water
molecules I'm buying, either. It doesn't *matter*.

No-one ever seems to consider the *advantages* of the "/64 everywhere"
approach. They decry the "waste" without looking at what that "waste" is
buying:

- everything is the same. No more calculating (leaf) subnet sizes, no
more stealing from Peter to pay Paul, no more getting it wrong - every
subnet is a /64.

- there are *always* enough addresses in *any* subnet for you add one
more device. Or even a hundred. You might run into other limits, but the
addressing will never get in your way.

- adding a subnet is easy - just take the next /64. No estimates,
calculations, consideration or judgement needed.

- your router configs are easier to understand

- your documentation is easier to write and easier to read.

What this boils down to is greater ease of network management and
administration. And that translates directly into money saved - saved in
design time, saved in implementation speed, save in ease of
troubleshooting, saved in ease of documentation, saved in fewer errors
made, saved in less downtime.

Spread across the whole Internet, all those advantages multiply. 

All those benefits come just from having a standard subnet size big
enough to accommodate any likely number of hosts. The fact that it is
big enough to handle completely *unlikely* numbers of hosts is a bonus -
because you can forget about that problem too. Your subnets will
*always* be big enough.

We could argue about where the line should be; how big the standard
network should be. For any remotely reasonable number of devices in
a /64, you are using zero percent of the 18 billion billion available
addresses. 2, 200, 20,000 or even a million, it's still zero percent to
a dozen decimal places. Let's sliiiiiide the pointer to the right,
making the standard network smaller and smaller and smaller until that
percentage is something bigger - say 1%. What have you achieved? If you
still have a big enough subnet to accommodate any likely number of
hosts, you are "wasting" addresses. Anything smaller, and you've brought
that old IPv4 concern back into the world - "have I got enough
addresses?" And if you make it so that you can have any sized leaf
subnet, you lose all the lovely advantages of "one size fits all".

My definition of "waste" is spending a limited resource for no benefit.
The above benefits seem to me to have real value, so I don't consider
"/64 everywhere" to be a "waste".

Regards, K.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer@biplane.com.au)
http://www.biplane.com.au/kauer
http://twitter.com/kauer389

GPG fingerprint: B862 FB15 FE96 4961 BC62 1A40 6239 1208 9865 5F9A
Old fingerprint: AE1D 4868 6420 AD9A A698 5251 1699 7B78 4EEE 6017


From v6ops@globis.net  Thu Oct 31 23:57:12 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7724A11E810D for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 23:57:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RzX-n8Z3mQAT for <ipv6@ietfa.amsl.com>; Thu, 31 Oct 2013 23:57:11 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id B035721F9FEE for <ipv6@ietf.org>; Thu, 31 Oct 2013 23:57:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 9DDAE87005F; Fri,  1 Nov 2013 07:57:08 +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 WUUsGmBBpXOk; Fri,  1 Nov 2013 07:57:08 +0100 (CET)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 5296F870056; Fri,  1 Nov 2013 07:57:08 +0100 (CET)
Message-ID: <527350C2.50502@globis.net>
Date: Fri, 01 Nov 2013 07:57:06 +0100
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Mark Andrews <marka@isc.org>
Subject: Re: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org> <526E43E8.3080601@gmail.com> <526E91A3.8000807@alvarezp.ods.org> <526F888E.20609@gmail.com> <52702A06.2040102@gmail.com> <021E64FECA7E5A4699562F4E667164810B4AF4FE@XCH-PHX-503.sw.nos.boeing.com> <CAKD1Yr23LUD-tj0hErFvQo0dHFaJk4BqLc-zVtcFxJ7_+jmwuQ@mail.gmail.com> <52717006.5000806@gmail.com> <CAAedzxro3Y_DwScfk9KE_uGP-XAxsTQ0TKgi0X8PL7dRwbTYJQ@mail.gmail.com> <5271EFCF.6000101@gmail.com> <CAAedzxo3UpF57DEEWfT7M2evX8nPrevXqTENKif0z5ANR1eLZA@mail.gmail.com> <021E64FECA7E5A4699562F4E667164810B4AFB99@XCH-PHX-503.sw.nos.boeing.com> <CAAedzxpq1Hn-5vAG6xkmC_qh-N=aFA+ZaLtAYz=CA=ijmra8_w@mail.gmail.com> <021E64FECA7E5A4699562F4E667164810B4AFBC7@XCH-PHX-503.sw.nos.boeing.com> <5272D09C.8040909@ gmail.co m> <021E64FECA7E5A4699562F4E667164810B4AFC01@XCH-PHX-503.sw.nos.boeing.com> <20131031223552.7FA479651F2@rock.dv.isc.org>
In-Reply-To: <20131031223552.7FA479651F2@rock.dv.isc.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Nov 2013 06:57:12 -0000

Mark Andrews wrote:
> In message <021E64FECA7E5A4699562F4E667164810B4AFC01@XCH-PHX-503.sw.nos.boeing.com>, "Manfredi, Albert E" writes:
>>> -----Original Message-----
>>> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
>>> Because there are trillions of /48s.
>> And we think that is way more than adequate, today. Until the paradigm changes, and every vehicle, every street, e
>> very building, every person, will need its own internal subnet structure. For things like vehicle-to-infrastructur
>> e comms, vehicle-to-vehicle comms, internal vehicle controls and diagnostics (separated into multiple subsystems o
>> f course), wearable medical sensors, and who knows what else. And space.
>>
>> I'm just saying, classful IPv4 also seemed like plenty at first. It was a mere decade before we knew differently.
>
> No classful IPv4 was *known* to not scale from the very beginning.
>
> There are 72057594037927936 /56's which are what most ISP are
> planning to hand out to residential customers.
>
> If you really want to be miserly you can request /64's on a needs
> basis with PD which is what internal home routers will need to do
> so the code to support this will exist if we ever need to got to
> that level when talking to ISP's.

Which would be fine if:

1) All allocations continue to be made by ISPs on a network provider =>
consumer model

2) We had a routing mechanism that could handle such a flat addressing
structure

3) We had a delegation mechanism for naming and addressing that could
easily cope with delegation on bit boundaries.

but we don't.

1. More and more we see demand from manufacturers e.g. car engine
management, and even subcomponent management.

2. We have a very limited number of bits of hierachy for route
aggregation, and thus effectively a limit to the hierarchical depth of
network topology/ organisations.

3. Once you factor in recommendations to delegate on nibble boundaries
(e.g. for DNS) you have somewhere around /32 to /64 = ±9 nibble
boundaries => 9 levels of depth of hierarchy + a flat LAN.

IMHO I think what we effectively have is an administrative
(non-technical) limit to scaling today, largely limited by an ability to
register, delegate, and aggregate; rather than the huge number of
possible addresses or prefixes. 'twas ever thus. In IPv4 it was
effectively +/- 3 levels (octet boundaries + a flat LAN).

regards.

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

-- 
Regards,
RayH

