From ipv6-bounces@ietf.org Sat Feb 03 09:20:32 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HDLdz-0000Jh-Jp; Sat, 03 Feb 2007 09:13:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HD2PZ-0006hS-Tv
	for ipv6@ietf.org; Fri, 02 Feb 2007 12:41:21 -0500
Received: from pilot.jhuapl.edu ([128.244.198.200] helo=jhuapl.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HD2PW-0006d5-LY
	for ipv6@ietf.org; Fri, 02 Feb 2007 12:41:21 -0500
Received: from ([128.244.206.105])
	by pilot.jhuapl.edu with ESMTP  id 5502123.20306766;
	Fri, 02 Feb 2007 12:40:54 -0500
Message-ID: <45C377A5.3020008@innovationslab.net>
Date: Fri, 02 Feb 2007 12:40:53 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207)
MIME-Version: 1.0
To: ipv6@ietf.org
X-Enigmail-Version: 0.94.1.2
Content-Type: multipart/mixed; boundary="------------050305040301040902080007"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
X-Mailman-Approved-At: Sat, 03 Feb 2007 09:13:29 -0500
Subject: WG Request: Adopt draft-haberman-ipv6-ra-flags-option-00.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

This is a multi-part message in MIME format.
--------------050305040301040902080007
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

All,
     This is a formal call to request IPv6 WG feedback on adopting the
below draft.  The premise of the draft is to expand the flags field that
is quickly running out of bits.

     Please provide your preference (positive or negative) on having
this document become an IPv6 WG document.  Comments on the contents are
most welcome as well.

Regards,
Brian


-------- Original Message --------
Subject: I-D ACTION:draft-haberman-ipv6-ra-flags-option-00.txt
Date: Tue, 01 Aug 2006 15:50:01 -0400
From: Internet-Drafts@ietf.org
Reply-To: internet-drafts@ietf.org
To: i-d-announce@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: IPv6 Router Advertisement Flags Option
	Author(s)	: B. Haberman, R. Hinden
	Filename	: draft-haberman-ipv6-ra-flags-option-00.txt
	Pages		: 7
	Date		: 2006-8-1
	
The IPv6 Neighbor Discovery's Router Advertisement message contains
an 8-bit field reserved for single-bit flags.  Several protocols have
reserved flags in this field and others are preparing to reserve a
sufficient number of flags to exhaust the field.  This document
defines an option to the Router Advertisement message that expands
the available number of flag bits available.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-haberman-ipv6-ra-flags-option-00.txt


--------------050305040301040902080007
Content-Type: text/plain; x-mac-type="0"; x-mac-creator="0";
	name="draft-haberman-ipv6-ra-flags-option-00.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
	filename="draft-haberman-ipv6-ra-flags-option-00.txt"

Content-Type: text/plain
Content-ID: <2006-8-1141246.I-D@ietf.org>



--------------050305040301040902080007
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--------------050305040301040902080007--




From ipv6-bounces@ietf.org Sat Feb 03 19:05:22 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HDUnk-0005wq-Rf; Sat, 03 Feb 2007 19:00:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HDUnj-0005k7-93
	for ipv6@ietf.org; Sat, 03 Feb 2007 19:00:11 -0500
Received: from [2002:425c:4242:0:210:5aff:fe86:1f54] (helo=cyteen.hactrn.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HDUnh-0007sp-Sa
	for ipv6@ietf.org; Sat, 03 Feb 2007 19:00:11 -0500
Received: from cyteen.hactrn.net (localhost [127.0.0.1])
	by cyteen.hactrn.net (Postfix) with ESMTP id D8F7A28429
	for <ipv6@ietf.org>; Sun,  4 Feb 2007 00:00:02 +0000 (UTC)
To: ipv6@ietf.org
From: Rob Austein <sra+ipng@hactrn.net>
Date: Sun, 04 Feb 2007 00:00:02 +0000
Message-Id: <20070204000002.D8F7A28429@cyteen.hactrn.net>
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Subject: Weekly posting summary for ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 28.57% |    2 | 52.66% |    29408 | zhimin.feng@orange-ftgroup.com
 14.29% |    1 | 13.72% |     7664 | alexandru.petrescu@motorola.com
 14.29% |    1 |  9.47% |     5290 | brian@innovationslab.net
 14.29% |    1 |  8.67% |     4843 | pars.mutaf@int-evry.fr
 14.29% |    1 |  8.36% |     4668 | mailman-owner@ietf.org
 14.29% |    1 |  7.11% |     3969 | sra+ipng@hactrn.net
--------+------+--------+----------+------------------------
100.00% |    7 |100.00% |    55842 | Total

Grunchweather Associates provides this automatic summary on an at-whim
basis at the request of the IPv6 WG chairs.  Your mileage may vary.
We decline responsibilities, all shapes, all sizes, all colors.
If this script produces broken output, you get to keep both pieces.

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



From ipv6-bounces@ietf.org Sun Feb 04 00:42:53 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HDa3r-0001zl-A0; Sun, 04 Feb 2007 00:37:11 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HDa3p-0001zc-7n
	for ipv6@ietf.org; Sun, 04 Feb 2007 00:37:09 -0500
Received: from ug-out-1314.google.com ([66.249.92.175])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HDa3n-0001YQ-T9
	for ipv6@ietf.org; Sun, 04 Feb 2007 00:37:09 -0500
Received: by ug-out-1314.google.com with SMTP id 72so987599ugd
	for <ipv6@ietf.org>; Sat, 03 Feb 2007 21:37:07 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=ADpZBCVX7BQ5nCwhMF+X0Iesbql+NIRjjzgtAhG9/BhBMQKsZqu8Fhzwab9J6HoO+vF9tmy/6N5NeXPXjTgYpmJeZ7y9Bd7ZRph1aKML7EcAeibJug/BCA8jLPBw/r0Dk0LacyJ39AnX5FeV+KuyxrhFXARl0aU1xQ3BnCGvIps=
Received: by 10.67.21.11 with SMTP id y11mr886008ugi.1170567426743;
	Sat, 03 Feb 2007 21:37:06 -0800 (PST)
Received: by 10.66.239.6 with HTTP; Sat, 3 Feb 2007 21:37:06 -0800 (PST)
Message-ID: <90cbfd80702032137p3e10df4ie1d0042586168cd9@mail.gmail.com>
Date: Sun, 4 Feb 2007 03:37:06 -0200
From: "Guilherme Sperb Machado" <gsmachado@gmail.com>
To: "Brian Haberman" <brian@innovationslab.net>
In-Reply-To: <45C377A5.3020008@innovationslab.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <45C377A5.3020008@innovationslab.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: ipv6@ietf.org
Subject: Re: WG Request: Adopt draft-haberman-ipv6-ra-flags-option-00.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

The draft link is not working. How can I read the proposed draft?

Thanks in advance,
Guilherme Sperb Machado

On 2/2/07, Brian Haberman <brian@innovationslab.net> wrote:
> All,
>      This is a formal call to request IPv6 WG feedback on adopting the
> below draft.  The premise of the draft is to expand the flags field that
> is quickly running out of bits.
>
>      Please provide your preference (positive or negative) on having
> this document become an IPv6 WG document.  Comments on the contents are
> most welcome as well.
>
> Regards,
> Brian
>
>
> -------- Original Message --------
> Subject: I-D ACTION:draft-haberman-ipv6-ra-flags-option-00.txt
> Date: Tue, 01 Aug 2006 15:50:01 -0400
> From: Internet-Drafts@ietf.org
> Reply-To: internet-drafts@ietf.org
> To: i-d-announce@ietf.org
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
>         Title           : IPv6 Router Advertisement Flags Option
>         Author(s)       : B. Haberman, R. Hinden
>         Filename        : draft-haberman-ipv6-ra-flags-option-00.txt
>         Pages           : 7
>         Date            : 2006-8-1
>
> The IPv6 Neighbor Discovery's Router Advertisement message contains
> an 8-bit field reserved for single-bit flags.  Several protocols have
> reserved flags in this field and others are preparing to reserve a
> sufficient number of flags to exhaust the field.  This document
> defines an option to the Router Advertisement message that expands
> the available number of flag bits available.
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-haberman-ipv6-ra-flags-option-00.txt
>
>
>
> Content-Type: text/plain
> Content-ID: <2006-8-1141246.I-D@ietf.org>
>
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>
>

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



From ipv6-bounces@ietf.org Sun Feb 04 05:56:30 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HDexi-0003x9-SU; Sun, 04 Feb 2007 05:51:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HDexg-0003vL-KW
	for ipv6@ietf.org; Sun, 04 Feb 2007 05:51:08 -0500
Received: from mtagate3.uk.ibm.com ([195.212.29.136])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HDeui-0002jf-No
	for ipv6@ietf.org; Sun, 04 Feb 2007 05:48:06 -0500
Received: from d12nrmr1607.megacenter.de.ibm.com
	(d12nrmr1607.megacenter.de.ibm.com [9.149.167.49])
	by mtagate3.uk.ibm.com (8.13.8/8.13.8) with ESMTP id l14Am3Ss099202
	for <ipv6@ietf.org>; Sun, 4 Feb 2007 10:48:03 GMT
Received: from d12av03.megacenter.de.ibm.com (d12av03.megacenter.de.ibm.com
	[9.149.165.213])
	by d12nrmr1607.megacenter.de.ibm.com (8.13.8/8.13.8/NCO v8.2) with
	ESMTP id l14Am3qL1839334
	for <ipv6@ietf.org>; Sun, 4 Feb 2007 11:48:03 +0100
Received: from d12av03.megacenter.de.ibm.com (loopback [127.0.0.1])
	by d12av03.megacenter.de.ibm.com (8.12.11.20060308/8.13.3) with ESMTP
	id l14Am3Zn018411 for <ipv6@ietf.org>; Sun, 4 Feb 2007 11:48:03 +0100
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232])
	by d12av03.megacenter.de.ibm.com (8.12.11.20060308/8.12.11) with ESMTP
	id l14Am26Y018408; Sun, 4 Feb 2007 11:48:02 +0100
Received: from [9.146.218.5] (sig-9-146-218-5.de.ibm.com [9.146.218.5])
	by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id LAA353684; 
	Sun, 4 Feb 2007 11:48:01 +0100
Message-ID: <45C5B9E3.9070902@zurich.ibm.com>
Date: Sun, 04 Feb 2007 11:48:03 +0100
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Guilherme Sperb Machado <gsmachado@gmail.com>
References: <45C377A5.3020008@innovationslab.net>
	<90cbfd80702032137p3e10df4ie1d0042586168cd9@mail.gmail.com>
In-Reply-To: <90cbfd80702032137p3e10df4ie1d0042586168cd9@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: Brian Haberman <brian@innovationslab.net>, ipv6@ietf.org
Subject: Re: WG Request: Adopt draft-haberman-ipv6-ra-flags-option-00.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

It's expired. Try
http://tools.ietf.org/id/draft-haberman-ipv6-ra-flags-option-00.txt

     Brian

On 2007-02-04 06:37, Guilherme Sperb Machado wrote:
> The draft link is not working. How can I read the proposed draft?
> 
> Thanks in advance,
> Guilherme Sperb Machado
> 
> On 2/2/07, Brian Haberman <brian@innovationslab.net> wrote:
>> All,
>>      This is a formal call to request IPv6 WG feedback on adopting the
>> below draft.  The premise of the draft is to expand the flags field that
>> is quickly running out of bits.
>>
>>      Please provide your preference (positive or negative) on having
>> this document become an IPv6 WG document.  Comments on the contents are
>> most welcome as well.
>>
>> Regards,
>> Brian
>>
>>
>> -------- Original Message --------
>> Subject: I-D ACTION:draft-haberman-ipv6-ra-flags-option-00.txt
>> Date: Tue, 01 Aug 2006 15:50:01 -0400
>> From: Internet-Drafts@ietf.org
>> Reply-To: internet-drafts@ietf.org
>> To: i-d-announce@ietf.org
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>>
>>
>>         Title           : IPv6 Router Advertisement Flags Option
>>         Author(s)       : B. Haberman, R. Hinden
>>         Filename        : draft-haberman-ipv6-ra-flags-option-00.txt
>>         Pages           : 7
>>         Date            : 2006-8-1
>>
>> The IPv6 Neighbor Discovery's Router Advertisement message contains
>> an 8-bit field reserved for single-bit flags.  Several protocols have
>> reserved flags in this field and others are preparing to reserve a
>> sufficient number of flags to exhaust the field.  This document
>> defines an option to the Router Advertisement message that expands
>> the available number of flag bits available.
>>
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-haberman-ipv6-ra-flags-option-00.txt 
>>
>>
>>
>>
>> Content-Type: text/plain
>> Content-ID: <2006-8-1141246.I-D@ietf.org>
>>
>>
>>
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
>>
>>
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 

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



From ipv6-bounces@ietf.org Mon Feb 05 09:02:13 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HE4Kn-0008BN-9I; Mon, 05 Feb 2007 08:56:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HE4Kl-0008BG-Sq
	for ipv6@ietf.org; Mon, 05 Feb 2007 08:56:39 -0500
Received: from mail128.messagelabs.com ([216.82.250.131])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HE4Kj-0000bP-Dc
	for ipv6@ietf.org; Mon, 05 Feb 2007 08:56:39 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@motorola.com
X-Msg-Ref: server-13.tower-128.messagelabs.com!1170683796!14630346!1
X-StarScan-Version: 5.5.10.7.1; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 31915 invoked from network); 5 Feb 2007 13:56:36 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-13.tower-128.messagelabs.com with SMTP;
	5 Feb 2007 13:56:36 -0000
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l15DuaaB029712;
	Mon, 5 Feb 2007 06:56:36 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id l15DuXIg017664;
	Mon, 5 Feb 2007 07:56:34 -0600 (CST)
Message-ID: <45C73790.1010207@motorola.com>
Date: Mon, 05 Feb 2007 14:56:32 +0100
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Brian Haberman <brian@innovationslab.net>
References: <45C377A5.3020008@innovationslab.net>
In-Reply-To: <45C377A5.3020008@innovationslab.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: ipv6@ietf.org
Subject: Re: WG Request: Adopt draft-haberman-ipv6-ra-flags-option-00.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Brian Haberman wrote:
> All, This is a formal call to request IPv6 WG feedback on adopting
> the below draft.  The premise of the draft is to expand the flags
> field that is quickly running out of bits.
> 
> Please provide your preference (positive or negative) on having this
> document become an IPv6 WG document.  Comments on the contents are 
> most welcome as well.

Hi, I'm new to the document/activity.  It doesn't seem to be listed in
the Charter but seems to me to be the only proposal of RA option
extensions in this way.

I'm positive about having such document as a WG item.

The flags in RA are indeed almost running out, only one left.  The
published literature is full with extensions in RA.

The encoding in the draft looks meaningful with respect to RFC2461
(length is 1 as 2461 expects).

Nits: there may be some need to identify better how this RA option must
precede all the other RA options (SLLAO, MTU, PI).  For example, draft
says the option must be the first option after the 'base NDP' header,
but there's no such thing as 'base NDP' header - one is tempted to think
'base IPv6 header'?  I think it's meant 'RA message header'?  Another
example, 2461 says an non-understood option should be dropped and
discontinue message processing, and 'RA options' will be non-understood
for a while by implementations, so maybe just request drop the option
but continue processing.

Question: if one needs to use this new option between two routers to let
each other know that the prefixes advertised _could_ be installed in the
routing table - would this option encoding be appropriate?

Alex

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



From ipv6-bounces@ietf.org Mon Feb 05 10:07:29 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HE5NL-0001WI-AC; Mon, 05 Feb 2007 10:03:23 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HE5NJ-0001WD-UB
	for ipv6@ietf.org; Mon, 05 Feb 2007 10:03:21 -0500
Received: from imr1.ericy.com ([198.24.6.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HE5ND-0004Zx-G8
	for ipv6@ietf.org; Mon, 05 Feb 2007 10:03:21 -0500
Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se
	[138.85.77.50])
	by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id l15F32u0027023;
	Mon, 5 Feb 2007 09:03:02 -0600
Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.51]) by
	eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Feb 2007 09:03:02 -0600
Received: from [142.133.10.140] ([142.133.10.140]) by
	eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Feb 2007 09:03:01 -0600
Message-ID: <45C74892.9060807@ericsson.com>
Date: Mon, 05 Feb 2007 10:09:06 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 1.5 (X11/20060313)
MIME-Version: 1.0
To: Brian Haberman <brian@innovationslab.net>
References: <45C377A5.3020008@innovationslab.net>
In-Reply-To: <45C377A5.3020008@innovationslab.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 05 Feb 2007 15:03:01.0750 (UTC)
	FILETIME=[BAFC3160:01C74936]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: ipv6@ietf.org
Subject: Re: WG Request: Adopt draft-haberman-ipv6-ra-flags-option-00.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Brian,
   I fully support this draft becoming a WG document.

Cheers
Suresh

Brian Haberman wrote:
> All,
>      This is a formal call to request IPv6 WG feedback on adopting the
> below draft.  The premise of the draft is to expand the flags field that
> is quickly running out of bits.
> 
>      Please provide your preference (positive or negative) on having
> this document become an IPv6 WG document.  Comments on the contents are
> most welcome as well.
> 
> Regards,
> Brian
> 
> 
> -------- Original Message --------
> Subject: I-D ACTION:draft-haberman-ipv6-ra-flags-option-00.txt
> Date: Tue, 01 Aug 2006 15:50:01 -0400
> From: Internet-Drafts@ietf.org
> Reply-To: internet-drafts@ietf.org
> To: i-d-announce@ietf.org
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> 
> 
> 	Title		: IPv6 Router Advertisement Flags Option
> 	Author(s)	: B. Haberman, R. Hinden
> 	Filename	: draft-haberman-ipv6-ra-flags-option-00.txt
> 	Pages		: 7
> 	Date		: 2006-8-1
> 	
> The IPv6 Neighbor Discovery's Router Advertisement message contains
> an 8-bit field reserved for single-bit flags.  Several protocols have
> reserved flags in this field and others are preparing to reserve a
> sufficient number of flags to exhaust the field.  This document
> defines an option to the Router Advertisement message that expands
> the available number of flag bits available.
> 
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-haberman-ipv6-ra-flags-option-00.txt
> 
> 
> 
> ------------------------------------------------------------------------
> 
> Content-Type: text/plain
> Content-ID: <2006-8-1141246.I-D@ietf.org>
> 
> 
> 
> ------------------------------------------------------------------------
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


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



From ipv6-bounces@ietf.org Mon Feb 05 12:17:26 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HE7QO-0007hJ-9b; Mon, 05 Feb 2007 12:14:40 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HE7QM-0007gO-Mu
	for ipv6@ietf.org; Mon, 05 Feb 2007 12:14:38 -0500
Received: from paoakoavas10.cable.comcast.com ([208.17.35.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HE7QL-0003z5-7e
	for ipv6@ietf.org; Mon, 05 Feb 2007 12:14:38 -0500
Received: from ([10.195.246.152])
	by paoakoavas10.cable.comcast.com with ESMTP  id KP-TDCH3.29985115;
	Mon, 05 Feb 2007 12:14:15 -0500
Received: from PACDCEXCMB05.cable.comcast.com ([24.40.15.116]) by
	NJMDCEXCRLY01.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.1830); Mon, 5 Feb 2007 12:14:15 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 5 Feb 2007 12:14:10 -0500
Message-ID: <EF2F0EC839870F43A6637360BC12ABD4010A6CAA@PACDCEXCMB05.cable.comcast.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WG Request: Adopt draft-haberman-ipv6-ra-flags-option-00.txt
Thread-Index: AcdHnmtBJljvTww9StyIlHvD+3KqgwBqZlvA
From: "Durand, Alain" <Alain_Durand@cable.comcast.com>
To: "Brian Haberman" <brian@innovationslab.net>,
	<ipv6@ietf.org>
X-OriginalArrivalTime: 05 Feb 2007 17:14:15.0776 (UTC)
	FILETIME=[10453600:01C74949]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: 
Subject: RE: WG Request: Adopt draft-haberman-ipv6-ra-flags-option-00.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

I would like to ask what is the transition plan for "legacy" IPv6 hosts
that do not implement this extension before I could consider this draft
a viable approach.

We have a number of bits that are currently defined that may be
questionable,
(the best example: O & M), so I would like to see some more
justification
why more bits are needed for the general RA case and maybe some clean-up
of the current bits before we embark into defining a new space for
potentially questionable new cases.

So, at this point, I do not support this draft.

  - Alain.

=20

> -----Original Message-----
> From: Brian Haberman [mailto:brian@innovationslab.net]=20
> Sent: Friday, February 02, 2007 12:41 PM
> To: ipv6@ietf.org
> Subject: WG Request: Adopt draft-haberman-ipv6-ra-flags-option-00.txt
>=20
> All,
>      This is a formal call to request IPv6 WG feedback on=20
> adopting the below draft.  The premise of the draft is to=20
> expand the flags field that is quickly running out of bits.
>=20
>      Please provide your preference (positive or negative) on=20
> having this document become an IPv6 WG document.  Comments on=20
> the contents are most welcome as well.
>=20
> Regards,
> Brian
>=20
>=20
> -------- Original Message --------
> Subject: I-D ACTION:draft-haberman-ipv6-ra-flags-option-00.txt
> Date: Tue, 01 Aug 2006 15:50:01 -0400
> From: Internet-Drafts@ietf.org
> Reply-To: internet-drafts@ietf.org
> To: i-d-announce@ietf.org
>=20
> A New Internet-Draft is available from the on-line=20
> Internet-Drafts directories.
>=20
>=20
> 	Title		: IPv6 Router Advertisement Flags Option
> 	Author(s)	: B. Haberman, R. Hinden
> 	Filename	: draft-haberman-ipv6-ra-flags-option-00.txt
> 	Pages		: 7
> 	Date		: 2006-8-1
> =09
> The IPv6 Neighbor Discovery's Router Advertisement message=20
> contains an 8-bit field reserved for single-bit flags. =20
> Several protocols have reserved flags in this field and=20
> others are preparing to reserve a sufficient number of flags=20
> to exhaust the field.  This document defines an option to the=20
> Router Advertisement message that expands the available=20
> number of flag bits available.
>=20
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-haberman-ipv6-ra-fla
> gs-option-00.txt
>=20
>=20

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



From ipv6-bounces@ietf.org Mon Feb 05 13:38:02 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HE8il-0002IA-R2; Mon, 05 Feb 2007 13:37:43 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HE8ij-0002Hp-Sy
	for ipv6@ietf.org; Mon, 05 Feb 2007 13:37:41 -0500
Received: from vms042pub.verizon.net ([206.46.252.42])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HE8ii-0003V4-Fc
	for ipv6@ietf.org; Mon, 05 Feb 2007 13:37:41 -0500
Received: from vms075.mailsrvcs.net ([192.168.1.2])
	by vms042.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01
	(built Apr
	3 2006)) with ESMTPA id <0JD000GM56EF3LL0@vms042.mailsrvcs.net> for
	ipv6@ietf.org; Mon, 05 Feb 2007 12:37:28 -0600 (CST)
Received: from 129.55.200.20 ([129.55.200.20])
	by vms075.mailsrvcs.net (Verizon Webmail) with HTTP; Mon,
	05 Feb 2007 12:37:27 -0600 (CST)
Date: Mon, 05 Feb 2007 12:37:27 -0600 (CST)
From: Tim Enos <timbeck04@verizon.net>
X-Originating-IP: [129.55.200.20]
To: "Durand, Alain" <Alain_Durand@cable.comcast.com>,
	Brian Haberman <brian@innovationslab.net>, ipv6@ietf.org
Message-id: <1856655.3180531170700647810.JavaMail.root@vms075.mailsrvcs.net>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7bit
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Cc: 
Subject: RE: WG Request: Adopt draft-haberman-ipv6-ra-flags-option-00.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Good afternoon all,

>From: "Durand, Alain" <Alain_Durand@cable.comcast.com>
>Date: 2007/02/05 Mon AM 11:14:10 CST
>To: Brian Haberman <brian@innovationslab.net>, ipv6@ietf.org
>Subject: RE: WG Request: Adopt draft-haberman-ipv6-ra-flags-option-00.txt

>I would like to ask what is the transition plan for "legacy" IPv6 hosts
>that do not implement this extension before I could consider this draft
>a viable approach.

This is a good question. FWIW, at the moment I would expect that the "legacy" IPv6 hosts would ignore the extension and continue processing the RA.

Another question seems to be what would happen to hosts which implement/rely upon flags that were un-defined as a result of the "clean-up" process mentioned elsewhere in this e-mail.

>
>We have a number of bits that are currently defined that may be
>questionable,
>(the best example: O & M), so I would like to see some more
>justification
>why more bits are needed for the general RA case and maybe some clean-up
>of the current bits before we embark into defining a new space for
>potentially questionable new cases.

I agree that some more justification (and potentially some subsequent "clean-up") of the already defined bits may be advisable prior to defining new space. 

>
>So, at this point, I do not support this draft.
>
>  - Alain.

Respectfully,

Tim Enos
Rom 8:28
>
> 
>
>> -----Original Message-----
>> From: Brian Haberman [mailto:brian@innovationslab.net] 
>> Sent: Friday, February 02, 2007 12:41 PM
>> To: ipv6@ietf.org
>> Subject: WG Request: Adopt draft-haberman-ipv6-ra-flags-option-00.txt
>> 
>> All,
>>      This is a formal call to request IPv6 WG feedback on 
>> adopting the below draft.  The premise of the draft is to 
>> expand the flags field that is quickly running out of bits.
>> 
>>      Please provide your preference (positive or negative) on 
>> having this document become an IPv6 WG document.  Comments on 
>> the contents are most welcome as well.
>> 
>> Regards,
>> Brian
>> 
>> 
>> -------- Original Message --------
>> Subject: I-D ACTION:draft-haberman-ipv6-ra-flags-option-00.txt
>> Date: Tue, 01 Aug 2006 15:50:01 -0400
>> From: Internet-Drafts@ietf.org
>> Reply-To: internet-drafts@ietf.org
>> To: i-d-announce@ietf.org
>> 
>> A New Internet-Draft is available from the on-line 
>> Internet-Drafts directories.
>> 
>> 
>> 	Title		: IPv6 Router Advertisement Flags Option
>> 	Author(s)	: B. Haberman, R. Hinden
>> 	Filename	: draft-haberman-ipv6-ra-flags-option-00.txt
>> 	Pages		: 7
>> 	Date		: 2006-8-1
>> 	
>> The IPv6 Neighbor Discovery's Router Advertisement message 
>> contains an 8-bit field reserved for single-bit flags.  
>> Several protocols have reserved flags in this field and 
>> others are preparing to reserve a sufficient number of flags 
>> to exhaust the field.  This document defines an option to the 
>> Router Advertisement message that expands the available 
>> number of flag bits available.
>> 
>> 
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-haberman-ipv6-ra-fla
>> gs-option-00.txt
>> 
>> 
>
>--------------------------------------------------------------------
>IETF IPv6 working group mailing list
>ipv6@ietf.org
>Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>--------------------------------------------------------------------


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



From ipv6-bounces@ietf.org Mon Feb 05 13:38:02 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HE8fp-0001Bb-KA; Mon, 05 Feb 2007 13:34:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HE8fo-0001BQ-Lz
	for ipv6@ietf.org; Mon, 05 Feb 2007 13:34:40 -0500
Received: from vms048pub.verizon.net ([206.46.252.48])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HE8fl-0002OX-8I
	for ipv6@ietf.org; Mon, 05 Feb 2007 13:34:40 -0500
Received: from vms075.mailsrvcs.net ([192.168.1.2])
	by vms048.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01
	(built Apr
	3 2006)) with ESMTPA id <0JD00027R691ANDA@vms048.mailsrvcs.net> for
	ipv6@ietf.org; Mon, 05 Feb 2007 12:34:14 -0600 (CST)
Received: from 129.55.200.20 ([129.55.200.20])
	by vms075.mailsrvcs.net (Verizon Webmail) with HTTP; Mon,
	05 Feb 2007 12:34:12 -0600 (CST)
Date: Mon, 05 Feb 2007 12:34:08 -0600 (CST)
From: Tim Enos <timbeck04@verizon.net>
X-Originating-IP: [129.55.200.20]
To: "Durand, Alain" <Alain_Durand@cable.comcast.com>,
	Brian Haberman <brian@innovationslab.net>, ipv6@ietf.org
Message-id: <6146247.3179941170700453426.JavaMail.root@vms075.mailsrvcs.net>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7bit
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Cc: 
Subject: RE: WG Request: Adopt draft-haberman-ipv6-ra-flags-option-00.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Good afternoon all,

>From: "Durand, Alain" <Alain_Durand@cable.comcast.com>
>Date: 2007/02/05 Mon AM 11:14:10 CST
>To: Brian Haberman <brian@innovationslab.net>, ipv6@ietf.org
>Subject: RE: WG Request: Adopt draft-haberman-ipv6-ra-flags-option-00.txt

>I would like to ask what is the transition plan for "legacy" IPv6 hosts
>that do not implement this extension before I could consider this draft
>a viable approach.

This is a good question. FWIW, at the moment I would expect that the "legacy" IPv6 hosts would ignore the extension and continue processing the RA.

Another question seems to be what would happen to hosts which implement/rely upon flags that were un-defined as a result of the "clean-up" process mentioned elsewhere in this e-mail.

>
>We have a number of bits that are currently defined that may be
>questionable,
>(the best example: O & M), so I would like to see some more
>justification
>why more bits are needed for the general RA case and maybe some clean-up
>of the current bits before we embark into defining a new space for
>potentially questionable new cases.

I agree that some more justification (and potentially some subsequent "clean-up") of the already defined bits may be advisable prior to defining new space. 

>
>So, at this point, I do not support this draft.
>
>  - Alain.

Best Regards,

Tim Enos
Rom 8:28
>
> 
>
>> -----Original Message-----
>> From: Brian Haberman [mailto:brian@innovationslab.net] 
>> Sent: Friday, February 02, 2007 12:41 PM
>> To: ipv6@ietf.org
>> Subject: WG Request: Adopt draft-haberman-ipv6-ra-flags-option-00.txt
>> 
>> All,
>>      This is a formal call to request IPv6 WG feedback on 
>> adopting the below draft.  The premise of the draft is to 
>> expand the flags field that is quickly running out of bits.
>> 
>>      Please provide your preference (positive or negative) on 
>> having this document become an IPv6 WG document.  Comments on 
>> the contents are most welcome as well.
>> 
>> Regards,
>> Brian
>> 
>> 
>> -------- Original Message --------
>> Subject: I-D ACTION:draft-haberman-ipv6-ra-flags-option-00.txt
>> Date: Tue, 01 Aug 2006 15:50:01 -0400
>> From: Internet-Drafts@ietf.org
>> Reply-To: internet-drafts@ietf.org
>> To: i-d-announce@ietf.org
>> 
>> A New Internet-Draft is available from the on-line 
>> Internet-Drafts directories.
>> 
>> 
>> 	Title		: IPv6 Router Advertisement Flags Option
>> 	Author(s)	: B. Haberman, R. Hinden
>> 	Filename	: draft-haberman-ipv6-ra-flags-option-00.txt
>> 	Pages		: 7
>> 	Date		: 2006-8-1
>> 	
>> The IPv6 Neighbor Discovery's Router Advertisement message 
>> contains an 8-bit field reserved for single-bit flags.  
>> Several protocols have reserved flags in this field and 
>> others are preparing to reserve a sufficient number of flags 
>> to exhaust the field.  This document defines an option to the 
>> Router Advertisement message that expands the available 
>> number of flag bits available.
>> 
>> 
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-haberman-ipv6-ra-fla
>> gs-option-00.txt
>> 
>> 
>
>--------------------------------------------------------------------
>IETF IPv6 working group mailing list
>ipv6@ietf.org
>Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>--------------------------------------------------------------------


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



From ipv6-bounces@ietf.org Mon Feb 05 16:27:38 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HEBKU-0008TL-UT; Mon, 05 Feb 2007 16:24:50 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HEBKT-0008Sz-Gq
	for ipv6@ietf.org; Mon, 05 Feb 2007 16:24:49 -0500
Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HEBHy-0004K0-Jj
	for ipv6@ietf.org; Mon, 05 Feb 2007 16:22:16 -0500
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l15LJb73022879; Mon, 5 Feb 2007 23:19:52 +0200
Received: from esebh002.NOE.Nokia.com ([172.21.138.77]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Feb 2007 23:20:08 +0200
Received: from [172.19.74.66] ([172.19.74.66]) by esebh002.NOE.Nokia.com with
	Microsoft SMTPSVC(5.0.2195.6881); Mon, 5 Feb 2007 23:20:07 +0200
In-Reply-To: <EF2F0EC839870F43A6637360BC12ABD4010A6CAA@PACDCEXCMB05.cable.comcast.com>
References: <EF2F0EC839870F43A6637360BC12ABD4010A6CAA@PACDCEXCMB05.cable.comcast.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <38AB167D-1233-443F-91D1-DDD7FBF9F933@nokia.com>
Content-Transfer-Encoding: 7bit
From: Bob Hinden <bob.hinden@nokia.com>
Date: Mon, 5 Feb 2007 13:20:37 -0800
To: "Durand, Alain" <Alain_Durand@cable.comcast.com>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 05 Feb 2007 21:20:08.0033 (UTC)
	FILETIME=[694CFD10:01C7496B]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Cc: Brian Haberman <brian@innovationslab.net>, ipv6@ietf.org
Subject: Re: WG Request: Adopt draft-haberman-ipv6-ra-flags-option-00.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bob.hinden@nokia.com
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi,

On Feb 5, 2007, at 9:14 AM, Durand, Alain wrote:

> I would like to ask what is the transition plan for "legacy" IPv6  
> hosts
> that do not implement this extension before I could consider this  
> draft
> a viable approach.

RFC2461, Section 4.2 says the following about new options:

       Future versions of this protocol may define new option types.
       Receivers MUST silently ignore any options they do not recognize
       and continue processing the message.

Any legacy host that didn't support the new option also wouldn't know  
how to support anything defined in the extension space.  So I don't  
think there is a problem with legacy hosts.

> We have a number of bits that are currently defined that may be
> questionable,
> (the best example: O & M), so I would like to see some more
> justification
> why more bits are needed for the general RA case and maybe some  
> clean-up
> of the current bits before we embark into defining a new space for
> potentially questionable new cases.

The intent of the draft was to document in one place all of the  
current bits and provide a way of creating new ones.

In my personal view, any discussion cleaning up the RA bits would  
take a very long time (based on the time it took for the w.g. to  
agree on the current text on the O&M bits), so I see very little  
value in trying to clean up the bits.  Further, back to your first  
question, cleaning up the bits would create a significant operational  
problem.

Bob

>
> So, at this point, I do not support this draft.
>
>   - Alain.
>
>
>
>> -----Original Message-----
>> From: Brian Haberman [mailto:brian@innovationslab.net]
>> Sent: Friday, February 02, 2007 12:41 PM
>> To: ipv6@ietf.org
>> Subject: WG Request: Adopt draft-haberman-ipv6-ra-flags-option-00.txt
>>
>> All,
>>      This is a formal call to request IPv6 WG feedback on
>> adopting the below draft.  The premise of the draft is to
>> expand the flags field that is quickly running out of bits.
>>
>>      Please provide your preference (positive or negative) on
>> having this document become an IPv6 WG document.  Comments on
>> the contents are most welcome as well.
>>
>> Regards,
>> Brian
>>
>>
>> -------- Original Message --------
>> Subject: I-D ACTION:draft-haberman-ipv6-ra-flags-option-00.txt
>> Date: Tue, 01 Aug 2006 15:50:01 -0400
>> From: Internet-Drafts@ietf.org
>> Reply-To: internet-drafts@ietf.org
>> To: i-d-announce@ietf.org
>>
>> A New Internet-Draft is available from the on-line
>> Internet-Drafts directories.
>>
>>
>> 	Title		: IPv6 Router Advertisement Flags Option
>> 	Author(s)	: B. Haberman, R. Hinden
>> 	Filename	: draft-haberman-ipv6-ra-flags-option-00.txt
>> 	Pages		: 7
>> 	Date		: 2006-8-1
>> 	
>> The IPv6 Neighbor Discovery's Router Advertisement message
>> contains an 8-bit field reserved for single-bit flags.
>> Several protocols have reserved flags in this field and
>> others are preparing to reserve a sufficient number of flags
>> to exhaust the field.  This document defines an option to the
>> Router Advertisement message that expands the available
>> number of flag bits available.
>>
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-haberman-ipv6-ra-fla
>> gs-option-00.txt
>>
>>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


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



From ipv6-bounces@ietf.org Mon Feb 05 16:46:26 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HEBee-0005ZJ-79; Mon, 05 Feb 2007 16:45:40 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HEBec-0005U0-Sk
	for ipv6@ietf.org; Mon, 05 Feb 2007 16:45:38 -0500
Received: from paoakoavas10.cable.comcast.com ([208.17.35.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HEBeZ-0000kK-Km
	for ipv6@ietf.org; Mon, 05 Feb 2007 16:45:38 -0500
Received: from ([10.195.246.152])
	by paoakoavas10.cable.comcast.com with ESMTP  id KP-TDCH3.29994198;
	Mon, 05 Feb 2007 16:45:11 -0500
Received: from PACDCEXCMB05.cable.comcast.com ([24.40.15.116]) by
	NJMDCEXCRLY01.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.1830); Mon, 5 Feb 2007 16:45:11 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 5 Feb 2007 16:45:08 -0500
Message-ID: <EF2F0EC839870F43A6637360BC12ABD4010A6E0B@PACDCEXCMB05.cable.comcast.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WG Request: Adopt draft-haberman-ipv6-ra-flags-option-00.txt
Thread-Index: AcdJa+jaqdjUu1PoT6y6FmupA8hB9QAAdETQ
From: "Durand, Alain" <Alain_Durand@cable.comcast.com>
To: <bob.hinden@nokia.com>
X-OriginalArrivalTime: 05 Feb 2007 21:45:11.0161 (UTC)
	FILETIME=[E93C1E90:01C7496E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: Brian Haberman <brian@innovationslab.net>, ipv6@ietf.org
Subject: RE: WG Request: Adopt draft-haberman-ipv6-ra-flags-option-00.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

=20

> -----Original Message-----
> From: Bob Hinden [mailto:bob.hinden@nokia.com]=20
> RFC2461, Section 4.2 says the following about new options:
>=20
>        Future versions of this protocol may define new option types.
>        Receivers MUST silently ignore any options they do not=20
> recognize
>        and continue processing the message.
>=20
> Any legacy host that didn't support the new option also=20
> wouldn't know how to support anything defined in the=20
> extension space.  So I don't think there is a problem with=20
> legacy hosts.

One thing I found unclear from the draft was if the 'legacy' bits
will be 'ported' or not to the new space. If they are 'ported',
one need to explain what happens if the bits do not match.

Also, if a new bit is deemed essential and must be reserved in the RA,
I wonder how this could in practise be deployed in a real network
given the number of existing implementations. In other words,
I wonder if it is not too late to go that route.


> > We have a number of bits that are currently defined that may be=20
> > questionable, (the best example: O & M), so I would like to=20
> see some=20
> > more justification why more bits are needed for the general RA case=20
> > and maybe some clean-up of the current bits before we embark into=20
> > defining a new space for potentially questionable new cases.
>=20
> The intent of the draft was to document in one place all of=20
> the current bits and provide a way of creating new ones.
>=20
> In my personal view, any discussion cleaning up the RA bits=20
> would take a very long time (based on the time it took for=20
> the w.g. to agree on the current text on the O&M bits), so I=20
> see very little value in trying to clean up the bits. =20
> Further, back to your first question, cleaning up the bits=20
> would create a significant operational problem.

IMHO, the O&M debacle demonstrates that specifying bits before
their usage is well understood is not wise.

   - Alain.

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



From ipv6-bounces@ietf.org Mon Feb 05 17:55:33 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HECgd-0004g5-Ac; Mon, 05 Feb 2007 17:51:47 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HECgc-0004fy-1p
	for ipv6@ietf.org; Mon, 05 Feb 2007 17:51:46 -0500
Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HECga-0006JP-Kb
	for ipv6@ietf.org; Mon, 05 Feb 2007 17:51:46 -0500
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l15Mn8Ec008218; Tue, 6 Feb 2007 00:49:22 +0200
Received: from esebh002.NOE.Nokia.com ([172.21.138.77]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 Feb 2007 00:51:14 +0200
Received: from [172.19.74.66] ([172.19.74.66]) by esebh002.NOE.Nokia.com with
	Microsoft SMTPSVC(5.0.2195.6881); Tue, 6 Feb 2007 00:51:13 +0200
In-Reply-To: <EF2F0EC839870F43A6637360BC12ABD4010A6E0B@PACDCEXCMB05.cable.comcast.com>
References: <EF2F0EC839870F43A6637360BC12ABD4010A6E0B@PACDCEXCMB05.cable.comcast.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <A8714F23-75E0-4353-96A6-EE9F57E7A808@nokia.com>
Content-Transfer-Encoding: 7bit
From: Bob Hinden <bob.hinden@nokia.com>
Date: Mon, 5 Feb 2007 14:51:43 -0800
To: "ext Durand, Alain" <Alain_Durand@cable.comcast.com>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 05 Feb 2007 22:51:13.0972 (UTC)
	FILETIME=[23411740:01C74978]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: Brian Haberman <brian@innovationslab.net>, ipv6@ietf.org
Subject: Re: WG Request: Adopt draft-haberman-ipv6-ra-flags-option-00.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bob.hinden@nokia.com
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Alain,

>> Any legacy host that didn't support the new option also
>> wouldn't know how to support anything defined in the
>> extension space.  So I don't think there is a problem with
>> legacy hosts.
>
> One thing I found unclear from the draft was if the 'legacy' bits
> will be 'ported' or not to the new space. If they are 'ported',
> one need to explain what happens if the bits do not match.

All of the existing bits are defined (and referenced in the draft) by  
RFCs and remain in the RA header.  The draft does not change any of  
these bit assignments.  The key text in the draft:

    The bit fields within the option are numbered from left to right  
from
    8 to 47 and follow the numbering of the flag bits in the RA option
    described in Figure 1.

Please suggest text to clarify what you see as an issue.

> Also, if a new bit is deemed essential and must be reserved in the RA,
> I wonder how this could in practise be deployed in a real network
> given the number of existing implementations. In other words,
> I wonder if it is not too late to go that route.

The new bits (8 - 47) define new options.  These options are ignored  
by existing implementations and may be implemented by new  
implementations.  You are correct that one can not define an new  
option that existing implementations need to support.  If  
implementations done see any value in the option, then it won't get  
supported, and vice versa.  All this draft is doing is to define  
additional RA bits.  There are several protocols in the pipeline (in  
other working groups) who need RA bits.

Bob



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



From ipv6-bounces@ietf.org Tue Feb 06 07:41:15 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HEPXP-0000Wy-2D; Tue, 06 Feb 2007 07:35:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HEPXN-0000VD-La
	for ipv6@ietf.org; Tue, 06 Feb 2007 07:35:05 -0500
Received: from mail127.messagelabs.com ([216.82.250.115])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HEPXL-0000Ib-8i
	for ipv6@ietf.org; Tue, 06 Feb 2007 07:35:05 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@motorola.com
X-Msg-Ref: server-7.tower-127.messagelabs.com!1170765299!2975182!1
X-StarScan-Version: 5.5.10.7.1; banners=-,-,-
X-Originating-IP: [144.189.100.105]
Received: (qmail 28470 invoked from network); 6 Feb 2007 12:35:00 -0000
Received: from motgate5.mot.com (HELO motgate5.mot.com) (144.189.100.105)
	by server-7.tower-127.messagelabs.com with SMTP;
	6 Feb 2007 12:35:00 -0000
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate5.mot.com (8.12.11/Motorola) with ESMTP id l16CYx3Z022019;
	Tue, 6 Feb 2007 05:34:59 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id l16CYudV007941;
	Tue, 6 Feb 2007 06:34:57 -0600 (CST)
Message-ID: <45C875EF.4040501@motorola.com>
Date: Tue, 06 Feb 2007 13:34:55 +0100
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Brian E Carpenter <brc@zurich.ibm.com>
References: <45C377A5.3020008@innovationslab.net>	<90cbfd80702032137p3e10df4ie1d0042586168cd9@mail.gmail.com>
	<45C5B9E3.9070902@zurich.ibm.com>
In-Reply-To: <45C5B9E3.9070902@zurich.ibm.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Cc: Brian Haberman <brian@innovationslab.net>, ipv6@ietf.org
Subject: Re: new NDP option or new RA option (was: WG Request: Adopt
	draft-haberman-ipv6-ra-flags-option-00.txt)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Brian E Carpenter wrote:
> It's expired. Try 
> http://tools.ietf.org/id/draft-haberman-ipv6-ra-flags-option-00.txt

The draft describes an option to be included in the RA.  However,
section 4 calls it a "NDP Expansion Option", meaning this option could
be included in - other than RA - NDP messages(?)

One would clarify that this Flags Expansion Option is to be used only
preceded by the RA header (Type 134).

At least because the necessity of this new option with flags comes
exclusively from the lack of flag space in RA, not in NS for example.

No?

Alex

> 
> Brian
> 
> On 2007-02-04 06:37, Guilherme Sperb Machado wrote:
>> The draft link is not working. How can I read the proposed draft?
>> 
>> Thanks in advance, Guilherme Sperb Machado
>> 
>> On 2/2/07, Brian Haberman <brian@innovationslab.net> wrote:
>>> All, This is a formal call to request IPv6 WG feedback on 
>>> adopting the below draft.  The premise of the draft is to expand 
>>> the flags field that is quickly running out of bits.
>>> 
>>> Please provide your preference (positive or negative) on having 
>>> this document become an IPv6 WG document.  Comments on the 
>>> contents are most welcome as well.
>>> 
>>> Regards, Brian
>>> 
>>> 
>>> -------- Original Message -------- Subject: I-D 
>>> ACTION:draft-haberman-ipv6-ra-flags-option-00.txt Date: Tue, 01 
>>> Aug 2006 15:50:01 -0400 From: Internet-Drafts@ietf.org Reply-To: 
>>> internet-drafts@ietf.org To: i-d-announce@ietf.org
>>> 
>>> A New Internet-Draft is available from the on-line 
>>> Internet-Drafts directories.
>>> 
>>> 
>>> Title           : IPv6 Router Advertisement Flags Option 
>>> Author(s)       : B. Haberman, R. Hinden Filename        : 
>>> draft-haberman-ipv6-ra-flags-option-00.txt Pages           : 7 
>>> Date            : 2006-8-1
>>> 
>>> The IPv6 Neighbor Discovery's Router Advertisement message 
>>> contains an 8-bit field reserved for single-bit flags.  Several 
>>> protocols have reserved flags in this field and others are 
>>> preparing to reserve a sufficient number of flags to exhaust the 
>>> field.  This document defines an option to the Router 
>>> Advertisement message that expands the available number of flag 
>>> bits available.
>>> 
>>> 
>>> A URL for this Internet-Draft is: 
>>> http://www.ietf.org/internet-drafts/draft-haberman-ipv6-ra-flags-option-00.txt
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> Content-Type: text/plain Content-ID: 
>>> <2006-8-1141246.I-D@ietf.org>
>>> 
>>> 
>>> 
>>> 
>>> --------------------------------------------------------------------
>>>  IETF IPv6 working group mailing list ipv6@ietf.org 
>>> Administrative Requests: 
>>> https://www1.ietf.org/mailman/listinfo/ipv6 
>>> --------------------------------------------------------------------
>>> 
>>> 
>>> 
>>> 
>>> 
>> 
>> --------------------------------------------------------------------
>>  IETF IPv6 working group mailing list ipv6@ietf.org Administrative 
>> Requests: https://www1.ietf.org/mailman/listinfo/ipv6 
>> --------------------------------------------------------------------
>> 
>> 
>> 
> 
> --------------------------------------------------------------------
>  IETF IPv6 working group mailing list ipv6@ietf.org Administrative 
> Requests: https://www1.ietf.org/mailman/listinfo/ipv6 
> --------------------------------------------------------------------
> 


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



From ipv6-bounces@ietf.org Tue Feb 06 13:06:22 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HEUcg-0006yt-07; Tue, 06 Feb 2007 13:00:54 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HETee-0002Ds-9S
	for ipv6@ietf.org; Tue, 06 Feb 2007 11:58:52 -0500
Received: from piper.jhuapl.edu ([128.244.26.33] helo=jhuapl.edu)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HETec-0002m0-UL
	for ipv6@ietf.org; Tue, 06 Feb 2007 11:58:52 -0500
Received: from ([128.244.206.105])
	by piper.jhuapl.edu with ESMTP  id 5502121.19785678;
	Tue, 06 Feb 2007 11:58:28 -0500
Message-ID: <45C8B3B4.8000002@innovationslab.net>
Date: Tue, 06 Feb 2007 11:58:28 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
References: <45C377A5.3020008@innovationslab.net>	<90cbfd80702032137p3e10df4ie1d0042586168cd9@mail.gmail.com>
	<45C5B9E3.9070902@zurich.ibm.com> <45C875EF.4040501@motorola.com>
In-Reply-To: <45C875EF.4040501@motorola.com>
X-Enigmail-Version: 0.94.1.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
X-Mailman-Approved-At: Tue, 06 Feb 2007 13:00:53 -0500
Cc: ipv6@ietf.org
Subject: Re: new NDP option or new RA option
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org



Alexandru Petrescu wrote:
> Brian E Carpenter wrote:
>> It's expired. Try
>> http://tools.ietf.org/id/draft-haberman-ipv6-ra-flags-option-00.txt
> 
> The draft describes an option to be included in the RA.  However,
> section 4 calls it a "NDP Expansion Option", meaning this option could
> be included in - other than RA - NDP messages(?)

I suppose it could but the context is lost given that the IANA registry
starts with the flag bits already defined in the RA header.

> 
> One would clarify that this Flags Expansion Option is to be used only
> preceded by the RA header (Type 134).
> 
> At least because the necessity of this new option with flags comes
> exclusively from the lack of flag space in RA, not in NS for example.
> 
> No?
> 

That is true.  We can certainly incorporate text to make that explicit.

Regards,
Brian

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



From ipv6-bounces@ietf.org Wed Feb 07 11:57:02 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HEq1S-00064l-TS; Wed, 07 Feb 2007 11:51:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HEj0K-0005du-NO
	for ipv6@ietf.org; Wed, 07 Feb 2007 04:22:16 -0500
Received: from smtp-vbr2.xs4all.nl ([194.109.24.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HEj0J-0004pX-09
	for ipv6@ietf.org; Wed, 07 Feb 2007 04:22:16 -0500
Received: from [145.99.234.66] (66-234.surfsnel.dsl.internl.net
	[145.99.234.66]) (authenticated bits=0)
	by smtp-vbr2.xs4all.nl (8.13.8/8.13.8) with ESMTP id l179M7Xt022749
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 7 Feb 2007 10:22:07 +0100 (CET) (envelope-from huizer@cs.uu.nl)
Message-ID: <45C99A45.3060507@cs.uu.nl>
Date: Wed, 07 Feb 2007 10:22:13 +0100
From: Erik Huizer <huizer@cs.uu.nl>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: ipv6@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by XS4ALL Virus Scanner
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
X-Mailman-Approved-At: Wed, 07 Feb 2007 11:51:52 -0500
Cc: Peter van Eijk <peter@van-eijk.net>, bob.hinden@nokia.com
Subject: IPv6 cases sought
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi,

The Dutch IPv6 Task Force (which I chair) has embarked on a study of
real-life IPv6 implementations in order to facilitate strategic
management investment decisions in IPv6.
The result of this study will be a brief report with case studies
describing business cases, urgency, generic project plans and lessons
and benefits learned from real implementations (if any).

I am seeking your help in identifying organisations that have 
succesfully implemented IPv6 in their network, with which we can
have interviews (e-mail or phone) on their IPv6 plans and migrations.
Specifically we are looking for organisations with a (commercial)
businesscase, i.e. who are not doing it just for the research or
demonstration value.

You only need to point us to them, and introduce us. They will then be
contacted by Peter van Eijk who is doing the actual study. We are eager
to start in the next couple of days.

Your collaboration is truly appreciated, and we will be happy to share
the results with you.


Feel free to forward this entire message.

Thanks,
Erik


=============================================
prof. dr. Erik Huizer
Internet Applications
Department of Information & Computing Sciences
University Utrecht
The Netherlands


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



From ipv6-bounces@ietf.org Fri Feb 09 10:05:48 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HFXCz-0005EF-58; Fri, 09 Feb 2007 09:58:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HFXCx-0005E7-DW
	for ipv6@ietf.org; Fri, 09 Feb 2007 09:58:39 -0500
Received: from smtp2.int-evry.fr ([157.159.10.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HFXCr-0005t1-NJ
	for ipv6@ietf.org; Fri, 09 Feb 2007 09:58:39 -0500
Received: from lor-maknavic3.int-evry.fr (lor-maknavic3.int-evry.fr
	[157.159.103.217])
	by smtp2.int-evry.fr (Postfix) with ESMTP id 7553B30017;
	Fri,  9 Feb 2007 15:58:26 +0100 (CET)
From: Pars Mutaf <pars.mutaf@int-evry.fr>
To: namedroppers@ops.ietf.org, ipv6@ietf.org
In-Reply-To: <1170195757.45bfc52de120e@imp.int-evry.fr>
References: <1168423598.15925.24.camel@lor-maknavic3.int-evry.fr>
	<45AA0D9D.4080705@piuha.net> <1168800701.45aa7bbdc4fdb@imp.int-evry.fr>
	<1170195757.45bfc52de120e@imp.int-evry.fr>
Content-Type: text/plain
Organization: INT Evry
Date: Fri, 09 Feb 2007 15:58:34 +0100
Message-Id: <1171033115.27018.6.camel@lor-maknavic3.int-evry.fr>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.1 
Content-Transfer-Encoding: 7bit
X-INT-MailScanner-Information: Please contact the ISP for more information
X-INT-MailScanner: Found to be clean
X-INT-MailScanner-MCPCheck: 
X-INT-MailScanner-SpamCheck: 
X-INT-MailScanner-From: pars.mutaf@int-evry.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Cc: 
Subject: better MNR or bypassing it
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: pars.mutaf@int-evry.fr
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Dear all, 

Quick reminder: the problem that I'm bringing to your 
attention is:

http://www.ietf.org/internet-drafts/draft-mutaf-piqproblem-00.txt

Here is a better formulated question. We have choices (the above
cited application largely merits one of them):

1. IETF designs a more general purpose multicast name resolution 
   protocol. Thanks :-) 
   Currently it is too much ZEROCONF-oriented. There are possibly 
   many other applications that will use multicast name 
   resolution. The above cited example is a very good one. The 
   above cited problem is poorly addressed by current multicast 
   name resolution protocols. 

2. Otherwise, the above cited application (private information 
   queries) can simply bypass name resolution. It can use 
   name-based IPv6 addresses (or HUMID addresses). No solution 
   will be provided for IPv4. This solution would work as follows 
   (briefly):

   The responder application run by Alice Collins' cellular host 
   configures a link-local IPv6 address and listens:

         link-local subnet prefix | 64bithash(alicecollins)

   where '|' denotes concatenation, and link-local subnet prefix
   is well-known and constant. 64bithash(alicecollins) is the 
   IPv6 interface ID.

   The initiator user enters the name Alice Collins and hence the 
   application can generate a query to the above address. The 
   phone number of Alice Collins can be learned from her phone 
   directly (if approved by her).

   It is also possible to search a host in multiple subnets 
   (using global scope addresses). I can explain this point if 
   you wish. It can also work with localized mobility management 
   and even Mobile IPv6, provided that you have the same 
   home/regional prefix with Alice Collins. This means that we 
   are not limited to link-local scope. But this needs more
   investigation.


Looking forward to your suggestions.

Thanks,

pars mutaf
   




On Tue, 2007-01-30 at 23:22 +0100, Pars MUTAF wrote:

> I would like to bring a new problem statement draft to your
> attention (1 page). Until it appears in the I-D rep, please
> find it here:
> 
> http://www.freewebs.com/pmutaf/draft-mutaf-piqproblem-00.txt
> 
> I believe that not having this application
> would be very unfortunate. (I think this is an INT area topic.)
> And currently available name resolution techniques do not
> address this problem as they should.
> 
> Do you have any comments on this problem statement?
> 
> Thanks.
> pars mutaf



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



From ipv6-bounces@ietf.org Fri Feb 09 14:56:51 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HFbnr-0006yf-2o; Fri, 09 Feb 2007 14:53:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HFbnp-0006yZ-SB
	for ipv6@ietf.org; Fri, 09 Feb 2007 14:53:01 -0500
Received: from slb-smtpout-01.boeing.com ([130.76.64.48]
	helo=slb-smtpout-01.ns.cs.boeing.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HFbnj-0004Ph-Em
	for ipv6@ietf.org; Fri, 09 Feb 2007 14:53:01 -0500
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [192.42.227.216])
	by slb-smtpout-01.ns.cs.boeing.com (8.13.6/8.13.6/TEST_SMTPIN) with
	ESMTP id l19JqpAi003223
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 9 Feb 2007 11:52:51 -0800 (PST)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.13.6/8.13.6/DOWNSTREAM_RELAY) with ESMTP id
	l19JqpIV002723; Fri, 9 Feb 2007 11:52:51 -0800 (PST)
Received: from XCH-NEBH-11.ne.nos.boeing.com (xch-nebh-11.ne.nos.boeing.com
	[128.225.80.27])
	by blv-av-01.boeing.com (8.13.6/8.13.6/UPSTREAM_RELAY) with ESMTP id
	l19Jqnsv002633; Fri, 9 Feb 2007 11:52:50 -0800 (PST)
Received: from XCH-NE-1V2.ne.nos.boeing.com ([128.225.80.43]) by
	XCH-NEBH-11.ne.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 9 Feb 2007 14:52:45 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 9 Feb 2007 14:52:44 -0500
Message-ID: <CA7D9B4A761066448304A6AFC09ABDA9015ACFEC@XCH-NE-1V2.ne.nos.boeing.com>
In-Reply-To: <1171033115.27018.6.camel@lor-maknavic3.int-evry.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: better MNR or bypassing it
Thread-Index: AcdMW+wcfqHaIbeGTIOc8EqsyoOFewAJtGkg
References: <1168423598.15925.24.camel@lor-maknavic3.int-evry.fr><45AA0D9D.4080705@piuha.net>
	<1168800701.45aa7bbdc4fdb@imp.int-evry.fr><1170195757.45bfc52de120e@imp.int-evry.fr>
	<1171033115.27018.6.camel@lor-maknavic3.int-evry.fr>
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: <pars.mutaf@int-evry.fr>, <namedroppers@ops.ietf.org>, <ipv6@ietf.org>
X-OriginalArrivalTime: 09 Feb 2007 19:52:45.0267 (UTC)
	FILETIME=[DE056230:01C74C83]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: 
Subject: RE: better MNR or bypassing it
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> -----Original Message-----
> From: Pars Mutaf [mailto:pars.mutaf@int-evry.fr]=20
> Dear all,=20
>=20
> Quick reminder: the problem that I'm bringing to your=20
> attention is:
>=20
> http://www.ietf.org/internet-drafts/draft-mutaf-piqproblem-00.txt

Pars, it seems to me that the reason cell phone numbers are hard to get
is that cell phone users have long preferred it to remain that way. For
that matter, with sales people completely abusing the regular land line
phone system, I believe the majority of land line telephone subscribers
would have preferred that other phone system to be equally made
difficult to abuse.

So I don't think that making it easier to distribute cell phone
telephone numbers is something that technology is preventing.

In your proposal, for example, the problem will happen when obnoxious,
over the top sales critters (as they have proven themselves to be)
figure out how to pretend they are alicecollins making the request for
your phone number. Your will reply "yes," and then you're screwed.

Or, alternatively, an alicecollins is making this request, but the one
you really know is called alicejcollins. Now this unknown person has
your cell number.

In short, I don't think it is technology that is needed here.

Bert

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



From ipv6-bounces@ietf.org Sat Feb 10 19:10:45 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HG2CE-0003o7-FC; Sat, 10 Feb 2007 19:03:58 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HG2CC-0003m1-24
	for ipv6@ietf.org; Sat, 10 Feb 2007 19:03:56 -0500
Received: from [2002:425c:4242:0:210:5aff:fe86:1f54] (helo=cyteen.hactrn.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HG28W-0007YU-AC
	for ipv6@ietf.org; Sat, 10 Feb 2007 19:00:09 -0500
Received: from cyteen.hactrn.net (localhost [127.0.0.1])
	by cyteen.hactrn.net (Postfix) with ESMTP id 9C58F28428
	for <ipv6@ietf.org>; Sun, 11 Feb 2007 00:00:03 +0000 (UTC)
To: ipv6@ietf.org
From: Rob Austein <sra+ipng@hactrn.net>
Date: Sun, 11 Feb 2007 00:00:03 +0000
Message-Id: <20070211000003.9C58F28428@cyteen.hactrn.net>
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Subject: Weekly posting summary for ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 12.50% |    2 | 14.46% |    13486 | timbeck04@verizon.net
 12.50% |    2 | 13.80% |    12863 | alexandru.petrescu@motorola.com
 12.50% |    2 | 13.71% |    12780 | bob.hinden@nokia.com
 12.50% |    2 | 12.34% |    11505 | alain_durand@cable.comcast.com
  6.25% |    1 |  7.25% |     6758 | brc@zurich.ibm.com
  6.25% |    1 |  6.50% |     6060 | pars.mutaf@int-evry.fr
  6.25% |    1 |  6.19% |     5775 | gsmachado@gmail.com
  6.25% |    1 |  6.10% |     5690 | albert.e.manfredi@boeing.com
  6.25% |    1 |  6.09% |     5678 | suresh.krishnan@ericsson.com
  6.25% |    1 |  4.88% |     4550 | huizer@cs.uu.nl
  6.25% |    1 |  4.52% |     4214 | brian@innovationslab.net
  6.25% |    1 |  4.16% |     3878 | sra+ipng@hactrn.net
--------+------+--------+----------+------------------------
100.00% |   16 |100.00% |    93237 | Total

Grunchweather Associates provides this automatic summary on an at-whim
basis at the request of the IPv6 WG chairs.  Your mileage may vary.
We decline responsibilities, all shapes, all sizes, all colors.
If this script produces broken output, you get to keep both pieces.

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



From ipv6-bounces@ietf.org Sun Feb 11 06:08:04 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGCTI-0003fW-E5; Sun, 11 Feb 2007 06:02:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGCTG-0003fR-RD
	for ipv6@ietf.org; Sun, 11 Feb 2007 06:02:14 -0500
Received: from massilia.int-evry.fr ([157.159.10.13])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HGCTA-00022X-9F
	for ipv6@ietf.org; Sun, 11 Feb 2007 06:02:14 -0500
Received: from massilia.int-evry.fr (localhost.localdomain [127.0.0.1])
	by massilia.int-evry.fr (8.12.11/8.12.11) with ESMTP id l1BB1uEh009158; 
	Sun, 11 Feb 2007 12:01:56 +0100
Received: (from apache@localhost)
	by massilia.int-evry.fr (8.12.11/8.12.11/Submit) id l1BB1uqM009155;
	Sun, 11 Feb 2007 12:01:56 +0100
X-Authentication-Warning: massilia.int-evry.fr: apache set sender to
	Pars.Mutaf@int-evry.fr using -f
Received: from www.passagesaintsebastien.com (www.passagesaintsebastien.com
	[81.57.101.151]) by imp.int-evry.fr (IMP) with HTTP 
	for <mutaf_pa@localhost>; Sun, 11 Feb 2007 12:01:55 +0100
Message-ID: <1171191715.45cef7a3e3477@imp.int-evry.fr>
Date: Sun, 11 Feb 2007 12:01:55 +0100
From: Pars MUTAF <Pars.Mutaf@int-evry.fr>
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
References: <1168423598.15925.24.camel@lor-maknavic3.int-evry.fr><45AA0D9D.4080705@piuha.net>
	<1168800701.45aa7bbdc4fdb@imp.int-evry.fr><1170195757.45bfc52de120e@imp.int-evry.fr>
	<1171033115.27018.6.camel@lor-maknavic3.int-evry.fr>
	<CA7D9B4A761066448304A6AFC09ABDA9015ACFEC@XCH-NE-1V2.ne.nos.boeing.com>
In-Reply-To: <CA7D9B4A761066448304A6AFC09ABDA9015ACFEC@XCH-NE-1V2.ne.nos.boeing.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.2.5
X-Originating-IP: 81.57.101.151
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2ed806e2f53ff1a061ad4f97e00345ac
Cc: namedroppers@ops.ietf.org, ipv6@ietf.org
Subject: Private Information Queries (was RE: better MNR or bypassing it)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


Hello,

Thanks much for all good questions. Please see below:


Selon "Manfredi, Albert E" <albert.e.manfredi@boeing.com>:

> > -----Original Message-----
> > From: Pars Mutaf [mailto:pars.mutaf@int-evry.fr]
> > Dear all,
> >
> > Quick reminder: the problem that I'm bringing to your
> > attention is:
> >
> > http://www.ietf.org/internet-drafts/draft-mutaf-piqproblem-00.txt
>
> Pars, it seems to me that the reason cell phone numbers are hard to get
> is that cell phone users have long preferred it to remain that way.


I don't agree with you here. Cell phone users had no choice. They were and
still are subject to a fundamental trade-off between privacy and
reachability.

I have seen users, with broken cell phones, or who have lost their phone.
They are simply in trouble. They have hard time recovering the cell phone
numbers of their friends, colleagues, family members etc.

I have seen users (including myself) exchanging phone numbers in
ridiculous ways. The first number is read to the other user, and the other
user returns his/her number via the cellular network. It should be noted
that this also requires short distance user contact. If the other user is
100 meters away, you see each other but you are in a crowded place and you
can't reach each other, you simply cannot communicate. You have cellular
phones but are unable to communicate.

Or, just after a tsunami, someone that I know is lost. But I don't have
a cell phone (or lost it). I can borrow a phone from someone else but I
don't have the phone number.

Or simply, you need another user's phone number but you don't have it yet.
You know each other but you have not exchanged your phone numbers yet.

etc etc...


> For
> that matter, with sales people completely abusing the regular land line
> phone system, I believe the majority of land line telephone subscribers
> would have preferred that other phone system to be equally made
> difficult to abuse.


This is an excellent point. Please see below.


>
> So I don't think that making it easier to distribute cell phone
> telephone numbers is something that technology is preventing.



The main requirement is that if you need private information about Alice,
you should ask Alice. Alice will decide in *real-time* (real-time is
really the keyword here). The decision belongs to Alice.

We have Bluetooth, IrDA etc, but they require user contact. Surprisingly
we cannot exchange private information via a cellular network (i.e. over
very large distances). I suspect that this is simply because we don't have
multicast name resolution or name-based IPv6 addresses currently (in
cellular context). Please take my last sentence seriously. I mean it.
These are the only solutions for learning someone's IP address from
his/her human name. And if you don't know Alice's device's IP address,
you cannot reach her phone and request her phone number.

I think this also answers a good question like: "If this protocol is that
important why we don't have it today?"... I think the answer is above.


> In your proposal, for example, the problem will happen when obnoxious,
> over the top sales critters (as they have proven themselves to be)
> figure out how to pretend they are alicecollins making the request for
> your phone number. Your will reply "yes," and then you're screwed.
>
> Or, alternatively, an alicecollins is making this request, but the one
> you really know is called alicejcollins. Now this unknown person has
> your cell number.


These are very sane and important concerns. This protocol must be designed
carefully. My point is that, *today*, we *have* well-known security
solutions to achieve that. A serious threat analysis must be made and the
protocol must be designed accordingly. Some of the potential threats and
defenses (I'm not expert on details):

     1. For example, as you have very well identified, the requesting
        user's identity must be verifiable. If not, the responder user
        must be notified. Again, the decision belongs to the user.

     2. There will be Denial-of-Service threats if we use public key
        cryptography. Same problem with IKE. In our case, we have an
        advantage: the requestor is necessarily a *human*. Consequently,
        CAPTCHAs (Turing test) may be used. All we need to do is to define
        a CAPTCHA option in our exchanges. Work is needed of course.

        URL: http://en.wikipedia.org/wiki/Captcha

     3. The last threat that you identified above looks like "phishing"
        to me. We have this problem on the web. I suspect that there is
        ongoing work on that. But anyway, I don't think this is a
        compelling enough reason to STOP this project.

Also,
some users may augment their own level of security by using a pseudonym
instead of their real name, etc etc.

If phone number information leaks (not because of the proposed protocol),
some users may periodically change their phone number (i.e. recovation).
But again, in this case, they will need the proposed protocol to
redistribute their new phone number more easily.

These decisions belong to the user.


>
> In short, I don't think it is technology that is needed here.


I think technology is needed, and we *have* this technology and the
necessary expertise. All we need to do is to put the pieces together.


Regards,

pars mutaf


>
> Bert
>



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

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



From ipv6-bounces@ietf.org Sun Feb 11 22:37:17 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGRuQ-0004aF-B7; Sun, 11 Feb 2007 22:31:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGRuN-0004a4-T7
	for ipv6@ietf.org; Sun, 11 Feb 2007 22:31:15 -0500
Received: from smtp.microsoft.com ([131.107.115.215])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HGRuK-0006la-J4
	for ipv6@ietf.org; Sun, 11 Feb 2007 22:31:15 -0500
Received: from TK5-EXHUB-C102.redmond.corp.microsoft.com (157.54.70.72) by
	TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with
	Microsoft
	SMTP Server (TLS) id 8.0.685.24; Sun, 11 Feb 2007 19:31:12 -0800
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com (157.54.0.39)
	by TK5-EXHUB-C102.redmond.corp.microsoft.com (157.54.70.72) with
	Microsoft SMTP Server id 8.0.685.24; Sun, 11 Feb 2007 19:31:11 -0800
Received: from WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com
	([157.54.62.24]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com
	with
	Microsoft SMTPSVC(6.0.3790.3953);	 Sun, 11 Feb 2007 19:31:11 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 11 Feb 2007 19:31:10 -0800
Message-ID: <70C6EFCDFC8AAD418EF7063CD132D064038CFF42@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <1171191715.45cef7a3e3477@imp.int-evry.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Private Information Queries (was RE: better MNR or bypassing it)
Thread-Index: AcdNzOIe3tWet7wTTny0ahfStiIGQAAgMjvw
References: <1168423598.15925.24.camel@lor-maknavic3.int-evry.fr><45AA0D9D.4080705@piuha.net><1168800701.45aa7bbdc4fdb@imp.int-evry.fr><1170195757.45bfc52de120e@imp.int-evry.fr><1171033115.27018.6.camel@lor-maknavic3.int-evry.fr><CA7D9B4A761066448304A6AFC09ABDA9015ACFEC@XCH-NE-1V2.ne.nos.boeing.com>
	<1171191715.45cef7a3e3477@imp.int-evry.fr>
From: Christian Huitema <huitema@windows.microsoft.com>
To: Pars MUTAF <Pars.Mutaf@int-evry.fr>, "Manfredi, Albert E"
	<albert.e.manfredi@boeing.com>
X-OriginalArrivalTime: 12 Feb 2007 03:31:11.0371 (UTC)
	FILETIME=[3DC345B0:01C74E56]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: namedroppers@ops.ietf.org, ipv6@ietf.org
Subject: RE: Private Information Queries (was RE: better MNR or bypassing it)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> I have seen users, with broken cell phones, or who have lost their
> phone. They are simply in trouble. They have hard time recovering the
cell
> phone numbers of their friends, colleagues, family members etc.

Do you mean that the only copy of their address book was inside their
cell phone? If that is the case, they will indeed have a hard time
retrieving all these numbers. On the other hand, there are many ways to
synchronize a cell phone with a PC or a server that keeps a safe copy.
You can even use vCards (RFC2426) do describe these entries in a
standardized way.

> I have seen users (including myself) exchanging phone numbers in
> ridiculous ways. The first number is read to the other user, and the
> other user returns his/her number via the cellular network. It should
be
> noted that this also requires short distance user contact. If the
other user
> is 100 meters away, you see each other but you are in a crowded place
and
> you can't reach each other, you simply cannot communicate. You have
> cellular phones but are unable to communicate.

That's ridiculous indeed, when you could simply attach vCard to an
e-mail. Not to mention publishing it in a web page, or make it available
to your friends in an instant-messaging service.

The problems that you describe hardly seem related to server-less name
resolution in a local network!

-- Christian Huitema




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



From ipv6-bounces@ietf.org Mon Feb 12 08:39:43 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGbLN-00085w-CN; Mon, 12 Feb 2007 08:35:45 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGbLJ-00085p-Ul
	for ipv6@ietf.org; Mon, 12 Feb 2007 08:35:41 -0500
Received: from smtp2.int-evry.fr ([157.159.10.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HGbLH-0005Y7-3T
	for ipv6@ietf.org; Mon, 12 Feb 2007 08:35:41 -0500
Received: from lor-maknavic3.int-evry.fr (lor-maknavic3.int-evry.fr
	[157.159.103.217])
	by smtp2.int-evry.fr (Postfix) with ESMTP id D76102FD37;
	Mon, 12 Feb 2007 14:35:29 +0100 (CET)
From: Pars Mutaf <pars.mutaf@int-evry.fr>
To: Christian Huitema <huitema@windows.microsoft.com>
In-Reply-To: <70C6EFCDFC8AAD418EF7063CD132D064038CFF42@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
References: <1168423598.15925.24.camel@lor-maknavic3.int-evry.fr>
	<45AA0D9D.4080705@piuha.net><1168800701.45aa7bbdc4fdb@imp.int-evry.fr>
	<1170195757.45bfc52de120e@imp.int-evry.fr>
	<1171033115.27018.6.camel@lor-maknavic3.int-evry.fr>
	<CA7D9B4A761066448304A6AFC09ABDA9015ACFEC@XCH-NE-1V2.ne.nos.boeing.com>
	<1171191715.45cef7a3e3477@imp.int-evry.fr>
	<70C6EFCDFC8AAD418EF7063CD132D064038CFF42@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain
Organization: INT Evry
Date: Mon, 12 Feb 2007 14:35:36 +0100
Message-Id: <1171287341.25622.12.camel@lor-maknavic3.int-evry.fr>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.1 
Content-Transfer-Encoding: 7bit
X-INT-MailScanner-Information: Please contact the ISP for more information
X-INT-MailScanner: Found to be clean
X-INT-MailScanner-MCPCheck: 
X-INT-MailScanner-SpamCheck: 
X-INT-MailScanner-From: pars.mutaf@int-evry.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
Cc: namedroppers@ops.ietf.org, ipv6@ietf.org
Subject: RE: Private Information Queries (was RE: better MNR or bypassing it)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: pars.mutaf@int-evry.fr
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi, 


On Sun, 2007-02-11 at 19:31 -0800, Christian Huitema wrote:
> I have seen users, with broken cell phones, or who have lost their
> phone. They are simply in trouble. They have hard time recovering the
> cell phone numbers of their friends, colleagues, family members etc.
> 
> Do you mean that the only copy of their address book was inside their
> cell phone? If that is the case, they will indeed have a hard time
> retrieving all these numbers. On the other hand, there are many ways
to
> synchronize a cell phone with a PC or a server that keeps a safe copy.
> You can even use vCards (RFC2426) do describe these entries in a
> standardized way.



That's right of course. Users should backup their correspondents' phone 
numbers to their PCs. However, this doesn't mean that they will do it 
unfortunately.

In addition, this assumes that everyone has a PC. 

In addition, even if you have a PC and even if you have a backup, 
I'm not sure if the PC will be immediately available when you buy a 
new phone (because the old one is broken).

Finally, I have also seen users with broken PCs.

(This happened recently, a friend has lost all his backup.)




> > I have seen users (including myself) exchanging phone numbers in
> > ridiculous ways. The first number is read to the other user, and the
> > other user returns his/her number via the cellular network. It
should
> > be noted that this also requires short distance user contact. If the
> > other user is 100 meters away, you see each other but you are in a 
> > crowded place and you can't reach each other, you simply cannot 
> > communicate. You have cellular phones but are unable to communicate.
> 
> That's ridiculous indeed, when you could simply attach vCard to an
> e-mail. Not to mention publishing it in a web page, or make it
available
> to your friends in an instant-messaging service.



Sending the phone number via e-mail is possible indeed, but this 
is a too indirect (hence slow) solution and makes some important 
assumptions. 

1. This assumes that you have the destination user's e-mail 
   address. BTW, I also think that the proposed protocol is not 
   limited to phone numbers. We can also request an e-mail 
   address. 

2. This solution is too indirect in that, you need service from 
   e-mail servers, which may be busy, temporarily unreachable, 
   the network may be congested etc. 

3. You have to wait until the mail arrives at the target mail box 
   and the user checks mail. Today we have special services 
   that notify the user upon new incoming mail. However, I'm not 
   sure how fast this is. In addition, this is an optional 
   service. 


Using an instant-messaging service has similar (almost same)
problems. 



> The problems that you describe hardly seem related to server-less name
> resolution in a local network!



The proposed protocol could also use infrastracture DNS (i.e. 
standard DNS). This would look as follows:

Let us assume that Alice Collins has a personal DNS name
"alicecollins.domain.com". Her phone has an IP address that is 
registered to this DNS name.

The requestor user enters the name Alice Collins, the proposed
application generates the corresponding DNS name, makes a 
standard DNS query, and obtains the IP address. At this point the 
proposed application can send a private information query to 
Alice's phone. If approved by Alice (in real-time), her phone 
number can be learned.

This would work globally, but I don't think this is realistic. 
(BTW, it can be noted that, one would ask why I need a phone 
number in this case.)

Using multicast name resolution (or, name-based IPv6 addresses)
with human names that have local significance only, seem 
realistic to me. Here the term "local" may take different 
meanings. It may be a local cellular network that covers a large 
number of cells, or a localized mobility management domain.

Such a local cellular zone can cover a large geographical area.
This is an important progress compared to using a technology
like Bluetooth (for exchanging private info). But the proposed 
protocol cannot work globally. That's why we need phone numbers
and our goal is to allow people to share their phone numbers 
more easily.

Regards,

pars mutaf

> 
> -- Christian Huitema
> 
> 
> 




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



From ipv6-bounces@ietf.org Wed Feb 14 13:09:20 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HHOVZ-00078Y-LS; Wed, 14 Feb 2007 13:05:33 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HHOVY-00077j-Hr
	for ipv6@ietf.org; Wed, 14 Feb 2007 13:05:32 -0500
Received: from smtp2.int-evry.fr ([157.159.10.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HHOVX-0007eY-2Z
	for ipv6@ietf.org; Wed, 14 Feb 2007 13:05:32 -0500
Received: from lor-maknavic3.int-evry.fr (lor-maknavic3.int-evry.fr
	[157.159.103.217])
	by smtp2.int-evry.fr (Postfix) with ESMTP id 962A02FD03;
	Wed, 14 Feb 2007 19:05:22 +0100 (CET)
From: Pars Mutaf <pars.mutaf@int-evry.fr>
To: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
In-Reply-To: <11E8CE30-40A2-41F5-9D39-BDE0AA3AB512@NLnetLabs.nl>
References: <1168423598.15925.24.camel@lor-maknavic3.int-evry.fr>
	<45AA0D9D.4080705@piuha.net><1168800701.45aa7bbdc4fdb@imp.int-evry.fr>
	<1170195757.45bfc52de120e@imp.int-evry.fr>
	<1171033115.27018.6.camel@lor-maknavic3.int-evry.fr>
	<CA7D9B4A761066448304A6AFC09ABDA9015ACFEC@XCH-NE-1V2.ne.nos.boeing.com>
	<1171191715.45cef7a3e3477@imp.int-evry.fr>
	<70C6EFCDFC8AAD418EF7063CD132D064038CFF42@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<1171287341.25622.12.camel@lor-maknavic3.int-evry.fr>
	<11E8CE30-40A2-41F5-9D39-BDE0AA3AB512@NLnetLabs.nl>
Content-Type: text/plain
Organization: INT Evry
Date: Wed, 14 Feb 2007 19:05:22 +0100
Message-Id: <1171476323.9643.31.camel@lor-maknavic3.int-evry.fr>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.1 
Content-Transfer-Encoding: 7bit
X-INT-MailScanner-Information: Please contact the ISP for more information
X-INT-MailScanner: Found to be clean
X-INT-MailScanner-MCPCheck: 
X-INT-MailScanner-SpamCheck: 
X-INT-MailScanner-From: pars.mutaf@int-evry.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 225414c974e0d6437992164e91287a51
Cc: Christian Huitema <huitema@windows.microsoft.com>, ipv6@ietf.org,
	namedroppers@ops.ietf.org
Subject: Re: Private Information Queries (was RE: better MNR or bypassing it)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: pars.mutaf@int-evry.fr
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Wed, 2007-02-14 at 16:43 +0100, Olaf M. Kolkman wrote:
> Hello Pars,
> 
> A few thoughts...
> 


Hello thanks.


> 
> On 12Feb 2007, at 2:35 PM, Pars Mutaf wrote:
> 
> >> The problems that you describe hardly seem related to server-less  
> >> name
> >> resolution in a local network!
> >
> >
> >
> > The proposed protocol could also use infrastracture DNS (i.e.
> > standard DNS). This would look as follows:
> >
> > Let us assume that Alice Collins has a personal DNS name
> > "alicecollins.domain.com". Her phone has an IP address that is
> > registered to this DNS name.
> >
> 
> So instead of having to remember Alice Collins' phone number you
have  
> to remember the domain name under which her
telephone-number-recovery- 
> services is located.



This is exact. That's why I have serious doubts about using 
infrastructure DNS and I am promoting MNR (or name-based local 
IPv6 addresses) as a general but local solution.

 
> > The requestor user enters the name Alice Collins, the proposed
> > application generates the corresponding DNS name,
> 
> How does the proposed application do that unambiguously? Given that  
> the 'Alice Collins' you are looking for might be a completely  
> different "Alice Collins" than I know.  The namespace collision will  
> be a problem that you will need to solve.
 


Right. Please see below in the context of MNR.


 
> > makes a
> > standard DNS query, and obtains the IP address. At this point the
> > proposed application can send a private information query to
> > Alice's phone. If approved by Alice (in real-time), her phone
> > number can be learned.
> >
> > This would work globally, but I don't think this is realistic.
> > (BTW, it can be noted that, one would ask why I need a phone
> > number in this case.)
> 
> Indeed, that is the argument above.
> 
> >
> > Using multicast name resolution (or, name-based IPv6 addresses)
> > with human names that have local significance only, seem
> > realistic to me. Here the term "local" may take different
> > meanings. It may be a local cellular network that covers a large
> > number of cells, or a localized mobility management domain.
> >
> > Such a local cellular zone can cover a large geographical area.
> > This is an important progress compared to using a technology
> > like Bluetooth (for exchanging private info). But the proposed
> > protocol cannot work globally. That's why we need phone numbers
> > and our goal is to allow people to share their phone numbers
> > more easily.
> 
> 
> I think the main problem will be to find a balance between size of  
> your "locality" and the amount of collisions in your namespace. That  
> will be problematic, as an illustration: Travel to Volendam (a  
> village in the Netherlands), walk down the street, and shout "Hey  
> Piet Veerman" and count the amounts of angry faces.

OK. I probably won't do that if I go to Volendam :-)



The automated approach to human name collisions can use a 
collision counter. The user enters his/her human name at 
configuration time: "Piet Veerman". The application will try to 
configure pietveerman0, and if it collides, pietveerman1, 
pietveerman2, etc. The user doesn't have to know which Piet 
Veerman he is. Note that as users move, these numbers may
change. A good implementation should always look for the smallest 
possible collision count (but without being too aggresive). 

Then if you need the phone number of a particular Piet Veerman 
in that village, what happens? 

The application tries pietveerman0, if no answer, the user
pushes on the NEXT button, it tries the next one until you 
find the searched Piet Veerman. The number of trials is left 
to the user. If you receive more than one responses, you will 
choose the right Piet Veerman, or call all of them one-by-one 
(you will say "sorry wrong number", etc). 

Another potential problem with colliding names is that for 
each wrong Piet Veerman, the requesting user will 
unneccessarily solve a challenge e.g. a CAPTCHA or other
Turing tests.

That's life. We cannot do more than that for colliding
names (may be I'm wrong). Perhaps parents can use this
application to detect collisions and avoid a colliding 
name for their baby? ;-))



> With the problem you are describing the number of angry faces if  
> relevant. If I were to activate the feature on the phone that would  
> provide me with the "Do you want to provide your phone number to  
> <foo>" and I were to receive more than 2 false positive requests for  
> my phone number, I would turn of the feature. So if I were the
target  
> group solving the name collisions will be important.



Yes. If there are many many Piet Veermans in the same area, this
application may be less efficient for these persons. May be they
should use pseudonyms.

I prefer looking at the problem the following way: this would work 
very well i.e. without or with very few collisions for many many 
users. 

The problem to me is the need for an efficient multicast name
resolution protocol (or, bypassing it ;-)

Regards,

pars



 
> --Olaf
> 
> 
> -----------------------------------------------------------
> Olaf M. Kolkman
> NLnet Labs
> http://www.nlnetlabs.nl/
> 
> 
> 


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



From ipv6-bounces@ietf.org Wed Feb 14 14:09:22 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HHPRt-0008GD-Ez; Wed, 14 Feb 2007 14:05:49 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HHPRs-0008Ev-A7
	for ipv6@ietf.org; Wed, 14 Feb 2007 14:05:48 -0500
Received: from smtp2.int-evry.fr ([157.159.10.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HHPRk-00077k-Sq
	for ipv6@ietf.org; Wed, 14 Feb 2007 14:05:48 -0500
Received: from lor-maknavic3.int-evry.fr (lor-maknavic3.int-evry.fr
	[157.159.103.217])
	by smtp2.int-evry.fr (Postfix) with ESMTP id EEFE62FDCB;
	Wed, 14 Feb 2007 20:05:35 +0100 (CET)
From: Pars Mutaf <pars.mutaf@int-evry.fr>
To: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
In-Reply-To: <1171476323.9643.31.camel@lor-maknavic3.int-evry.fr>
References: <1168423598.15925.24.camel@lor-maknavic3.int-evry.fr>
	<45AA0D9D.4080705@piuha.net><1168800701.45aa7bbdc4fdb@imp.int-evry.fr>
	<1170195757.45bfc52de120e@imp.int-evry.fr>
	<1171033115.27018.6.camel@lor-maknavic3.int-evry.fr>
	<CA7D9B4A761066448304A6AFC09ABDA9015ACFEC@XCH-NE-1V2.ne.nos.boeing.com>
	<1171191715.45cef7a3e3477@imp.int-evry.fr>
	<70C6EFCDFC8AAD418EF7063CD132D064038CFF42@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<1171287341.25622.12.camel@lor-maknavic3.int-evry.fr>
	<11E8CE30-40A2-41F5-9D39-BDE0AA3AB512@NLnetLabs.nl>
	<1171476323.9643.31.camel@lor-maknavic3.int-evry.fr>
Content-Type: text/plain
Organization: INT Evry
Date: Wed, 14 Feb 2007 20:05:36 +0100
Message-Id: <1171479936.13220.15.camel@lor-maknavic3.int-evry.fr>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.1 
Content-Transfer-Encoding: 7bit
X-INT-MailScanner-Information: Please contact the ISP for more information
X-INT-MailScanner: Found to be clean
X-INT-MailScanner-MCPCheck: 
X-INT-MailScanner-SpamCheck: 
X-INT-MailScanner-From: pars.mutaf@int-evry.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ccfb4541e989aa743998098cd315d0fd
Cc: Christian Huitema <huitema@windows.microsoft.com>,
	namedroppers@ops.ietf.org, ipv6@ietf.org
Subject: Re: Private Information Queries (was RE: better MNR or bypassing it)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: pars.mutaf@int-evry.fr
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Wed, 2007-02-14 at 19:05 +0100, Pars Mutaf wrote:
> On Wed, 2007-02-14 at 16:43 +0100, Olaf M. Kolkman wrote:
> > Hello Pars,
> > 
> > A few thoughts...
> > 
> 
> 
> Hello thanks.
> 
> 
> > 
> > On 12Feb 2007, at 2:35 PM, Pars Mutaf wrote:
> > 
> > >> The problems that you describe hardly seem related to server-less  
> > >> name
> > >> resolution in a local network!
> > >
> > >
> > >
> > > The proposed protocol could also use infrastracture DNS (i.e.
> > > standard DNS). This would look as follows:
> > >
> > > Let us assume that Alice Collins has a personal DNS name
> > > "alicecollins.domain.com". Her phone has an IP address that is
> > > registered to this DNS name.
> > >
> > 
> > So instead of having to remember Alice Collins' phone number you
> have  
> > to remember the domain name under which her
> telephone-number-recovery- 
> > services is located.
> 
> 
> 
> This is exact. That's why I have serious doubts about using 
> infrastructure DNS and I am promoting MNR (or name-based local 
> IPv6 addresses) as a general but local solution.

sorry. quick precision: 

I'm arguing that only a local solution is realistic because
users cannot possibly remember domain names (especially if there
are many of them). They can only remember "human names". In addition, 
there is no evidence that such special domains will exist.

Hence the local solution (discussed below). Within a cellular
local network, we can cover a large area and share our phone
numbers easily over long distances. This is much better than 
using Bluetooth (which requires short distance user contact). 
But I'm not pretending a global solution.

Thanks, 
pars


>  
> > > The requestor user enters the name Alice Collins, the proposed
> > > application generates the corresponding DNS name,
> > 
> > How does the proposed application do that unambiguously? Given that  
> > the 'Alice Collins' you are looking for might be a completely  
> > different "Alice Collins" than I know.  The namespace collision will  
> > be a problem that you will need to solve.
>  
> 
> 
> Right. Please see below in the context of MNR.
> 
> 
>  
> > > makes a
> > > standard DNS query, and obtains the IP address. At this point the
> > > proposed application can send a private information query to
> > > Alice's phone. If approved by Alice (in real-time), her phone
> > > number can be learned.
> > >
> > > This would work globally, but I don't think this is realistic.
> > > (BTW, it can be noted that, one would ask why I need a phone
> > > number in this case.)
> > 
> > Indeed, that is the argument above.
> > 
> > >
> > > Using multicast name resolution (or, name-based IPv6 addresses)
> > > with human names that have local significance only, seem
> > > realistic to me. Here the term "local" may take different
> > > meanings. It may be a local cellular network that covers a large
> > > number of cells, or a localized mobility management domain.
> > >
> > > Such a local cellular zone can cover a large geographical area.
> > > This is an important progress compared to using a technology
> > > like Bluetooth (for exchanging private info). But the proposed
> > > protocol cannot work globally. That's why we need phone numbers
> > > and our goal is to allow people to share their phone numbers
> > > more easily.
> > 
> > 
> > I think the main problem will be to find a balance between size of  
> > your "locality" and the amount of collisions in your namespace. That  
> > will be problematic, as an illustration: Travel to Volendam (a  
> > village in the Netherlands), walk down the street, and shout "Hey  
> > Piet Veerman" and count the amounts of angry faces.
> 
> OK. I probably won't do that if I go to Volendam :-)
> 
> 
> 
> The automated approach to human name collisions can use a 
> collision counter. The user enters his/her human name at 
> configuration time: "Piet Veerman". The application will try to 
> configure pietveerman0, and if it collides, pietveerman1, 
> pietveerman2, etc. The user doesn't have to know which Piet 
> Veerman he is. Note that as users move, these numbers may
> change. A good implementation should always look for the smallest 
> possible collision count (but without being too aggresive). 
> 
> Then if you need the phone number of a particular Piet Veerman 
> in that village, what happens? 
> 
> The application tries pietveerman0, if no answer, the user
> pushes on the NEXT button, it tries the next one until you 
> find the searched Piet Veerman. The number of trials is left 
> to the user. If you receive more than one responses, you will 
> choose the right Piet Veerman, or call all of them one-by-one 
> (you will say "sorry wrong number", etc). 
> 
> Another potential problem with colliding names is that for 
> each wrong Piet Veerman, the requesting user will 
> unneccessarily solve a challenge e.g. a CAPTCHA or other
> Turing tests.
> 
> That's life. We cannot do more than that for colliding
> names (may be I'm wrong). Perhaps parents can use this
> application to detect collisions and avoid a colliding 
> name for their baby? ;-))
> 
> 
> 
> > With the problem you are describing the number of angry faces if  
> > relevant. If I were to activate the feature on the phone that would  
> > provide me with the "Do you want to provide your phone number to  
> > <foo>" and I were to receive more than 2 false positive requests for  
> > my phone number, I would turn of the feature. So if I were the
> target  
> > group solving the name collisions will be important.
> 
> 
> 
> Yes. If there are many many Piet Veermans in the same area, this
> application may be less efficient for these persons. May be they
> should use pseudonyms.
> 
> I prefer looking at the problem the following way: this would work 
> very well i.e. without or with very few collisions for many many 
> users. 
> 
> The problem to me is the need for an efficient multicast name
> resolution protocol (or, bypassing it ;-)
> 
> Regards,
> 
> pars
> 
> 
> 
>  
> > --Olaf
> > 
> > 
> > -----------------------------------------------------------
> > Olaf M. Kolkman
> > NLnet Labs
> > http://www.nlnetlabs.nl/
> > 
> > 
> > 
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


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



From ipv6-bounces@ietf.org Wed Feb 14 17:26:05 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HHSVI-0003gQ-Jw; Wed, 14 Feb 2007 17:21:32 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HHSVG-0003e9-2H
	for ipv6@ietf.org; Wed, 14 Feb 2007 17:21:30 -0500
Received: from stl-smtpout-01.boeing.com ([130.76.96.56]
	helo=stl-smtpout-01.ns.cs.boeing.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HHSVC-00056X-Ne
	for ipv6@ietf.org; Wed, 14 Feb 2007 17:21:30 -0500
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4])
	by stl-smtpout-01.ns.cs.boeing.com (8.13.6/8.13.6/TEST_SMTPIN) with
	ESMTP id l1EMLNPv001916
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 14 Feb 2007 16:21:23 -0600 (CST)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1])
	by slb-av-01.boeing.com (8.13.6/8.13.6/DOWNSTREAM_RELAY) with ESMTP id
	l1EMLMvq000632; Wed, 14 Feb 2007 14:21:22 -0800 (PST)
Received: from XCH-NEBH-11.ne.nos.boeing.com (xch-nebh-11.ne.nos.boeing.com
	[128.225.80.27])
	by slb-av-01.boeing.com (8.13.6/8.13.6/UPSTREAM_RELAY) with ESMTP id
	l1EMLLxi000604; Wed, 14 Feb 2007 14:21:22 -0800 (PST)
Received: from XCH-NE-1V2.ne.nos.boeing.com ([128.225.80.43]) by
	XCH-NEBH-11.ne.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 14 Feb 2007 17:21:21 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 14 Feb 2007 17:21:21 -0500
Message-ID: <CA7D9B4A761066448304A6AFC09ABDA9015AD005@XCH-NE-1V2.ne.nos.boeing.com>
In-Reply-To: <1171479936.13220.15.camel@lor-maknavic3.int-evry.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Private Information Queries (was RE: better MNR or bypassing it)
Thread-Index: AcdQa3Lfb+UxG4MNTmi0MfYPPx1YJQAGWekg
References: <1168423598.15925.24.camel@lor-maknavic3.int-evry.fr><45AA0D9D.4080705@piuha.net><1168800701.45aa7bbdc4fdb@imp.int-evry.fr><1170195757.45bfc52de120e@imp.int-evry.fr><1171033115.27018.6.camel@lor-maknavic3.int-evry.fr><CA7D9B4A761066448304A6AFC09ABDA9015ACFEC@XCH-NE-1V2.ne.nos.boeing.com><1171191715.45cef7a3e3477@imp.int-evry.fr><70C6EFCDFC8AAD418EF7063CD132D064038CFF42@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><1171287341.25622.12.camel@lor-maknavic3.int-evry.fr><11E8CE30-40A2-41F5-9D39-BDE0AA3AB512@NLnetLabs.nl><1171476323.9643.31.camel@lor-maknavic3.int-evry.fr>
	<1171479936.13220.15.camel@lor-maknavic3.int-evry.fr>
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: <pars.mutaf@int-evry.fr>
X-OriginalArrivalTime: 14 Feb 2007 22:21:21.0584 (UTC)
	FILETIME=[74A02300:01C75086]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: namedroppers@ops.ietf.org, ipv6@ietf.org
Subject: RE: Private Information Queries (was RE: better MNR or bypassing it)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> -----Original Message-----
> From: Pars Mutaf [mailto:pars.mutaf@int-evry.fr]=20

> I'm arguing that only a local solution is realistic because
> users cannot possibly remember domain names (especially if there
> are many of them). They can only remember "human names". In addition,=20
> there is no evidence that such special domains will exist.
>=20
> Hence the local solution (discussed below). Within a cellular
> local network, we can cover a large area and share our phone
> numbers easily over long distances. This is much better than=20
> using Bluetooth (which requires short distance user contact).=20
> But I'm not pretending a global solution.

Pars, I'm not sure why a local-only solution is very helpful. The guy
across the room at a conference may well have a cell number from a
different country. If that case isn't included in this solution, I'm not
sure how attractive it is.

In any case, what makes this any different from people's e-mail address
book? E-mail addresses are global, and I guess most people do not keep
them in their heads either. They use address books, which are hopefully
backed up somewhere. Same goes for web sites in the favorites or
bookmarks folder. Easier with DNS than using IP addresses, but still not
easy enough.

I think the name collision issue is what makes these proposals
difficult.

Bert

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



From ipv6-bounces@ietf.org Thu Feb 15 05:08:02 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HHdS2-0003o1-Mj; Thu, 15 Feb 2007 05:02:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HHdS0-0003mr-LF
	for ipv6@ietf.org; Thu, 15 Feb 2007 05:02:52 -0500
Received: from smtp2.int-evry.fr ([157.159.10.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HHdRz-0008BU-8g
	for ipv6@ietf.org; Thu, 15 Feb 2007 05:02:52 -0500
Received: from lor-maknavic3.int-evry.fr (lor-maknavic3.int-evry.fr
	[157.159.103.217])
	by smtp2.int-evry.fr (Postfix) with ESMTP id 2809B2FFA0;
	Thu, 15 Feb 2007 11:02:36 +0100 (CET)
From: Pars Mutaf <pars.mutaf@int-evry.fr>
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
In-Reply-To: <CA7D9B4A761066448304A6AFC09ABDA9015AD005@XCH-NE-1V2.ne.nos.boeing.com>
References: <1168423598.15925.24.camel@lor-maknavic3.int-evry.fr>
	<45AA0D9D.4080705@piuha.net><1168800701.45aa7bbdc4fdb@imp.int-evry.fr>
	<1170195757.45bfc52de120e@imp.int-evry.fr>
	<1171033115.27018.6.camel@lor-maknavic3.int-evry.fr>
	<CA7D9B4A761066448304A6AFC09ABDA9015ACFEC@XCH-NE-1V2.ne.nos.boeing.com>
	<1171191715.45cef7a3e3477@imp.int-evry.fr>
	<70C6EFCDFC8AAD418EF7063CD132D064038CFF42@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<1171287341.25622.12.camel@lor-maknavic3.int-evry.fr>
	<11E8CE30-40A2-41F5-9D39-BDE0AA3AB512@NLnetLabs.nl>
	<1171476323.9643.31.camel@lor-maknavic3.int-evry.fr>
	<1171479936.13220.15.camel@lor-maknavic3.int-evry.fr>
	<CA7D9B4A761066448304A6AFC09ABDA9015AD005@XCH-NE-1V2.ne.nos.boeing.com>
Content-Type: text/plain
Organization: INT Evry
Date: Thu, 15 Feb 2007 11:02:36 +0100
Message-Id: <1171533756.4759.20.camel@lor-maknavic3.int-evry.fr>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.1 
Content-Transfer-Encoding: 7bit
X-INT-MailScanner-Information: Please contact the ISP for more information
X-INT-MailScanner: Found to be clean
X-INT-MailScanner-MCPCheck: 
X-INT-MailScanner-SpamCheck: 
X-INT-MailScanner-From: pars.mutaf@int-evry.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: namedroppers@ops.ietf.org, ipv6@ietf.org
Subject: RE: Private Information Queries (was RE: better MNR or bypassing it)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: pars.mutaf@int-evry.fr
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Wed, 2007-02-14 at 17:21 -0500, Manfredi, Albert E wrote:
> -----Original Message-----
> > From: Pars Mutaf [mailto:pars.mutaf@int-evry.fr] 
> 
> > I'm arguing that only a local solution is realistic because
> > users cannot possibly remember domain names (especially if there
> > are many of them). They can only remember "human names". In 
> > addition, there is no evidence that such special domains will exist.
> > 
> > Hence the local solution (discussed below). Within a cellular
> > local network, we can cover a large area and share our phone
> > numbers easily over long distances. This is much better than 
> > using Bluetooth (which requires short distance user contact). 
> > But I'm not pretending a global solution.
> 
> Pars, I'm not sure why a local-only solution is very helpful. The guy
> across the room at a conference may well have a cell number from a
> different country. If that case isn't included in this solution, I'm 
> not sure how attractive it is.


Hi Bert, 

Conference room is a too old an uninteresting example.

This is very attractive in the cellular context. For example, you 
buy a new phone, you are impatient to call someone you know (who 
lives in the area). But you don't have the phone number yet. You 
can even call that person for asking another person's phone number
(who is not here).

You don't think about all these possibilities today, simply 
because you assume that you cannot do it.


> In any case, what makes this any different from people's e-mail 
> address
> book? E-mail addresses are global, and I guess most people do not keep
> them in their heads either. They use address books, which are 
> hopefully
> backed up somewhere. Same goes for web sites in the favorites or
> bookmarks folder. Easier with DNS than using IP addresses, but still 
> not easy enough.


I'm not sure if you see the context I'm talking about. 

 
> I think the name collision issue is what makes these proposals
> difficult.


OK may be I'll stop talking as if I invented multicast DNS. 
Collisions are not my problem. I don't think they are a technical
problem. 

You are looking for John Smith, the phone will scan all John Smiths
in the local cellular network, and you will receive 'n' results. (My
proposal comes into play only after that.) 

If John Smith is a too much colliding name, this is John Smith's
problem. We cannot penalize many other users for that.

Are you arguing that this protocol is impossible and cellular 
users will never be able to do that?

Thanks,
pars



> 
> Bert





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



From ipv6-bounces@ietf.org Thu Feb 15 10:28:37 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HHiTc-0005Fu-3d; Thu, 15 Feb 2007 10:24:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HHazS-0006SU-2a; Thu, 15 Feb 2007 02:25:14 -0500
Received: from borg.juniper.net ([207.17.137.119])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HHamG-0000Hx-UP; Thu, 15 Feb 2007 02:11:38 -0500
Received: from unknown (HELO beta.jnpr.net) ([172.24.18.109])
	by borg.juniper.net with ESMTP; 14 Feb 2007 23:11:37 -0800
X-IronPort-AV: i="4.14,173,1170662400"; 
	d="txt'?scan'208"; a="675693147:sNHT93270032"
Received: from [172.27.8.108] ([172.27.8.108]) by beta.jnpr.net over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 14 Feb 2007 23:11:33 -0800
Message-ID: <45D4079D.7080801@juniper.net>
Date: Thu, 15 Feb 2007 15:11:25 +0800
From: Mark Williams <miw@juniper.net>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: int-area@ietf.org,  routing-discussion@ietf.org,  ipv6@ietf.org, 
	sava@nrc.tsinghua.edu.cn, Geoff Huston <gih@apnic.net>, 
	David Ward <dward@cisco.com>
Content-Type: multipart/mixed; boundary="------------010209050300040109070808"
X-OriginalArrivalTime: 15 Feb 2007 07:11:33.0365 (UTC)
	FILETIME=[85ECB250:01C750D0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2af167865907217f0b49c659e31a77f7
X-Mailman-Approved-At: Thu, 15 Feb 2007 10:24:50 -0500
Cc: Lixia Zhang <lixia@CS.UCLA.EDU>, Ronald Bonica <rbonica@juniper.net>,
	Ross Callon <rcallon@juniper.net>, fanye@us.ibm.com
Subject: Further Call for Interest and Participation: Source Address
 Validation Architecture (SAVA)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: miw@juniper.net
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

This is a multi-part message in MIME format.
--------------010209050300040109070808
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

All,

We are again calling for interest and participation in a project to 
devise a
framework architecture and solutions to the problem of validation of
source addresses in IPv6 networks in order to protect network
infrastructure from address spoofing attacks.

This will be the topic of a BoF session at IETF 67 in Prague.

(Also, if you will be in Bali for the Apricot 2007 see invitation for an 
open interim meeting below.)

Attached, please find the draft problem statement:
draft-wu-sava-problem-statement-00.txt

Further drafts proposing a possible framework and a strawman solution 
design can be found on the ID Website:
http://www.ietf.org/internet-drafts/draft-wu-sava-framework-00.txt
http://www.ietf.org/internet-drafts/draft-wu-sava-solution-e2e-ipv6-00.txt

The effort is based on the current situation that it would seem that, at
least as things currently stand, it is unlikely that spoofed source
addresses will be able to be excluded from the Internet backbones unless
some further solutions and practices are put into place.

The SAVA effort has roots in research and development to that end for
IPv6 networks currently being undertaken at Tsinghua University in
Beijing. A number of papers have been published and code has been
written, which is currently under test on the CERNET-II backbone.
We seek the participation and assistance of the wider Internet community in
order to create a framework of practices and solutions which will be
deployable on a much wider basis.

A document repository for drafts and other documents is available at:
http://narl.tsinghua.edu.cn/sava/

An interim mailing list
sava@nrc.tsinghua.edu.cn <mailto:sava@nrc.tsinghua.edu.cn>
has been created and can be joined by going to:
http://www.nrc.tsinghua.edu.cn/mailman/listinfo/sava
an archive is also available at the same address.

In addition, for those who may be attending the APRICOT 2007 conference 
in Bali, there will be an OPEN INTERIM MEETING for all interested 
parties held in Bali just before the main conference track starts.
DATE: 27-Feb-2007
Time: 0900-1200 (i.e. before conference proper starts)
Venue: Sheraton Laguna Resort, Nusa Dua, Bali  (hotel right next to the 
conference hotel)
Please email me if you think you might attend and I'll make sure you are 
kept up to date with
any changes and documents, etc.

cheers,

Mark

-----------------------------------------------------------------
Mark Williams                        Juniper Networks
Liaison                              Beijing Office
Academic Networking Sector           Tel: +86 10 6528 8800 x16032
Asia Pacific                         FAX: +61 7 3251 0155
miw@juniper.net                      Cell: +86 1370-111-4749


--------------010209050300040109070808
Content-Type: text/plain;
 name="draft-wu-sava-problem-statement.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="draft-wu-sava-problem-statement.txt"




Network Working Group                                              J. Wu
Internet-Draft                                                    CERNET
Intended status: Experimental                                  R. Bonica
Expires: August 18, 2007                                Juniper Networks
                                                                   J. Bi
                                                                   X. Li
                                                                  G. Ren
                                                                  CERNET
                                                           M I. Williams
                                                        Juniper Networks
                                                       February 14, 2007


        Source Address Validation Architecture Problem Statement
                    draft-sava-problem-statement-00

Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on August 18, 2007.

Copyright Notice

   Copyright (C) The IETF Trust (2007).

Abstract

   This document outlines the problems for the Source Address



Wu, et al.               Expires August 18, 2007                [Page 1]

Internet-Draft           SAVA Problem Statement            February 2007


   Verification Architecture (SAVA) initiative to solve.  It examines
   the current state in the internet, looks at current best practices
   and discusses why the current approach is unlikely to ever solve the
   problem of IP address spoofing.  It also discusses some of the
   problems that SAVA should NOT attempt to solve.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Current State of Affairs  . . . . . . . . . . . . . . . . . . . 3
   3.  Best Current Practices  . . . . . . . . . . . . . . . . . . . . 4
   4.  Deficiencies of Ingress-Filter (BCP0038) and uRPF Approach  . . 4
   5.  Why IPSEC is not the Solution to This Problem . . . . . . . . . 5
   6.  Framework Requirements  . . . . . . . . . . . . . . . . . . . . 5
     6.1.  Direct Benefit to Deployers . . . . . . . . . . . . . . . . 5
     6.2.  Solution Focus on IPv6  . . . . . . . . . . . . . . . . . . 5
     6.3.  Performance . . . . . . . . . . . . . . . . . . . . . . . . 5
     6.4.  Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . 6
     6.5.  Multiple-Fence Solution . . . . . . . . . . . . . . . . . . 6
     6.6.  Incrementally Deployable  . . . . . . . . . . . . . . . . . 6
     6.7.  Loose Coupling  . . . . . . . . . . . . . . . . . . . . . . 6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
   8.  Security Considerations . . . . . . . . . . . . . . . . . . . . 6
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 6
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . . . 7
     10.1. Normative References  . . . . . . . . . . . . . . . . . . . 7
     10.2. Informative References  . . . . . . . . . . . . . . . . . . 7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 7
   Intellectual Property and Copyright Statements  . . . . . . . . . . 9















Wu, et al.               Expires August 18, 2007                [Page 2]

Internet-Draft           SAVA Problem Statement            February 2007


1.  Introduction

   The Internet is a decentralized system which basically provides best
   effort, packet-based data forwarding service.  In the forwarding
   process, the device (router, switch, gateway, etc.) forwards IP
   packets based on the destination IP address.  In most cases, the
   source IP address is not checked.  The lack of source IP address
   checking makes it easy for the attackers to spoof the source address.
   And it has facilitated many existing attacks in the Internet.

   In recent years, there have been some efforts in the research
   community to design mechanisms on fighting against source address
   spoofing.  We think it is now a suitable time to summarize the
   progress and to standardize some results of research efforts to
   protocols, to enhance the authenticity of the source address.
   Providing authentic IP address is not only helpful to network
   security, but also helpful to some other aspects, e.g., network
   application, network management and accounting, etc.

   The motivation of this document is to clarify the problem in solving
   the spoofing of source address.  The general problem of supporting
   authenticity of source address in the Internet is divided into three
   seperated sub-problems, refered as "inter-AS AIAA problem", "intra-AS
   SAVA problem" and "access network SAVA problem".  The primary
   difference between these three problems is the different level and
   scope in network topology.  The "inter-AS SAVA problem" considers the
   source address spoofing involved with more than one ASes.  The
   "inter-AS SAVA problem" considers the source address spoofing inside
   one AS.  The "access network SAVA problem" considers the source
   address spoofing inside one access network.  There may be multiple
   candidate solutions for each sub-problem.

   Because the current Internet addressing architecture does not verify
   the source address of the packets received and forwarded, has been
   formed for many years, it is difficult and not cost-effective to
   change from the current Internet infrastructure.  The development of
   the IPv6 based next generation Internet will give us the opportunity
   to implement an authentic addressing architecture.  In this memo,
   only the issues in IPv6 network are discussed.


2.  Current State of Affairs

   In the MIT Spoofer Project [Bev05], the authors found that
   approximately one-quarter of the observed addresses, netblocks and
   autonomous systems (AS) permit full or partial spoofing.  And they
   suggested that a large portion of the Internet is vulnerable to
   spoofing and concerted attacks employing spoofing remain a serious



Wu, et al.               Expires August 18, 2007                [Page 3]

Internet-Draft           SAVA Problem Statement            February 2007


   concern.


3.  Best Current Practices

   The current method of avoiding packets with spoofed source addresses
   entering and being propagated on the Internet relies on two methods:

   1.  Ingress Filtering as per BCP0038 [RFC2827].  This method requires
       ISPs and organisations at the edge to apply filters limiting the
       source addresses allowed on incoming packets to those
       specifically allowed in the stub networks.  If BCP0038 were
       followed at all ingress points to the Internet, then there would
       be no spoofed packets on the Internet.

   2.  Unicast Reverse Path Forwarding (uRPF) filtering.  This is a
       feature available on routers that can be used to block incoming
       packets if, in the case a packet were constructed with the
       incoming packet's source address as its destination address, the
       constructed packet would NOT be routed back along the ingress
       link for the incoming packet.  Assuming random incidence of
       spoofed packets and symmetric routing, a router with n links and
       with uRPF configured would drop (n-1)/n of all incoming spoofed
       packets, greatly mitigating DoS attacks using spoofed packets,
       for example (See [RFC3871]).


4.  Deficiencies of Ingress-Filter (BCP0038) and uRPF Approach

   Ingress filtering is definitely to be recommended, and uRPF filtering
   certainly does have its uses, but, at least in the current state of
   the Internet, they are insufficient as a protection of the routing
   infrastructure.

   1.  Ingress filtering works, but it only works if all, or at least
       the vast majority of ingress points apply ingress filtering.  As
       can be seen in the Internet today, even when 25% of the Internet
       is unsecured, those elements that want access to "spoofable"
       connections simply move their connection to unsecured attachment
       points.

   2.  uRPF does not work well in places where assymetric routing
       happens.  This constitutes a large part of the Internet








Wu, et al.               Expires August 18, 2007                [Page 4]

Internet-Draft           SAVA Problem Statement            February 2007


5.  Why IPSEC is not the Solution to This Problem

   IPSEC is a solution to many problems, and it is not the intention of
   the authors to suggest that it should not be deployed.  It is just
   not the solution to this particular problem.

   Whereas IPSEC solves end-end security problems and allows endpoints
   in a connection to verify the identity of connected endpoints, there
   is also a need for the infrastructure of the Internet to be able to
   protect itself.  Many attacks employ spoofed IP addresses to either
   conceal the source of an infrastructure attack or to cause the
   network infrastructure to, in effect, attack itself.

   The network must be able to secure itself from poorly-secured
   endpoints.  The goal of the solution to the problem must be to
   discard spoofed traffic as close to the source of the attack as
   possible. (i.e. within the infrastructure rather than at the other
   endpoint(s).


6.  Framework Requirements

   Following is a list of key requirements for any solution/s to the
   problem described above.  They will be more completely delineated in
   the proposed workgroup charter and the framework document.

6.1.  Direct Benefit to Deployers

   One of the reasons for the less-than-adequate deployment of ingress
   filters is that, in deploying the filters, a network operator or
   attached private network is mostly protecting the rest of the
   Internet rather than itself.  It should be a design goal for any
   solution to give those that deploy the solution some increased level
   of protection from spoofed attacks from outside of their own
   adminitrative domain.

6.2.  Solution Focus on IPv6

   While it is not the intent to develop solutions that cannot be
   deployed on an IPv4 network, the focus of the work should be on
   solutions for IPv6 networks.  In other words, if a solution is
   feasible for IPv6 deployment, but infeasible for IPv4 deployment,
   that shall not be construed as a disadvantage for the solution.

6.3.  Performance

   Deployment of SAVA solutions should not place unreasonable stress on
   network infrastructure components.



Wu, et al.               Expires August 18, 2007                [Page 5]

Internet-Draft           SAVA Problem Statement            February 2007


6.4.  Scaling

   SAVA solutions should be feasible for network sizes and no-default
   prefix tables many times the size experienced today.  SAVA solutions
   should scale in a way that is at worst linear with the size of the
   Internet.

6.5.  Multiple-Fence Solution

   Ingress filtering is a single fence solution, in that it is only
   applicable only at the access network or at the boundary between an
   attached private network and a network provider.  Where the attached
   network is not a stub, it cannot be deployed effectively.  It should
   be the goal of the SAVA working group to provide solutions that can
   be deployed at the boundaries between ISPs or on intra-ISP links as
   well.

6.6.  Incrementally Deployable

   It must be possible to deploy SAVA solutions incrementally across the
   network.  In other words, there can be no "flag day".

6.7.  Loose Coupling

   Components of the overall solution should be able to be deployed in a
   "mix and match" fashion. this allows for multiple solutions for a
   given component of the overall solution.


7.  IANA Considerations

   This document makes no request of IANA.

   Note to RFC Editor: this section may be removed on publication as an
   RFC.


8.  Security Considerations

   For this document, no specific security considerations.  Many of the
   solution elements will need to be examined carefully for robustness
   and to see if they do not in themselves introduce security problems.


9.  Acknowledgements


10.  References



Wu, et al.               Expires August 18, 2007                [Page 6]

Internet-Draft           SAVA Problem Statement            February 2007


10.1.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

10.2.  Informative References

   [Bev05]    Beverley, S. and S. Bauer, ""The spoofer project:
              inferring the extent of source address filtering on the
              Internet", USENIX SRUTI 2005", 2007.

   [RFC2827]  Ferguson, P. and D. Senie, "Network Ingress Filtering:
              Defeating Denial of Service Attacks which employ IP Source
              Address Spoofing", BCP 38, RFC 2827, May 2000.

   [RFC3871]  Jones, G., "Operational Security Requirements for Large
              Internet Service Provider (ISP) IP Network
              Infrastructure", RFC 3871, September 2004.


Authors' Addresses

   Jianping Wu
   CERNET
   Network Center, Tsinghua University
   Beijing  100084
   China

   Email: jianping@cernet.edu.cn


   Ronald P. Bonica
   Juniper Networks
   2251 Corporate Park Drive
   Herndon, VA  20171
   USA


   Jun Bi
   CERNET
   Network Center, Tsinghua University
   Beijing  100084
   China

   Email: junbi@cernet.edu.cn






Wu, et al.               Expires August 18, 2007                [Page 7]

Internet-Draft           SAVA Problem Statement            February 2007


   Xing Li
   CERNET
   Network Center, Tsinghua University
   Beijing  100084
   China

   Email: xing@cernet.edu.cn


   Gang Ren
   CERNET
   Network Center, Tsinghua University
   Beijing  100084
   China

   Email: rg03@mails.tsinghua.edu.cn


   Mark I. Williams
   Juniper Networks
   Suite 1508, W3 Tower, Oriental Plaza, 1 East Chang'An Ave
   Dong Cheng District, Beijing  100738
   China

   Email: miw@juniper.net


























Wu, et al.               Expires August 18, 2007                [Page 8]

Internet-Draft           SAVA Problem Statement            February 2007


Full Copyright Statement

   Copyright (C) The IETF Trust (2007).

   This document is subject to the rights, licenses and restrictions
   contained in BCP 78, and except as set forth therein, the authors
   retain all their rights.

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
   THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
   OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
   THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.


Acknowledgment

   Funding for the RFC Editor function is provided by the IETF
   Administrative Support Activity (IASA).





Wu, et al.               Expires August 18, 2007                [Page 9]



--------------010209050300040109070808
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--------------010209050300040109070808--




From ipv6-bounces@ietf.org Fri Feb 16 11:36:31 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HI5zm-00060J-FQ; Fri, 16 Feb 2007 11:31:38 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HI08b-0003IF-9f; Fri, 16 Feb 2007 05:16:21 -0500
Received: from kremlin.juniper.net ([207.17.137.120])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HI08Z-0000KL-9h; Fri, 16 Feb 2007 05:16:21 -0500
Received: from unknown (HELO beta.jnpr.net) ([172.24.18.109])
	by kremlin.juniper.net with ESMTP; 16 Feb 2007 02:16:19 -0800
X-IronPort-AV: i="4.14,180,1170662400"; 
	d="scan'208"; a="657343009:sNHT81934224"
Received: from [172.27.8.109] ([172.27.8.109]) by beta.jnpr.net over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 16 Feb 2007 02:16:16 -0800
Message-ID: <45D5846B.5090102@juniper.net>
Date: Fri, 16 Feb 2007 18:16:11 +0800
From: Mark Williams <miw@juniper.net>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: int-area@ietf.org,  routing-discussion@ietf.org,  ipv6@ietf.org, 
	sava@nrc.tsinghua.edu.cn
References: <45D4079D.7080801@juniper.net>
In-Reply-To: <45D4079D.7080801@juniper.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 16 Feb 2007 10:16:16.0777 (UTC)
	FILETIME=[7E90E790:01C751B3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 47f87af9e1d92eac54caf69b67f82b72
X-Mailman-Approved-At: Fri, 16 Feb 2007 11:31:37 -0500
Cc: Lixia Zhang <lixia@CS.UCLA.EDU>, Ronald Bonica <rbonica@juniper.net>,
	Jun Bi <junbi@tsinghua.edu.cn>,
	Ross Callon <rcallon@juniper.net>, fanye@us.ibm.com,
	Geoff Huston <gih@apnic.net>
Subject: Re: Further Call for Interest and Participation: Source Address
 Validation Architecture (SAVA)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: miw@juniper.net
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

All,

in response to some concerns about the clash between the meeting in Bali 
with the APRICOT future of Routing Workshop, we have changed the time 
for the Bali Interim meeting. I am assured the 2 locations are within 5 
minutes of each other.

New Details:

DATE: 27-Feb-2007
Time: 1245-1545  (working lunch will be supplied.)
Venue: Sheraton Laguna Resort, Nusa Dua, Bali  (hotel right next to the
conference hotel)
Please email me if you think you might attend and I'll make sure you are
kept up to date with any changes and documents, etc.

cheers,

Mark

Mark Williams wrote:
>
> All,
>
> We are again calling for interest and participation in a project to
> devise a
> framework architecture and solutions to the problem of validation of
> source addresses in IPv6 networks in order to protect network
> infrastructure from address spoofing attacks.
>
> This will be the topic of a BoF session at IETF 67 in Prague.
>
> (Also, if you will be in Bali for the Apricot 2007 see invitation for an
> open interim meeting below.)
>
> Attached, please find the draft problem statement:
> draft-wu-sava-problem-statement-00.txt
>
> Further drafts proposing a possible framework and a strawman solution
> design can be found on the ID Website:
> http://www.ietf.org/internet-drafts/draft-wu-sava-framework-00.txt
> http://www.ietf.org/internet-drafts/draft-wu-sava-solution-e2e-ipv6-00.txt
>
> The effort is based on the current situation that it would seem that, at
> least as things currently stand, it is unlikely that spoofed source
> addresses will be able to be excluded from the Internet backbones unless
> some further solutions and practices are put into place.
>
> The SAVA effort has roots in research and development to that end for
> IPv6 networks currently being undertaken at Tsinghua University in
> Beijing. A number of papers have been published and code has been
> written, which is currently under test on the CERNET-II backbone.
> We seek the participation and assistance of the wider Internet 
> community in
> order to create a framework of practices and solutions which will be
> deployable on a much wider basis.
>
> A document repository for drafts and other documents is available at:
> http://narl.tsinghua.edu.cn/sava/
>
> An interim mailing list
> sava@nrc.tsinghua.edu.cn <mailto:sava@nrc.tsinghua.edu.cn>
> has been created and can be joined by going to:
> http://www.nrc.tsinghua.edu.cn/mailman/listinfo/sava
> an archive is also available at the same address.
>
> In addition, for those who may be attending the APRICOT 2007 conference
> in Bali, there will be an OPEN INTERIM MEETING for all interested
> parties held in Bali just before the main conference track starts.
> DATE: 27-Feb-2007
> Time: 0900-1200 (i.e. before conference proper starts)
> Venue: Sheraton Laguna Resort, Nusa Dua, Bali  (hotel right next to the
> conference hotel)
> Please email me if you think you might attend and I'll make sure you are
> kept up to date with
> any changes and documents, etc.
>
> cheers,
>
> Mark
>
> -----------------------------------------------------------------
> Mark Williams                        Juniper Networks
> Liaison                              Beijing Office
> Academic Networking Sector           Tel: +86 10 6528 8800 x16032
> Asia Pacific                         FAX: +61 7 3251 0155
> miw@juniper.net                      Cell: +86 1370-111-4749
>
> ------------------------------------------------------------------------
>
>
>
>
> Network Working Group                                              J. Wu
> Internet-Draft                                                    CERNET
> Intended status: Experimental                                  R. Bonica
> Expires: August 18, 2007                                Juniper Networks
>                                                                    J. Bi
>                                                                    X. Li
>                                                                   G. Ren
>                                                                   CERNET
>                                                            M I. Williams
>                                                         Juniper Networks
>                                                        February 14, 2007
>
>
>         Source Address Validation Architecture Problem Statement
>                     draft-sava-problem-statement-00
>
> Status of this Memo
>
>    By submitting this Internet-Draft, each author represents that any
>    applicable patent or other IPR claims of which he or she is aware
>    have been or will be disclosed, and any of which he or she becomes
>    aware will be disclosed, in accordance with Section 6 of BCP 79.
>
>    Internet-Drafts are working documents of the Internet Engineering
>    Task Force (IETF), its areas, and its working groups.  Note that
>    other groups may also distribute working documents as Internet-
>    Drafts.
>
>    Internet-Drafts are draft documents valid for a maximum of six months
>    and may be updated, replaced, or obsoleted by other documents at any
>    time.  It is inappropriate to use Internet-Drafts as reference
>    material or to cite them other than as "work in progress."
>
>    The list of current Internet-Drafts can be accessed at
>    http://www.ietf.org/ietf/1id-abstracts.txt.
>
>    The list of Internet-Draft Shadow Directories can be accessed at
>    http://www.ietf.org/shadow.html.
>
>    This Internet-Draft will expire on August 18, 2007.
>
> Copyright Notice
>
>    Copyright (C) The IETF Trust (2007).
>
> Abstract
>
>    This document outlines the problems for the Source Address
>
>
>
> Wu, et al.               Expires August 18, 2007                [Page 1]
> 
> Internet-Draft           SAVA Problem Statement            February 2007
>
>
>    Verification Architecture (SAVA) initiative to solve.  It examines
>    the current state in the internet, looks at current best practices
>    and discusses why the current approach is unlikely to ever solve the
>    problem of IP address spoofing.  It also discusses some of the
>    problems that SAVA should NOT attempt to solve.
>
> Requirements Language
>
>    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
>    document are to be interpreted as described in RFC 2119 [RFC2119].
>
>
> Table of Contents
>
>    1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
>    2.  Current State of Affairs  . . . . . . . . . . . . . . . . . . . 3
>    3.  Best Current Practices  . . . . . . . . . . . . . . . . . . . . 4
>    4.  Deficiencies of Ingress-Filter (BCP0038) and uRPF Approach  . . 4
>    5.  Why IPSEC is not the Solution to This Problem . . . . . . . . . 5
>    6.  Framework Requirements  . . . . . . . . . . . . . . . . . . . . 5
>      6.1.  Direct Benefit to Deployers . . . . . . . . . . . . . . . . 5
>      6.2.  Solution Focus on IPv6  . . . . . . . . . . . . . . . . . . 5
>      6.3.  Performance . . . . . . . . . . . . . . . . . . . . . . . . 5
>      6.4.  Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . 6
>      6.5.  Multiple-Fence Solution . . . . . . . . . . . . . . . . . . 6
>      6.6.  Incrementally Deployable  . . . . . . . . . . . . . . . . . 6
>      6.7.  Loose Coupling  . . . . . . . . . . . . . . . . . . . . . . 6
>    7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
>    8.  Security Considerations . . . . . . . . . . . . . . . . . . . . 6
>    9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 6
>    10. References  . . . . . . . . . . . . . . . . . . . . . . . . . . 7
>      10.1. Normative References  . . . . . . . . . . . . . . . . . . . 7
>      10.2. Informative References  . . . . . . . . . . . . . . . . . . 7
>    Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 7
>    Intellectual Property and Copyright Statements  . . . . . . . . . . 9
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Wu, et al.               Expires August 18, 2007                [Page 2]
> 
> Internet-Draft           SAVA Problem Statement            February 2007
>
>
> 1.  Introduction
>
>    The Internet is a decentralized system which basically provides best
>    effort, packet-based data forwarding service.  In the forwarding
>    process, the device (router, switch, gateway, etc.) forwards IP
>    packets based on the destination IP address.  In most cases, the
>    source IP address is not checked.  The lack of source IP address
>    checking makes it easy for the attackers to spoof the source address.
>    And it has facilitated many existing attacks in the Internet.
>
>    In recent years, there have been some efforts in the research
>    community to design mechanisms on fighting against source address
>    spoofing.  We think it is now a suitable time to summarize the
>    progress and to standardize some results of research efforts to
>    protocols, to enhance the authenticity of the source address.
>    Providing authentic IP address is not only helpful to network
>    security, but also helpful to some other aspects, e.g., network
>    application, network management and accounting, etc.
>
>    The motivation of this document is to clarify the problem in solving
>    the spoofing of source address.  The general problem of supporting
>    authenticity of source address in the Internet is divided into three
>    seperated sub-problems, refered as "inter-AS AIAA problem", "intra-AS
>    SAVA problem" and "access network SAVA problem".  The primary
>    difference between these three problems is the different level and
>    scope in network topology.  The "inter-AS SAVA problem" considers the
>    source address spoofing involved with more than one ASes.  The
>    "inter-AS SAVA problem" considers the source address spoofing inside
>    one AS.  The "access network SAVA problem" considers the source
>    address spoofing inside one access network.  There may be multiple
>    candidate solutions for each sub-problem.
>
>    Because the current Internet addressing architecture does not verify
>    the source address of the packets received and forwarded, has been
>    formed for many years, it is difficult and not cost-effective to
>    change from the current Internet infrastructure.  The development of
>    the IPv6 based next generation Internet will give us the opportunity
>    to implement an authentic addressing architecture.  In this memo,
>    only the issues in IPv6 network are discussed.
>
>
> 2.  Current State of Affairs
>
>    In the MIT Spoofer Project [Bev05], the authors found that
>    approximately one-quarter of the observed addresses, netblocks and
>    autonomous systems (AS) permit full or partial spoofing.  And they
>    suggested that a large portion of the Internet is vulnerable to
>    spoofing and concerted attacks employing spoofing remain a serious
>
>
>
> Wu, et al.               Expires August 18, 2007                [Page 3]
> 
> Internet-Draft           SAVA Problem Statement            February 2007
>
>
>    concern.
>
>
> 3.  Best Current Practices
>
>    The current method of avoiding packets with spoofed source addresses
>    entering and being propagated on the Internet relies on two methods:
>
>    1.  Ingress Filtering as per BCP0038 [RFC2827].  This method requires
>        ISPs and organisations at the edge to apply filters limiting the
>        source addresses allowed on incoming packets to those
>        specifically allowed in the stub networks.  If BCP0038 were
>        followed at all ingress points to the Internet, then there would
>        be no spoofed packets on the Internet.
>
>    2.  Unicast Reverse Path Forwarding (uRPF) filtering.  This is a
>        feature available on routers that can be used to block incoming
>        packets if, in the case a packet were constructed with the
>        incoming packet's source address as its destination address, the
>        constructed packet would NOT be routed back along the ingress
>        link for the incoming packet.  Assuming random incidence of
>        spoofed packets and symmetric routing, a router with n links and
>        with uRPF configured would drop (n-1)/n of all incoming spoofed
>        packets, greatly mitigating DoS attacks using spoofed packets,
>        for example (See [RFC3871]).
>
>
> 4.  Deficiencies of Ingress-Filter (BCP0038) and uRPF Approach
>
>    Ingress filtering is definitely to be recommended, and uRPF filtering
>    certainly does have its uses, but, at least in the current state of
>    the Internet, they are insufficient as a protection of the routing
>    infrastructure.
>
>    1.  Ingress filtering works, but it only works if all, or at least
>        the vast majority of ingress points apply ingress filtering.  As
>        can be seen in the Internet today, even when 25% of the Internet
>        is unsecured, those elements that want access to "spoofable"
>        connections simply move their connection to unsecured attachment
>        points.
>
>    2.  uRPF does not work well in places where assymetric routing
>        happens.  This constitutes a large part of the Internet
>
>
>
>
>
>
>
>
> Wu, et al.               Expires August 18, 2007                [Page 4]
> 
> Internet-Draft           SAVA Problem Statement            February 2007
>
>
> 5.  Why IPSEC is not the Solution to This Problem
>
>    IPSEC is a solution to many problems, and it is not the intention of
>    the authors to suggest that it should not be deployed.  It is just
>    not the solution to this particular problem.
>
>    Whereas IPSEC solves end-end security problems and allows endpoints
>    in a connection to verify the identity of connected endpoints, there
>    is also a need for the infrastructure of the Internet to be able to
>    protect itself.  Many attacks employ spoofed IP addresses to either
>    conceal the source of an infrastructure attack or to cause the
>    network infrastructure to, in effect, attack itself.
>
>    The network must be able to secure itself from poorly-secured
>    endpoints.  The goal of the solution to the problem must be to
>    discard spoofed traffic as close to the source of the attack as
>    possible. (i.e. within the infrastructure rather than at the other
>    endpoint(s).
>
>
> 6.  Framework Requirements
>
>    Following is a list of key requirements for any solution/s to the
>    problem described above.  They will be more completely delineated in
>    the proposed workgroup charter and the framework document.
>
> 6.1.  Direct Benefit to Deployers
>
>    One of the reasons for the less-than-adequate deployment of ingress
>    filters is that, in deploying the filters, a network operator or
>    attached private network is mostly protecting the rest of the
>    Internet rather than itself.  It should be a design goal for any
>    solution to give those that deploy the solution some increased level
>    of protection from spoofed attacks from outside of their own
>    adminitrative domain.
>
> 6.2.  Solution Focus on IPv6
>
>    While it is not the intent to develop solutions that cannot be
>    deployed on an IPv4 network, the focus of the work should be on
>    solutions for IPv6 networks.  In other words, if a solution is
>    feasible for IPv6 deployment, but infeasible for IPv4 deployment,
>    that shall not be construed as a disadvantage for the solution.
>
> 6.3.  Performance
>
>    Deployment of SAVA solutions should not place unreasonable stress on
>    network infrastructure components.
>
>
>
> Wu, et al.               Expires August 18, 2007                [Page 5]
> 
> Internet-Draft           SAVA Problem Statement            February 2007
>
>
> 6.4.  Scaling
>
>    SAVA solutions should be feasible for network sizes and no-default
>    prefix tables many times the size experienced today.  SAVA solutions
>    should scale in a way that is at worst linear with the size of the
>    Internet.
>
> 6.5.  Multiple-Fence Solution
>
>    Ingress filtering is a single fence solution, in that it is only
>    applicable only at the access network or at the boundary between an
>    attached private network and a network provider.  Where the attached
>    network is not a stub, it cannot be deployed effectively.  It should
>    be the goal of the SAVA working group to provide solutions that can
>    be deployed at the boundaries between ISPs or on intra-ISP links as
>    well.
>
> 6.6.  Incrementally Deployable
>
>    It must be possible to deploy SAVA solutions incrementally across the
>    network.  In other words, there can be no "flag day".
>
> 6.7.  Loose Coupling
>
>    Components of the overall solution should be able to be deployed in a
>    "mix and match" fashion. this allows for multiple solutions for a
>    given component of the overall solution.
>
>
> 7.  IANA Considerations
>
>    This document makes no request of IANA.
>
>    Note to RFC Editor: this section may be removed on publication as an
>    RFC.
>
>
> 8.  Security Considerations
>
>    For this document, no specific security considerations.  Many of the
>    solution elements will need to be examined carefully for robustness
>    and to see if they do not in themselves introduce security problems.
>
>
> 9.  Acknowledgements
>
>
> 10.  References
>
>
>
> Wu, et al.               Expires August 18, 2007                [Page 6]
> 
> Internet-Draft           SAVA Problem Statement            February 2007
>
>
> 10.1.  Normative References
>
>    [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
>               Requirement Levels", BCP 14, RFC 2119, March 1997.
>
> 10.2.  Informative References
>
>    [Bev05]    Beverley, S. and S. Bauer, ""The spoofer project:
>               inferring the extent of source address filtering on the
>               Internet", USENIX SRUTI 2005", 2007.
>
>    [RFC2827]  Ferguson, P. and D. Senie, "Network Ingress Filtering:
>               Defeating Denial of Service Attacks which employ IP Source
>               Address Spoofing", BCP 38, RFC 2827, May 2000.
>
>    [RFC3871]  Jones, G., "Operational Security Requirements for Large
>               Internet Service Provider (ISP) IP Network
>               Infrastructure", RFC 3871, September 2004.
>
>
> Authors' Addresses
>
>    Jianping Wu
>    CERNET
>    Network Center, Tsinghua University
>    Beijing  100084
>    China
>
>    Email: jianping@cernet.edu.cn
>
>
>    Ronald P. Bonica
>    Juniper Networks
>    2251 Corporate Park Drive
>    Herndon, VA  20171
>    USA
>
>
>    Jun Bi
>    CERNET
>    Network Center, Tsinghua University
>    Beijing  100084
>    China
>
>    Email: junbi@cernet.edu.cn
>
>
>
>
>
>
> Wu, et al.               Expires August 18, 2007                [Page 7]
> 
> Internet-Draft           SAVA Problem Statement            February 2007
>
>
>    Xing Li
>    CERNET
>    Network Center, Tsinghua University
>    Beijing  100084
>    China
>
>    Email: xing@cernet.edu.cn
>
>
>    Gang Ren
>    CERNET
>    Network Center, Tsinghua University
>    Beijing  100084
>    China
>
>    Email: rg03@mails.tsinghua.edu.cn
>
>
>    Mark I. Williams
>    Juniper Networks
>    Suite 1508, W3 Tower, Oriental Plaza, 1 East Chang'An Ave
>    Dong Cheng District, Beijing  100738
>    China
>
>    Email: miw@juniper.net
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Wu, et al.               Expires August 18, 2007                [Page 8]
> 
> Internet-Draft           SAVA Problem Statement            February 2007
>
>
> Full Copyright Statement
>
>    Copyright (C) The IETF Trust (2007).
>
>    This document is subject to the rights, licenses and restrictions
>    contained in BCP 78, and except as set forth therein, the authors
>    retain all their rights.
>
>    This document and the information contained herein are provided on an
>    "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
>    OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
>    THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
>    OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
>    THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
>    WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
>
>
> Intellectual Property
>
>    The IETF takes no position regarding the validity or scope of any
>    Intellectual Property Rights or other rights that might be claimed to
>    pertain to the implementation or use of the technology described in
>    this document or the extent to which any license under such rights
>    might or might not be available; nor does it represent that it has
>    made any independent effort to identify any such rights.  Information
>    on the procedures with respect to rights in RFC documents can be
>    found in BCP 78 and BCP 79.
>
>    Copies of IPR disclosures made to the IETF Secretariat and any
>    assurances of licenses to be made available, or the result of an
>    attempt made to obtain a general license or permission for the use of
>    such proprietary rights by implementers or users of this
>    specification can be obtained from the IETF on-line IPR repository at
>    http://www.ietf.org/ipr.
>
>    The IETF invites any interested party to bring to its attention any
>    copyrights, patents or patent applications, or other proprietary
>    rights that may cover technology that may be required to implement
>    this standard.  Please address the information to the IETF at
>    ietf-ipr@ietf.org.
>
>
> Acknowledgment
>
>    Funding for the RFC Editor function is provided by the IETF
>    Administrative Support Activity (IASA).
>
>
>
>
>
> Wu, et al.               Expires August 18, 2007                [Page 9]
> 
>
>   
> ------------------------------------------------------------------------
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>   

-- 
"Product roadmap and/or product discussion in this email set forth
Juniper Networks' current intention and is subject to change at any
time without notice.  No purchases are contingent upon Juniper
Networks delivering any feature or functionality expressed or implied
in this roadmap or product discussion."
-----------------------------------------------------------------
Mark Williams                        Juniper Networks
Liaison                              Beijing Office
Academic Networking Sector           Tel: +86 10 6528 8800 x16032
Asia Pacific                         FAX: +61 7 3251 0155
miw@juniper.net                      Cell: +86 1370-111-4749

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



From ipv6-bounces@ietf.org Sat Feb 17 19:06:57 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HIZTb-0003wI-VU; Sat, 17 Feb 2007 19:00:23 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HIZTa-0003w8-Ce
	for ipv6@ietf.org; Sat, 17 Feb 2007 19:00:22 -0500
Received: from [2002:425c:4242:0:210:5aff:fe86:1f54] (helo=cyteen.hactrn.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HIZTa-0003e0-4N
	for ipv6@ietf.org; Sat, 17 Feb 2007 19:00:22 -0500
Received: from cyteen.hactrn.net (localhost [127.0.0.1])
	by cyteen.hactrn.net (Postfix) with ESMTP id E80B52844C
	for <ipv6@ietf.org>; Sun, 18 Feb 2007 00:00:02 +0000 (UTC)
To: ipv6@ietf.org
From: Rob Austein <sra+ipng@hactrn.net>
Date: Sun, 18 Feb 2007 00:00:02 +0000
Message-Id: <20070218000002.E80B52844C@cyteen.hactrn.net>
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Subject: Weekly posting summary for ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 50.00% |    5 | 39.63% |    44467 | pars.mutaf@int-evry.fr
 20.00% |    2 | 45.82% |    51405 | miw@juniper.net
 10.00% |    1 |  5.58% |     6264 | albert.e.manfredi@boeing.com
 10.00% |    1 |  5.19% |     5825 | huitema@windows.microsoft.com
 10.00% |    1 |  3.77% |     4233 | sra+ipng@hactrn.net
--------+------+--------+----------+------------------------
100.00% |   10 |100.00% |   112194 | Total

Grunchweather Associates provides this automatic summary on an at-whim
basis at the request of the IPv6 WG chairs.  Your mileage may vary.
We decline responsibilities, all shapes, all sizes, all colors.
If this script produces broken output, you get to keep both pieces.

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



From ipv6-bounces@ietf.org Sat Feb 24 19:08:30 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HL6oD-0006mI-3y; Sat, 24 Feb 2007 19:00:09 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HL6oB-0006l2-OG
	for ipv6@ietf.org; Sat, 24 Feb 2007 19:00:07 -0500
Received: from [2002:425c:4242:0:210:5aff:fe86:1f54] (helo=cyteen.hactrn.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HL6oB-0003hj-Gj
	for ipv6@ietf.org; Sat, 24 Feb 2007 19:00:07 -0500
Received: from cyteen.hactrn.net (localhost [127.0.0.1])
	by cyteen.hactrn.net (Postfix) with ESMTP id DC41828462
	for <ipv6@ietf.org>; Sun, 25 Feb 2007 00:00:02 +0000 (UTC)
To: ipv6@ietf.org
From: Rob Austein <sra+ipng@hactrn.net>
Date: Sun, 25 Feb 2007 00:00:02 +0000
Message-Id: <20070225000002.DC41828462@cyteen.hactrn.net>
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Subject: Weekly posting summary for ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
100.00% |    1 |100.00% |     3805 | Total
--------+------+--------+----------+------------------------
100.00% |    1 |100.00% |     3805 | sra+ipng@hactrn.net

Grunchweather Associates provides this automatic summary on an at-whim
basis at the request of the IPv6 WG chairs.  Your mileage may vary.
We decline responsibilities, all shapes, all sizes, all colors.
If this script produces broken output, you get to keep both pieces.

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



From ipv6-bounces@ietf.org Sun Feb 25 06:50:17 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLHlm-0006NJ-T9; Sun, 25 Feb 2007 06:42:22 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKBe2-0004Ry-07
	for ipv6@ietf.org; Thu, 22 Feb 2007 05:57:50 -0500
Received: from burp.tkv.asdf.org ([212.16.99.49] helo=moth.iki.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKBe0-0008He-Io
	for ipv6@ietf.org; Thu, 22 Feb 2007 05:57:49 -0500
Received: from moth.iki.fi (msa@localhost [127.0.0.1])
	by moth.iki.fi (8.13.8/8.13.8/Debian-3) with ESMTP id l1MAvZGw026554
	for <ipv6@ietf.org>; Thu, 22 Feb 2007 12:57:35 +0200
Received: (from msa@localhost)
	by moth.iki.fi (8.13.8/8.13.8/Submit) id l1MAvYSL026550;
	Thu, 22 Feb 2007 12:57:34 +0200
Date: Thu, 22 Feb 2007 12:57:34 +0200
Message-Id: <200702221057.l1MAvYSL026550@moth.iki.fi>
From: Markku Savela <msa@moth.iki.fi>
To: ipv6@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
X-Mailman-Approved-At: Sun, 25 Feb 2007 06:42:21 -0500
Subject: IPv6 (and IPv4) over IEEE 802.15.3 ?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi,

Slightly off topic, but I'm trying to find something that would guide
how to map IPv6 (and also IPv4) over IEEE 802.15.3 link layer.

I only found 6lowpan for 802.15.4. Where is the same for 802.15.3?

-- 
Markku Savela

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



From ipv6-bounces@ietf.org Sun Feb 25 19:51:02 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLTtN-0000VT-T5; Sun, 25 Feb 2007 19:39:01 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HLTtM-0000VE-CK
	for ipv6@ietf.org; Sun, 25 Feb 2007 19:39:00 -0500
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HLTtG-0007Rt-UF
	for ipv6@ietf.org; Sun, 25 Feb 2007 19:39:00 -0500
Received: from ep_mmp2 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTP id <0JE100CDHOGDP9@mailout2.samsung.com> for ipv6@ietf.org;
	Mon, 26 Feb 2007 09:38:37 +0900 (KST)
Received: from daniel ([168.219.198.109])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0JE1003BNOGCMT@mmp2.samsung.com> for
	ipv6@ietf.org; Mon, 26 Feb 2007 09:38:37 +0900 (KST)
Date: Mon, 26 Feb 2007 09:38:27 +0900
From: Daniel Park <soohong.park@samsung.com>
In-reply-to: <200702221057.l1MAvYSL026550@moth.iki.fi>
To: 'Markku Savela' <msa@moth.iki.fi>, ipv6@ietf.org
Message-id: <0JE1003BOOGCMT@mmp2.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcdY03bt3j5HdihQTmqRBuW+1o4ivAAaTG1w
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: 6lowpan <6lowpan@lists.ietf.org>
Subject: RE: IPv6 (and IPv4) over IEEE 802.15.3 ?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


(ccing 6lowpan list)

Markku,

No space for this discussion in IETF yet. If you have any
tangible and applicable use cases in conjunction with IP
over 802.15.3, it should be chartered to develop the solutions.

Several years back, IP over 802.15.1 (BT) occurred in
IETF, but failed to be formed a new WG. From the IP 
perspective, 6lowpan (IPv6 over 802.15.4) has its applicable 
area as ZigBee and this kinds of IP connectivity. 16ng 
(IP over 802.16) has also its applicable area such as 
WiMAX and WiBro IP networks. 

Is there any specific reason for IETF to develop IP over
802.15.3 solutions ? Otherwise, I'd recommend you to
work on that via Individual Track regardless of any specific
WGs at this stage. Also, 6lowpan would be better 
place for further discussion than IPv6 since they have
WPAN expertises...

My 0.02 cents.

Daniel 

-----Original Message-----
From: Markku Savela [mailto:msa@moth.iki.fi] 
Sent: Thursday, February 22, 2007 7:58 PM
To: ipv6@ietf.org
Subject: IPv6 (and IPv4) over IEEE 802.15.3 ?

Hi,

Slightly off topic, but I'm trying to find something that would guide how to
map IPv6 (and also IPv4) over IEEE 802.15.3 link layer.

I only found 6lowpan for 802.15.4. Where is the same for 802.15.3?

--
Markku Savela

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



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



From ipv6-bounces@ietf.org Mon Feb 26 11:30:15 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLieo-0006Sm-0k; Mon, 26 Feb 2007 11:24:58 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HLiem-0006QU-5G
	for ipv6@ietf.org; Mon, 26 Feb 2007 11:24:56 -0500
Received: from mail128.messagelabs.com ([216.82.250.131])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HLiej-0008I0-Pr
	for ipv6@ietf.org; Mon, 26 Feb 2007 11:24:56 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@motorola.com
X-Msg-Ref: server-5.tower-128.messagelabs.com!1172507092!15130959!1
X-StarScan-Version: 5.5.10.7.1; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 21137 invoked from network); 26 Feb 2007 16:24:52 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-5.tower-128.messagelabs.com with SMTP;
	26 Feb 2007 16:24:52 -0000
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l1QGOqgc014137
	for <ipv6@ietf.org>; Mon, 26 Feb 2007 09:24:52 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id l1QGOpg0010413
	for <ipv6@ietf.org>; Mon, 26 Feb 2007 10:24:51 -0600 (CST)
Message-ID: <45E309D1.9060504@motorola.com>
Date: Mon, 26 Feb 2007 17:24:49 +0100
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: ipv6@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Subject: One potential use of draft-haberman-ipv6-ra-flags-option-00.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi IPv6 WG,

I'm looking at using prefixes in the Router Advertisement, a bit like 
rfc4191 (differently than the classic PIO (Prefix Information Option)).

The context is to make two Mobile Routers (NEMOv6-RFC3963, Moving 
Networks) talk to each other when their Home Agents aren't available. 
To that end, there was recent discussion on the MANEMO list 
manemo@mobileip.jp.

This prefix-in-special-RA mechanism is in the NANO draft 
draft-petrescu-manemo-nano-00.txt http://tinyurl.com/35h78x
It uses NDP expansion flags of draft-haberman.

And I'm looking for feedback whether I'm using this expansion flags 
correctly.

Or any other issue with having a prefix in an RA that is used by the 
receiving _router_ (not 'host' as in rfc4191) to establish a route to a 
neighbouring router's link-local address.

Or any another better way to achieve same effect: make two Mobile 
Routers talk to each other via their egress interface.

Thanks,

Alex

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



