From owner-multi6@ops.ietf.org  Wed Dec  1 05:49:06 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11659
	for <multi6-archive@lists.ietf.org>; Wed, 1 Dec 2004 05:49:05 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD))
	id 1CZS1z-000KzS-Lw
	for multi6-data@psg.com; Wed, 01 Dec 2004 10:48:19 +0000
Received: from [195.212.29.151] (helo=mtagate2.de.ibm.com)
	by psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1CZS1y-000Kyv-MT
	for multi6@ops.ietf.org; Wed, 01 Dec 2004 10:48:19 +0000
Received: from d12nrmr1707.megacenter.de.ibm.com (d12nrmr1707.megacenter.de.ibm.com [9.149.167.81])
	by mtagate2.de.ibm.com (8.12.10/8.12.10) with ESMTP id iB1AmHbP118136
	for <multi6@ops.ietf.org>; Wed, 1 Dec 2004 10:48:17 GMT
Received: from d12av03.megacenter.de.ibm.com (d12av03.megacenter.de.ibm.com [9.149.165.213])
	by d12nrmr1707.megacenter.de.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id iB1AmQBD039042
	for <multi6@ops.ietf.org>; Wed, 1 Dec 2004 11:48:26 +0100
Received: from d12av03.megacenter.de.ibm.com (loopback [127.0.0.1])
	by d12av03.megacenter.de.ibm.com (8.12.11/8.12.11) with ESMTP id iB1AmG9b025168
	for <multi6@ops.ietf.org>; Wed, 1 Dec 2004 11:48:17 +0100
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232])
	by d12av03.megacenter.de.ibm.com (8.12.11/8.12.11) with ESMTP id iB1AmGYJ025153;
	Wed, 1 Dec 2004 11:48:16 +0100
Received: from zurich.ibm.com (sig-9-145-249-118.de.ibm.com [9.145.249.118])
	by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id LAA79096;
	Wed, 1 Dec 2004 11:48:15 +0100
Message-ID: <41ADA175.6030609@zurich.ibm.com>
Date: Wed, 01 Dec 2004 11:48:21 +0100
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
CC: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>,
        Multi6 List <multi6@ops.ietf.org>
Subject: Re: Mini WGLC draft-ietf-multi6-multihoming-threats-02.txt
References: <44BEF211-3F73-11D9-B14D-000A95928574@kurtis.pp.se> <E6FF5A0C-4327-11D9-92FB-000A95CD987A@muada.com>
In-Reply-To: <E6FF5A0C-4327-11D9-92FB-000A95CD987A@muada.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.1
Sender: owner-multi6@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Iljitsch van Beijnum wrote:
> On 26-nov-04, at 7:20, Kurt Erik Lindqvist wrote:
> 
>> hereby we start a "mini" Working Group Last Call for the threats
>> document. This concludes on December the 1th 17.00 CET.
> 
> 
> The link doesn't work.

Looks like somebody's mail system wrapped the line
http://www.ietf.org/internet-drafts/draft-ietf-multi6-multihoming-threats-02.txt

> 
> What exactly is the purpose of this last call?

Just a final check before the IESG reaches its decision.

    Brian



From owner-multi6@ops.ietf.org  Wed Dec  1 05:54:07 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12009
	for <multi6-archive@lists.ietf.org>; Wed, 1 Dec 2004 05:54:07 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD))
	id 1CZS7P-000MKO-Eg
	for multi6-data@psg.com; Wed, 01 Dec 2004 10:53:55 +0000
Received: from [195.212.29.136] (helo=mtagate3.uk.ibm.com)
	by psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1CZS7O-000MK5-3R
	for multi6@ops.ietf.org; Wed, 01 Dec 2004 10:53:54 +0000
Received: from d06nrmr1407.portsmouth.uk.ibm.com (d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185])
	by mtagate3.uk.ibm.com (8.12.10/8.12.10) with ESMTP id iB1ArO5M185440;
	Wed, 1 Dec 2004 10:53:27 GMT
Received: from sihl.zurich.ibm.com (d06av04.portsmouth.uk.ibm.com [9.149.37.216])
	by d06nrmr1407.portsmouth.uk.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id iB1ArRG2139898;
	Wed, 1 Dec 2004 10:53:28 GMT
Received: from zurich.ibm.com (sig-9-145-249-118.de.ibm.com [9.145.249.118])
	by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id LAA48024;
	Wed, 1 Dec 2004 11:52:05 +0100
Message-ID: <41ADA256.7040506@zurich.ibm.com>
Date: Wed, 01 Dec 2004 11:52:06 +0100
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: Mohan Parthasarathy <mohanp@sbcglobal.net>
CC: Multi6 <multi6@ops.ietf.org>
Subject: Re: mumti6dt drafts as WG drafts?
References: <41AC6D70.30204@zurich.ibm.com> <010901c4d74b$02984870$861167c0@adithya>
In-Reply-To: <010901c4d74b$02984870$861167c0@adithya>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.1
Sender: owner-multi6@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Well, yes, the solution architecture draft is intended to give the
overview.

It's quite likely that when the various pieces have stabilized,
they should be combined into a more complete document. But that is
really a question for whichever WG is tasked with doing the complete
specification, so it is not a question for multi6 today. The idea now
was to get the existing drafts into a good state individually.

     Brian

Mohan Parthasarathy wrote:
> Brian,
> 
> So, the solution architecture document will come later on based on the
> WG documents i guess. What is the rationale behind having it as
> separate documents still ? Having read some of them, i felt that it might be
> good to have some of them at least merged to understand the solution
> better. For example, the first three below (shim, hba and func) can be
> merged. 
> 
> -mohan
> 
> 
>>In accordance with the consensus to proceed with the direction
>>proposed by the design team, does anyone object to the next versions
>>of the following drafts being formally adopted as WG drafts?
>>This would mean they have names like draft-ietf-multi6-*
>>
>>Please let us know this week if you object, and why.
>>
>>     Multihoming Level 3 Shim Approach
>>     (draft-nordmark-multi6dt-shim-00.txt)
>>     Hash Based Addresses (HBA)
>>     (draft-bagnulo-multi6dt-hba-00.txt)
>>     Functional decomposition of the M6 protocol
>>     (draft-bagnulo-multi6dt-functional-dec-00.txt)
>>     Failure Detection and Locator Selection in Multi6
>>     (draft-arkko-multi6dt-failure-detection-00.txt)
>>     Multi6 Application Referral Issues
>>     (draft-nordmark-multi6dt-refer-00.txt)
>>
>>
>>    Brian
>>    multi6 co-chair
>>
> 
> 



From owner-multi6@ops.ietf.org  Wed Dec  1 05:57:17 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12645
	for <multi6-archive@lists.ietf.org>; Wed, 1 Dec 2004 05:57:17 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD))
	id 1CZSAY-000N19-EB
	for multi6-data@psg.com; Wed, 01 Dec 2004 10:57:10 +0000
Received: from [195.212.29.135] (helo=mtagate2.uk.ibm.com)
	by psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1CZSAF-000Mwp-RX
	for multi6@ops.ietf.org; Wed, 01 Dec 2004 10:57:09 +0000
Received: from d06nrmr1307.portsmouth.uk.ibm.com (d06nrmr1307.portsmouth.uk.ibm.com [9.149.38.129])
	by mtagate2.uk.ibm.com (8.12.10/8.12.10) with ESMTP id iB1AuRpN354718;
	Wed, 1 Dec 2004 10:56:30 GMT
Received: from sihl.zurich.ibm.com (d06av04.portsmouth.uk.ibm.com [9.149.37.216])
	by d06nrmr1307.portsmouth.uk.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id iB1AuXDc269226;
	Wed, 1 Dec 2004 10:56:33 GMT
Received: from zurich.ibm.com (sig-9-145-249-118.de.ibm.com [9.145.249.118])
	by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id LAA65390;
	Wed, 1 Dec 2004 11:56:22 +0100
Message-ID: <41ADA35C.3000008@zurich.ibm.com>
Date: Wed, 01 Dec 2004 11:56:28 +0100
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: Erik Nordmark <erik.nordmark@sun.com>
CC: Tim Shepard <shep@alum.mit.edu>, Multi6 <multi6@ops.ietf.org>
Subject: Re: Draft multi6 minutes
References: <E1CZ9YJ-00077y-00@alva.home> <41ACB5D5.7040902@sun.com>
In-Reply-To: <41ACB5D5.7040902@sun.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.1
Sender: owner-multi6@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Erik Nordmark wrote:
> Tim Shepard wrote:
...
>> If security is not needed, then perhaps we don't even need to use the
>> HBA scheme.  If security is needed, then perhaps this scheme isn't
>> much better than using some public key cryptography.
> 
> 
> We know that security is needed. full stop.

Also, whether HBA is better or worse than PK crypto isn't quite the
point for me (chair hat off). As long as HBA is strong enough, the
fact that it doesn't require any kind of PKI is an enormous benefit.
Multihoming needs to work between any arbitrary pair of hosts, and doing
that without PKI is an enormous win.

     Brian



From owner-multi6@ops.ietf.org  Wed Dec  1 07:59:12 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24827
	for <multi6-archive@lists.ietf.org>; Wed, 1 Dec 2004 07:59:11 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD))
	id 1CZU2W-000EHW-Va
	for multi6-data@psg.com; Wed, 01 Dec 2004 12:57:00 +0000
Received: from [83.149.65.1] (helo=sequoia.muada.com)
	by psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1CZU2V-000EH9-St
	for multi6@ops.ietf.org; Wed, 01 Dec 2004 12:57:00 +0000
Received: from [127.0.0.1] (sequoia.muada.com [83.149.65.1])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id iB1Cv1Qx088850;
	Wed, 1 Dec 2004 13:57:01 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <41ADA175.6030609@zurich.ibm.com>
References: <44BEF211-3F73-11D9-B14D-000A95928574@kurtis.pp.se> <E6FF5A0C-4327-11D9-92FB-000A95CD987A@muada.com> <41ADA175.6030609@zurich.ibm.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <7966538F-4398-11D9-92FB-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>,
        Multi6 List <multi6@ops.ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Mini WGLC draft-ietf-multi6-multihoming-threats-02.txt
Date: Wed, 1 Dec 2004 13:56:53 +0100
To: Brian E Carpenter <brc@zurich.ibm.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham 
	version=3.0.1
Sender: owner-multi6@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 1-dec-04, at 11:48, Brian E Carpenter wrote:

>> What exactly is the purpose of this last call?

> Just a final check before the IESG reaches its decision.

Before publishing this as an RFC, you mean?

Nit on page 6:

                     interface.  Normally an address uniquely identifies
                     an interfaces but there are cases when the same

Page 32:

     - Third trusted party.  A third party establishes that a given


"Identifier" is defined very differently from the use of "ULID" in the 
more recent DT drafts, to the degree that an ULID can't be an 
identifier according to this document's definition.




From owner-multi6@ops.ietf.org  Wed Dec  1 09:32:15 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03047
	for <multi6-archive@lists.ietf.org>; Wed, 1 Dec 2004 09:32:15 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD))
	id 1CZVVq-0000yq-8L
	for multi6-data@psg.com; Wed, 01 Dec 2004 14:31:22 +0000
Received: from [207.31.248.245] (helo=thingmagic.com)
	by psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1CZVVp-0000yc-Eh
	for multi6@ops.ietf.org; Wed, 01 Dec 2004 14:31:21 +0000
Received: from [24.61.30.237] (account margaret HELO [192.168.2.2])
  by thingmagic.com (CommuniGate Pro SMTP 4.1.8)
  with ESMTP-TLS id 212682; Wed, 01 Dec 2004 09:24:46 -0500
Mime-Version: 1.0
Message-Id: <p06200707bdd385bcee5d@[192.168.2.2]>
In-Reply-To: <7966538F-4398-11D9-92FB-000A95CD987A@muada.com>
References: <44BEF211-3F73-11D9-B14D-000A95928574@kurtis.pp.se>
 <E6FF5A0C-4327-11D9-92FB-000A95CD987A@muada.com>
 <41ADA175.6030609@zurich.ibm.com>
 <7966538F-4398-11D9-92FB-000A95CD987A@muada.com>
Date: Wed, 1 Dec 2004 09:31:13 -0500
To: Iljitsch van Beijnum <iljitsch@muada.com>,
        Brian E Carpenter <brc@zurich.ibm.com>
From: Margaret Wasserman <margaret@thingmagic.com>
Subject: Re: Mini WGLC draft-ietf-multi6-multihoming-threats-02.txt
Cc: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>,
        Multi6 List <multi6@ops.ietf.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham 
	version=3.0.1
Sender: owner-multi6@ops.ietf.org
Precedence: bulk


Hi Iljitsch,

At 1:56 PM +0100 12/1/04, Iljitsch van Beijnum wrote:
>Page 32:
>
>     - Third trusted party.  A third party establishes that a given
>
>"Identifier" is defined very differently from the use of "ULID" in 
>the more recent DT drafts, to the degree that an ULID can't be an 
>identifier according to this document's definition.

I think that this is a good point...

I am not sure that all of the threats related to redirection exist 
when you use ULIDs vs. a pure ID/Loc split.

Are there other places in the document where the threat model would 
be different for ULIDs than for IDs that are not also usable as 
locators?

Margaret





From owner-multi6@ops.ietf.org  Wed Dec  1 10:37:19 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12651
	for <multi6-archive@lists.ietf.org>; Wed, 1 Dec 2004 10:37:18 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD))
	id 1CZWVa-0009HH-5T
	for multi6-data@psg.com; Wed, 01 Dec 2004 15:35:10 +0000
Received: from [195.212.29.153] (helo=mtagate4.de.ibm.com)
	by psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1CZWVY-0009Gm-QP
	for multi6@ops.ietf.org; Wed, 01 Dec 2004 15:35:09 +0000
Received: from d12nrmr1507.megacenter.de.ibm.com (d12nrmr1507.megacenter.de.ibm.com [9.149.167.1])
	by mtagate4.de.ibm.com (8.12.10/8.12.10) with ESMTP id iB1FZ7vU227182
	for <multi6@ops.ietf.org>; Wed, 1 Dec 2004 15:35:07 GMT
Received: from d12av02.megacenter.de.ibm.com (d12av02.megacenter.de.ibm.com [9.149.165.228])
	by d12nrmr1507.megacenter.de.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id iB1FZ2aI130794
	for <multi6@ops.ietf.org>; Wed, 1 Dec 2004 16:35:02 +0100
Received: from d12av02.megacenter.de.ibm.com (loopback [127.0.0.1])
	by d12av02.megacenter.de.ibm.com (8.12.11/8.12.11) with ESMTP id iB1FZ6uv003343
	for <multi6@ops.ietf.org>; Wed, 1 Dec 2004 16:35:06 +0100
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232])
	by d12av02.megacenter.de.ibm.com (8.12.11/8.12.11) with ESMTP id iB1FZ6Df003332;
	Wed, 1 Dec 2004 16:35:06 +0100
Received: from zurich.ibm.com (sig-9-145-249-118.de.ibm.com [9.145.249.118])
	by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id QAA65880;
	Wed, 1 Dec 2004 16:35:04 +0100
Message-ID: <41ADE4AD.5020505@zurich.ibm.com>
Date: Wed, 01 Dec 2004 16:35:09 +0100
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: Margaret Wasserman <margaret@thingmagic.com>
CC: Iljitsch van Beijnum <iljitsch@muada.com>,
        Kurt Erik Lindqvist <kurtis@kurtis.pp.se>,
        Multi6 List <multi6@ops.ietf.org>
Subject: Re: Mini WGLC draft-ietf-multi6-multihoming-threats-02.txt
References: <44BEF211-3F73-11D9-B14D-000A95928574@kurtis.pp.se> <E6FF5A0C-4327-11D9-92FB-000A95CD987A@muada.com> <41ADA175.6030609@zurich.ibm.com> <7966538F-4398-11D9-92FB-000A95CD987A@muada.com> <p06200707bdd385bcee5d@[192.168.2.2]>
In-Reply-To: <p06200707bdd385bcee5d@[192.168.2.2]>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.1
Sender: owner-multi6@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Margaret Wasserman wrote:
> 
> Hi Iljitsch,
> 
> At 1:56 PM +0100 12/1/04, Iljitsch van Beijnum wrote:
> 
>> Page 32:
>>
>>     - Third trusted party.  A third party establishes that a given
>>
>> "Identifier" is defined very differently from the use of "ULID" in the 
>> more recent DT drafts, to the degree that an ULID can't be an 
>> identifier according to this document's definition.
> 
> 
> I think that this is a good point...
> 
> I am not sure that all of the threats related to redirection exist when 
> you use ULIDs vs. a pure ID/Loc split.
> 
> Are there other places in the document where the threat model would be 
> different for ULIDs than for IDs that are not also usable as locators?

Personal opinion: this document is intended to discuss generic threats,
and I think it's a bit unfair to expect it to discuss threats for a
model that hadn't even been invented when the document was almost final.

So I would resolve this by adding a sentence that the specific form of
ULID introduced by the recent design team was not considered and may
(only may) introduce additional threats.

That doesn't let us off the hook of course - ULID threats still need to
be analyzed.

    Brian



From owner-multi6@ops.ietf.org  Wed Dec  1 11:03:32 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17320
	for <multi6-archive@lists.ietf.org>; Wed, 1 Dec 2004 11:03:31 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD))
	id 1CZWwX-000CoJ-Un
	for multi6-data@psg.com; Wed, 01 Dec 2004 16:03:01 +0000
Received: from [192.71.80.74] (helo=laptop2.kurtis.pp.se)
	by psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1CZWwX-000Co0-1R
	for multi6@ops.ietf.org; Wed, 01 Dec 2004 16:03:01 +0000
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by laptop2.kurtis.pp.se (Postfix) with ESMTP
	id C55E76B12E5; Wed,  1 Dec 2004 17:03:18 +0100 (CET)
In-Reply-To: <41ADE4AD.5020505@zurich.ibm.com>
References: <44BEF211-3F73-11D9-B14D-000A95928574@kurtis.pp.se> <E6FF5A0C-4327-11D9-92FB-000A95CD987A@muada.com> <41ADA175.6030609@zurich.ibm.com> <7966538F-4398-11D9-92FB-000A95CD987A@muada.com> <p06200707bdd385bcee5d@[192.168.2.2]> <41ADE4AD.5020505@zurich.ibm.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=fixed
Message-Id: <81951DA8-43B2-11D9-9F36-000A95928574@kurtis.pp.se>
Content-Transfer-Encoding: 7bit
Cc: Multi6 List <multi6@ops.ietf.org>,
        Margaret Wasserman <margaret@thingmagic.com>,
        Iljitsch van Beijnum <iljitsch@muada.com>
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
Subject: Re: Mini WGLC draft-ietf-multi6-multihoming-threats-02.txt
Date: Wed, 1 Dec 2004 17:03:14 +0100
To: Brian E Carpenter <brc@zurich.ibm.com>
X-Pgp-Rfc2646-Fix: 1
X-Mailer: Apple Mail (2.619)
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham 
	version=3.0.1
Sender: owner-multi6@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

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


On 2004-12-01, at 16.35, Brian E Carpenter wrote:

> Margaret Wasserman wrote:
>> Hi Iljitsch,
>> At 1:56 PM +0100 12/1/04, Iljitsch van Beijnum wrote:
>>> Page 32:
>>>
>>>     - Third trusted party.  A third party establishes that a given
>>>
>>> "Identifier" is defined very differently from the use of "ULID" in 
>>> the more recent DT drafts, to the degree that an ULID can't be an 
>>> identifier according to this document's definition.
>> I think that this is a good point...
>> I am not sure that all of the threats related to redirection exist 
>> when you use ULIDs vs. a pure ID/Loc split.
>> Are there other places in the document where the threat model would 
>> be different for ULIDs than for IDs that are not also usable as 
>> locators?
>
> Personal opinion: this document is intended to discuss generic threats,
> and I think it's a bit unfair to expect it to discuss threats for a
> model that hadn't even been invented when the document was almost 
> final.
>
> So I would resolve this by adding a sentence that the specific form of
> ULID introduced by the recent design team was not considered and may
> (only may) introduce additional threats.
>
> That doesn't let us off the hook of course - ULID threats still need to
> be analyzed.

I agree with Brian, and I think that analyzing the threats to ULIDs 
would be a priority for the son-of-multi6.

- - kurtis -

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.1

iQA/AwUBQa3rRaarNKXTPFCVEQL2OQCfbRFJ4UnuYQqC8pfH8OfQ0fNBsvwAoIVm
IHWrHwpPP2YxuXecI2lLc7Ty
=mMQN
-----END PGP SIGNATURE-----




From owner-multi6@ops.ietf.org  Wed Dec  1 11:12:59 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18603
	for <multi6-archive@lists.ietf.org>; Wed, 1 Dec 2004 11:12:59 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD))
	id 1CZX5u-000EWs-GK
	for multi6-data@psg.com; Wed, 01 Dec 2004 16:12:42 +0000
Received: from [163.117.136.123] (helo=smtp03.uc3m.es)
	by psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1CZX5t-000EWa-CZ
	for multi6@ops.ietf.org; Wed, 01 Dec 2004 16:12:41 +0000
Received: from smtp03.uc3m.es (localhost [127.0.0.1])
	by localhost.uc3m.es (Postfix) with ESMTP
	id 228A430811; Wed,  1 Dec 2004 17:12:40 +0100 (CET)
Received: from [163.117.139.34] (unknown [163.117.139.34])
	by smtp03.uc3m.es (Postfix) with ESMTP
	id 0218F3080C; Wed,  1 Dec 2004 17:12:40 +0100 (CET)
In-Reply-To: <010901c4d74b$02984870$861167c0@adithya>
References: <41AC6D70.30204@zurich.ibm.com> <010901c4d74b$02984870$861167c0@adithya>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <D62DB0FB-43B3-11D9-97A6-000D93ACD0FE@it>
Content-Transfer-Encoding: quoted-printable
Cc: "Brian E Carpenter" <brc@zurich.ibm.com>, "Multi6" <multi6@ops.ietf.org>
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
Subject: Re: mumti6dt drafts as WG drafts?
Date: Wed, 1 Dec 2004 17:12:45 +0100
To: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
X-Mailer: Apple Mail (2.619)
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.1
Sender: owner-multi6@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Hi Mohan,

El 01/12/2004, a las 3:11, Mohan Parthasarathy escribi=F3:

> Brian,
>
> So, the solution architecture document will come later on based on the
> WG documents i guess. What is the rationale behind having it as
> separate documents still ? Having read some of them, i felt that it=20
> might be
> good to have some of them at least merged to understand the solution
> better. For example, the first three below (shim, hba and func) can be
> merged.
>

with respect to the HBA draft, imho it would be better to separate the=20=

security mechanisms used form the protocol itself. I mean imho it is=20
not such a good idea to hardcode the security mechanism inside the=20
protocol. HBA is, at most, one of the possible security mechanisms for=20=

multi6 imho. there may and probably will be others. For instance it=20
makes sense to support a different security mechanism based in cgas=20
(only cga i mean) in order to support mobile environmets, Probably in=20
the future new security mechanisms can be defined.
So making a clear distinction between the core multi6 protocol and the=20=

security mechanism used is good imho

makes sense?

regards, marcelo


> -mohan
>
>> In accordance with the consensus to proceed with the direction
>> proposed by the design team, does anyone object to the next versions
>> of the following drafts being formally adopted as WG drafts?
>> This would mean they have names like draft-ietf-multi6-*
>>
>> Please let us know this week if you object, and why.
>>
>>      Multihoming Level 3 Shim Approach
>>      (draft-nordmark-multi6dt-shim-00.txt)
>>      Hash Based Addresses (HBA)
>>      (draft-bagnulo-multi6dt-hba-00.txt)
>>      Functional decomposition of the M6 protocol
>>      (draft-bagnulo-multi6dt-functional-dec-00.txt)
>>      Failure Detection and Locator Selection in Multi6
>>      (draft-arkko-multi6dt-failure-detection-00.txt)
>>      Multi6 Application Referral Issues
>>      (draft-nordmark-multi6dt-refer-00.txt)
>>
>>
>>     Brian
>>     multi6 co-chair
>>
>




From owner-multi6@ops.ietf.org  Wed Dec  1 11:20:02 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19597
	for <multi6-archive@lists.ietf.org>; Wed, 1 Dec 2004 11:20:02 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD))
	id 1CZXCk-000FXp-5A
	for multi6-data@psg.com; Wed, 01 Dec 2004 16:19:46 +0000
Received: from [207.31.248.245] (helo=thingmagic.com)
	by psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1CZXCZ-000FX0-JX
	for multi6@ops.ietf.org; Wed, 01 Dec 2004 16:19:35 +0000
Received: from [207.31.248.246] (account margaret HELO [192.168.2.2])
  by thingmagic.com (CommuniGate Pro SMTP 4.1.8)
  with ESMTP-TLS id 212803; Wed, 01 Dec 2004 11:13:00 -0500
Mime-Version: 1.0
Message-Id: <p0620070fbdd39f031edd@[192.168.2.2]>
In-Reply-To: <41ADE4AD.5020505@zurich.ibm.com>
References: <44BEF211-3F73-11D9-B14D-000A95928574@kurtis.pp.se>
 <E6FF5A0C-4327-11D9-92FB-000A95CD987A@muada.com>
 <41ADA175.6030609@zurich.ibm.com>
 <7966538F-4398-11D9-92FB-000A95CD987A@muada.com>
 <p06200707bdd385bcee5d@[192.168.2.2]> <41ADE4AD.5020505@zurich.ibm.com>
Date: Wed, 1 Dec 2004 11:19:25 -0500
To: Brian E Carpenter <brc@zurich.ibm.com>
From: Margaret Wasserman <margaret@thingmagic.com>
Subject: Re: Mini WGLC draft-ietf-multi6-multihoming-threats-02.txt
Cc: Iljitsch van Beijnum <iljitsch@muada.com>,
        Kurt Erik Lindqvist <kurtis@kurtis.pp.se>,
        Multi6 List <multi6@ops.ietf.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.1
Sender: owner-multi6@ops.ietf.org
Precedence: bulk

At 4:35 PM +0100 12/1/04, Brian E Carpenter wrote:
>So I would resolve this by adding a sentence that the specific form of
>ULID introduced by the recent design team was not considered and may
>(only may) introduce additional threats.

This works for me...  With the understanding that there will need to 
be some further analysis (perhaps in a different WG) to determine 
how/if the threats for ULIDs differ from those described in this 
document.

Margaret




From owner-multi6@ops.ietf.org  Wed Dec  1 11:23:33 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20347
	for <multi6-archive@lists.ietf.org>; Wed, 1 Dec 2004 11:23:32 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD))
	id 1CZXGF-000GD5-Vs
	for multi6-data@psg.com; Wed, 01 Dec 2004 16:23:23 +0000
Received: from [83.149.65.1] (helo=sequoia.muada.com)
	by psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1CZXGE-000GCq-Un
	for multi6@ops.ietf.org; Wed, 01 Dec 2004 16:23:23 +0000
Received: from [127.0.0.1] (sequoia.muada.com [83.149.65.1])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id iB1GNRQx091970;
	Wed, 1 Dec 2004 17:23:27 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <41ADE4AD.5020505@zurich.ibm.com>
References: <44BEF211-3F73-11D9-B14D-000A95928574@kurtis.pp.se> <E6FF5A0C-4327-11D9-92FB-000A95CD987A@muada.com> <41ADA175.6030609@zurich.ibm.com> <7966538F-4398-11D9-92FB-000A95CD987A@muada.com> <p06200707bdd385bcee5d@[192.168.2.2]> <41ADE4AD.5020505@zurich.ibm.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <5038272D-43B5-11D9-92FB-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>,
        Multi6 List <multi6@ops.ietf.org>,
        Margaret Wasserman <margaret@thingmagic.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Mini WGLC draft-ietf-multi6-multihoming-threats-02.txt
Date: Wed, 1 Dec 2004 17:23:19 +0100
To: Brian E Carpenter <brc@zurich.ibm.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham 
	version=3.0.1
Sender: owner-multi6@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 1-dec-04, at 16:35, Brian E Carpenter wrote:

>>> "Identifier" is defined very differently from the use of "ULID" in 
>>> the more recent DT drafts, to the degree that an ULID can't be an 
>>> identifier according to this document's definition.

>> I think that this is a good point...
>> I am not sure that all of the threats related to redirection exist 
>> when you use ULIDs vs. a pure ID/Loc split.

Not if we require initial connectivity to happen using the ULID as a 
reachable address/locator.

(But I think we'll want to be able to repair an initially unreachable 
ULID using alternative locators in the future, so we probably shouldn't 
depend on this advantage more than we have to.)

>> Are there other places in the document where the threat model would 
>> be different for ULIDs than for IDs that are not also usable as 
>> locators?

Hard to say. However, the threat model is radically different when HBA 
(or CGA) is in use, so a document that looks at this will be very 
different from this general purpose document. I'm not sure if analyzing 
ULIDs without HBA/CGA is useful, considering the proposed solutions 
that are on the table.

> Personal opinion: this document is intended to discuss generic threats,
> and I think it's a bit unfair to expect it to discuss threats for a
> model that hadn't even been invented when the document was almost 
> final.

I agree. My problem with the identifier definition is that an ULID 
doesn't fit this definition, most notably because:

                     The identifiers are not associated with an
                     interface.

My conclusion is that the definition is too strict so it should be 
changed to encompass ULIDs so nothing stands in the way of applying 
this document to solutions that use ULIDs.




From owner-multi6@ops.ietf.org  Wed Dec  1 12:00:25 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26473
	for <multi6-archive@lists.ietf.org>; Wed, 1 Dec 2004 12:00:25 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD))
	id 1CZXon-000KDn-D9
	for multi6-data@psg.com; Wed, 01 Dec 2004 16:59:05 +0000
Received: from [131.160.192.2] (helo=p2.piuha.net)
	by psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1CZXom-000KDY-Hd
	for multi6@ops.ietf.org; Wed, 01 Dec 2004 16:59:04 +0000
Received: from piuha.net (p2.piuha.net [131.160.192.2])
	by p2.piuha.net (Postfix) with ESMTP id 0C8D58988B;
	Wed,  1 Dec 2004 18:59:03 +0200 (EET)
Message-ID: <41ADF7D5.6070501@piuha.net>
Date: Wed, 01 Dec 2004 18:56:53 +0200
From: Jari Arkko <jari.arkko@piuha.net>
Reply-To: jari.arkko@piuha.net
Organization: None
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040316
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
Cc: Mohan Parthasarathy <mohanp@sbcglobal.net>, Multi6 <multi6@ops.ietf.org>
Subject: Re: mumti6dt drafts as WG drafts?
References: <41AC6D70.30204@zurich.ibm.com> <010901c4d74b$02984870$861167c0@adithya> <D62DB0FB-43B3-11D9-97A6-000D93ACD0FE@it>
In-Reply-To: <D62DB0FB-43B3-11D9-97A6-000D93ACD0FE@it>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham 
	version=3.0.1
Sender: owner-multi6@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

marcelo bagnulo braun wrote:

> with respect to the HBA draft, imho it would be better to separate the 
> security mechanisms used form the protocol itself. I mean imho it is not 
> such a good idea to hardcode the security mechanism inside the protocol. 
> HBA is, at most, one of the possible security mechanisms for multi6 
> imho. there may and probably will be others. For instance it makes sense 
> to support a different security mechanism based in cgas (only cga i 
> mean) in order to support mobile environmets, Probably in the future new 
> security mechanisms can be defined.
> So making a clear distinction between the core multi6 protocol and the 
> security mechanism used is good imho

I agree with Marcelo. To put it in slightly different words,
I believe HBA is modular enough to be defined on its own.
For the shim and functional decomposition merging would
be more appropriate.

--Jari



From owner-multi6@ops.ietf.org  Wed Dec  1 12:14:05 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27814
	for <multi6-archive@lists.ietf.org>; Wed, 1 Dec 2004 12:14:05 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD))
	id 1CZY2x-000MQF-N4
	for multi6-data@psg.com; Wed, 01 Dec 2004 17:13:43 +0000
Received: from [131.160.192.2] (helo=p2.piuha.net)
	by psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1CZY2t-000MPv-Gu
	for multi6@ops.ietf.org; Wed, 01 Dec 2004 17:13:39 +0000
Received: from piuha.net (p2.piuha.net [131.160.192.2])
	by p2.piuha.net (Postfix) with ESMTP id A54778988B;
	Wed,  1 Dec 2004 19:13:38 +0200 (EET)
Message-ID: <41ADFB41.3000500@piuha.net>
Date: Wed, 01 Dec 2004 19:11:29 +0200
From: Jari Arkko <jari.arkko@piuha.net>
Reply-To: jari.arkko@piuha.net
Organization: None
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040316
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Brian E Carpenter <brc@zurich.ibm.com>
Cc: Erik Nordmark <erik.nordmark@sun.com>, Tim Shepard <shep@alum.mit.edu>,
        Multi6 <multi6@ops.ietf.org>
Subject: Re: Draft multi6 minutes
References: <E1CZ9YJ-00077y-00@alva.home> <41ACB5D5.7040902@sun.com> <41ADA35C.3000008@zurich.ibm.com>
In-Reply-To: <41ADA35C.3000008@zurich.ibm.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.1
Sender: owner-multi6@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Brian E Carpenter wrote:

> Also, whether HBA is better or worse than PK crypto isn't quite the
> point for me (chair hat off). As long as HBA is strong enough, the
> fact that it doesn't require any kind of PKI is an enormous benefit.
> Multihoming needs to work between any arbitrary pair of hosts, and doing
> that without PKI is an enormous win.

A small clarification may be appropriate here. We do not
have a PKI (= Public Key *Infrastructure*) proposal on
the table. The only thing we have on the table is a
proposal which uses at least symmetric key crypto and may
also use public key crypto. However, both modes are very
similar from the 10.000 ft perspective: both are
completely zero-config and neither one requires any
other nodes besides the multihomed node to work. The only
difference is in the cryptographic formulas and some
flexibility. So no infrastructure involved or needed.

The way that I understand Tim's comment was
that he was asking (1) whether the benefits of
symmetric-only mode are useful if you in any
case may have to do some of the Sec calculations,
which add to the CPU cost of the scheme when
creating addresses, and (2) whether the 2^59
difference between defenders and attackers is
useful. Erik responded well to the latter question,
and I don't have much to add.

The first question is valid, however. But you have
to remember that the Sec scheme is only built for
the future -- right now we don't feel it needs to
be turned on. So there is an immediate benefit to
MULTI6 users. YMMV regarding the value of that
benefit. Personally, I think it is good bang for
the buck, considering that it does not increase the
complexity more than a little -- even if current
equipment such as cell phones can already handle
PK crypto well.

But as explained above, the benefit that symmetric key
crypto has to do with CPU cost, NOT with the requirement
for any infrastructure.

--Jari



From owner-multi6@ops.ietf.org  Wed Dec  1 13:51:37 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09112
	for <multi6-archive@lists.ietf.org>; Wed, 1 Dec 2004 13:51:36 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD))
	id 1CZZXd-000ABi-HQ
	for multi6-data@psg.com; Wed, 01 Dec 2004 18:49:29 +0000
Received: from [192.18.42.13] (helo=nwkea-mail-1.sun.com)
	by psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1CZZXT-000A9j-7q
	for multi6@ops.ietf.org; Wed, 01 Dec 2004 18:49:19 +0000
Received: from jurassic.eng.sun.com ([129.146.81.36])
	by nwkea-mail-1.sun.com (8.12.10/8.12.9) with ESMTP id iB1InB6O010528;
	Wed, 1 Dec 2004 10:49:11 -0800 (PST)
Received: from [192.9.61.11] (punchin-nordmark.SFBay.Sun.COM [192.9.61.11])
	by jurassic.eng.sun.com (8.13.1+Sun/8.13.1) with ESMTP id iB1InBTH455379;
	Wed, 1 Dec 2004 10:49:11 -0800 (PST)
Message-ID: <41AE1263.1050607@sun.com>
Date: Wed, 01 Dec 2004 10:50:11 -0800
From: Erik Nordmark <erik.nordmark@sun.com>
User-Agent: Mozilla Thunderbird 0.8 (X11/20040916)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
CC: Brian E Carpenter <brc@zurich.ibm.com>,
        Kurt Erik Lindqvist <kurtis@kurtis.pp.se>,
        Multi6 List <multi6@ops.ietf.org>
Subject: Re: Mini WGLC draft-ietf-multi6-multihoming-threats-02.txt
References: <44BEF211-3F73-11D9-B14D-000A95928574@kurtis.pp.se> <E6FF5A0C-4327-11D9-92FB-000A95CD987A@muada.com> <41ADA175.6030609@zurich.ibm.com> <7966538F-4398-11D9-92FB-000A95CD987A@muada.com>
In-Reply-To: <7966538F-4398-11D9-92FB-000A95CD987A@muada.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.1
Sender: owner-multi6@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Iljitsch van Beijnum wrote:

> Nit on page 6:
> 
>                     interface.  Normally an address uniquely identifies
>                     an interfaces but there are cases when the same
> 
> Page 32:
> 
>     - Third trusted party.  A third party establishes that a given

Thanks.

> "Identifier" is defined very differently from the use of "ULID" in the 
> more recent DT drafts, to the degree that an ULID can't be an identifier 
> according to this document's definition.

While the definitions are different, I don't see what the conflict is.
Can you elaborate?

   Erik



From owner-multi6@ops.ietf.org  Wed Dec  1 13:53:30 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09313
	for <multi6-archive@lists.ietf.org>; Wed, 1 Dec 2004 13:53:30 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD))
	id 1CZZas-000Ar0-9I
	for multi6-data@psg.com; Wed, 01 Dec 2004 18:52:50 +0000
Received: from [192.18.98.36] (helo=brmea-mail-4.sun.com)
	by psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1CZZaj-000ApG-6a
	for multi6@ops.ietf.org; Wed, 01 Dec 2004 18:52:41 +0000
Received: from jurassic.eng.sun.com ([129.146.82.37])
	by brmea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id iB1IqXun008876;
	Wed, 1 Dec 2004 11:52:33 -0700 (MST)
Received: from [192.9.61.11] (punchin-nordmark.SFBay.Sun.COM [192.9.61.11])
	by jurassic.eng.sun.com (8.13.1+Sun/8.13.1) with ESMTP id iB1IqXfT456514;
	Wed, 1 Dec 2004 10:52:33 -0800 (PST)
Message-ID: <41AE132D.50005@sun.com>
Date: Wed, 01 Dec 2004 10:53:33 -0800
From: Erik Nordmark <erik.nordmark@sun.com>
User-Agent: Mozilla Thunderbird 0.8 (X11/20040916)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Margaret Wasserman <margaret@thingmagic.com>
CC: Iljitsch van Beijnum <iljitsch@muada.com>,
        Brian E Carpenter <brc@zurich.ibm.com>,
        Kurt Erik Lindqvist <kurtis@kurtis.pp.se>,
        Multi6 List <multi6@ops.ietf.org>
Subject: Re: Mini WGLC draft-ietf-multi6-multihoming-threats-02.txt
References: <44BEF211-3F73-11D9-B14D-000A95928574@kurtis.pp.se> <E6FF5A0C-4327-11D9-92FB-000A95CD987A@muada.com> <41ADA175.6030609@zurich.ibm.com> <7966538F-4398-11D9-92FB-000A95CD987A@muada.com> <p06200707bdd385bcee5d@[192.168.2.2]>
In-Reply-To: <p06200707bdd385bcee5d@[192.168.2.2]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham 
	version=3.0.1
Sender: owner-multi6@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Margaret Wasserman wrote:

> I am not sure that all of the threats related to redirection exist when 
> you use ULIDs vs. a pure ID/Loc split.

Which is why there is some text disclaiming this in the 3rd paragraph of 
the introduction.

> Are there other places in the document where the threat model would be 
> different for ULIDs than for IDs that are not also usable as locators?

Do we need to answer this question now and for this document?
My assumption is that any proposed solution would need to do some form 
of security evaluation against the whole list of threats and it might 
very well be that some threats don't apply at all because there is no 
separate ID name space. But we can defer that question until later I 
think, and keep this document more general.

    Erik



From owner-multi6@ops.ietf.org  Wed Dec  1 14:40:07 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16523
	for <multi6-archive@lists.ietf.org>; Wed, 1 Dec 2004 14:40:07 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD))
	id 1CZaJa-000J3f-Cw
	for multi6-data@psg.com; Wed, 01 Dec 2004 19:39:02 +0000
Received: from [192.18.98.36] (helo=brmea-mail-4.sun.com)
	by psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1CZaJZ-000J3N-8c
	for multi6@ops.ietf.org; Wed, 01 Dec 2004 19:39:01 +0000
Received: from jurassic.eng.sun.com ([129.146.85.105])
	by brmea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id iB1Ivjun012978;
	Wed, 1 Dec 2004 11:57:45 -0700 (MST)
Received: from [192.9.61.11] (punchin-nordmark.SFBay.Sun.COM [192.9.61.11])
	by jurassic.eng.sun.com (8.13.1+Sun/8.13.1) with ESMTP id iB1IvjR7458050;
	Wed, 1 Dec 2004 10:57:45 -0800 (PST)
Message-ID: <41AE1465.3090207@sun.com>
Date: Wed, 01 Dec 2004 10:58:45 -0800
From: Erik Nordmark <erik.nordmark@Sun.COM>
User-Agent: Mozilla Thunderbird 0.8 (X11/20040916)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
CC: Brian E Carpenter <brc@zurich.ibm.com>,
        Kurt Erik Lindqvist <kurtis@kurtis.pp.se>,
        Multi6 List <multi6@ops.ietf.org>,
        Margaret Wasserman <margaret@thingmagic.com>
Subject: Re: Mini WGLC draft-ietf-multi6-multihoming-threats-02.txt
References: <44BEF211-3F73-11D9-B14D-000A95928574@kurtis.pp.se> <E6FF5A0C-4327-11D9-92FB-000A95CD987A@muada.com> <41ADA175.6030609@zurich.ibm.com> <7966538F-4398-11D9-92FB-000A95CD987A@muada.com> <p06200707bdd385bcee5d@[192.168.2.2]> <41ADE4AD.5020505@zurich.ibm.com> <5038272D-43B5-11D9-92FB-000A95CD987A@muada.com>
In-Reply-To: <5038272D-43B5-11D9-92FB-000A95CD987A@muada.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham 
	version=3.0.1
Sender: owner-multi6@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Iljitsch van Beijnum wrote:

> I agree. My problem with the identifier definition is that an ULID 
> doesn't fit this definition, most notably because:
> 
>                     The identifiers are not associated with an
>                     interface.
> 
> My conclusion is that the definition is too strict so it should be 
> changed to encompass ULIDs so nothing stands in the way of applying this 
> document to solutions that use ULIDs.

Ignore my mail asking for clarifications; I now see the issue.

I think we should reword the above sentence to say that the identifiers 
are not tightly bound to an interface; to provide communication 
survivability when one interface fails the identifiers must be usable on 
any interface.

(I welcome suggestions for how to make that text shorter.)

    Erik



From owner-multi6@ops.ietf.org  Wed Dec  1 15:10:36 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18917
	for <multi6-archive@lists.ietf.org>; Wed, 1 Dec 2004 15:10:35 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD))
	id 1CZaYz-000LtT-0r
	for multi6-data@psg.com; Wed, 01 Dec 2004 19:54:57 +0000
Received: from [83.149.65.1] (helo=sequoia.muada.com)
	by psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1CZaYy-000LtC-4L
	for multi6@ops.ietf.org; Wed, 01 Dec 2004 19:54:56 +0000
Received: from [127.0.0.1] (sequoia.muada.com [83.149.65.1])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id iB1Jt2Qx095187;
	Wed, 1 Dec 2004 20:55:02 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <41AE1465.3090207@sun.com>
References: <44BEF211-3F73-11D9-B14D-000A95928574@kurtis.pp.se> <E6FF5A0C-4327-11D9-92FB-000A95CD987A@muada.com> <41ADA175.6030609@zurich.ibm.com> <7966538F-4398-11D9-92FB-000A95CD987A@muada.com> <p06200707bdd385bcee5d@[192.168.2.2]> <41ADE4AD.5020505@zurich.ibm.com> <5038272D-43B5-11D9-92FB-000A95CD987A@muada.com> <41AE1465.3090207@sun.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <DEF91183-43D2-11D9-92FB-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: Multi6 List <multi6@ops.ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Mini WGLC draft-ietf-multi6-multihoming-threats-02.txt
Date: Wed, 1 Dec 2004 20:54:54 +0100
To: Erik Nordmark <erik.nordmark@sun.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.1
Sender: owner-multi6@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 1-dec-04, at 19:58, Erik Nordmark wrote:

> I think we should reword the above sentence to say that the 
> identifiers are not tightly bound to an interface; to provide 
> communication survivability when one interface fails the identifiers 
> must be usable on any interface.

> (I welcome suggestions for how to make that text shorter.)

An identifier continues to function regardless of the state of any one 
interface.




From owner-multi6@ops.ietf.org  Wed Dec  1 22:05:54 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27840
	for <multi6-archive@lists.ietf.org>; Wed, 1 Dec 2004 22:05:53 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD))
	id 1CZhGL-000Fkx-RG
	for multi6-data@psg.com; Thu, 02 Dec 2004 03:04:09 +0000
Received: from [66.163.170.80] (helo=smtp810.mail.sc5.yahoo.com)
	by psg.com with smtp (Exim 4.43 (FreeBSD))
	id 1CZhGL-000FkB-2p
	for multi6@ops.ietf.org; Thu, 02 Dec 2004 03:04:09 +0000
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.17.134 with login)
  by smtp810.mail.sc5.yahoo.com with SMTP; 2 Dec 2004 03:04:07 -0000
Message-ID: <015a01c4d81b$9027caa0$861167c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "marcelo bagnulo braun" <marcelo@it.uc3m.es>
Cc: "Brian E Carpenter" <brc@zurich.ibm.com>, "Multi6" <multi6@ops.ietf.org>
References: <41AC6D70.30204@zurich.ibm.com> <010901c4d74b$02984870$861167c0@adithya> <D62DB0FB-43B3-11D9-97A6-000D93ACD0FE@it>
Subject: Re: mumti6dt drafts as WG drafts?
Date: Wed, 1 Dec 2004 19:03:56 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.1
Sender: owner-multi6@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Marcelo,

I agree that merging HBA may not be a good idea. Perhaps, i should have
stayed away from examples :-) I did not realise earlier that the output of this
WG will be these 5 documents and some other group is going to figure out
producing a solution document. 

-mohan
 

> Brian,
>
> So, the solution architecture document will come later on based on the
> WG documents i guess. What is the rationale behind having it as
> separate documents still ? Having read some of them, i felt that it 
> might be
> good to have some of them at least merged to understand the solution
> better. For example, the first three below (shim, hba and func) can be
> merged.
>

with respect to the HBA draft, imho it would be better to separate the 
security mechanisms used form the protocol itself. I mean imho it is 
not such a good idea to hardcode the security mechanism inside the 
protocol. HBA is, at most, one of the possible security mechanisms for 
multi6 imho. there may and probably will be others. For instance it 
makes sense to support a different security mechanism based in cgas 
(only cga i mean) in order to support mobile environmets, Probably in 
the future new security mechanisms can be defined.
So making a clear distinction between the core multi6 protocol and the 
security mechanism used is good imho

makes sense?

regards, marcelo


> -mohan
>
>> In accordance with the consensus to proceed with the direction
>> proposed by the design team, does anyone object to the next versions
>> of the following drafts being formally adopted as WG drafts?
>> This would mean they have names like draft-ietf-multi6-*
>>
>> Please let us know this week if you object, and why.
>>
>>      Multihoming Level 3 Shim Approach
>>      (draft-nordmark-multi6dt-shim-00.txt)
>>      Hash Based Addresses (HBA)
>>      (draft-bagnulo-multi6dt-hba-00.txt)
>>      Functional decomposition of the M6 protocol
>>      (draft-bagnulo-multi6dt-functional-dec-00.txt)
>>      Failure Detection and Locator Selection in Multi6
>>      (draft-arkko-multi6dt-failure-detection-00.txt)
>>      Multi6 Application Referral Issues
>>      (draft-nordmark-multi6dt-refer-00.txt)
>>
>>
>>     Brian
>>     multi6 co-chair
>>
>





From owner-multi6@ops.ietf.org  Sun Dec  5 00:03:40 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17857
	for <multi6-archive@lists.ietf.org>; Sun, 5 Dec 2004 00:03:39 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD))
	id 1CaoVm-0004yK-4S
	for multi6-data@psg.com; Sun, 05 Dec 2004 05:00:42 +0000
Received: from [66.92.66.68] (helo=cyteen.hactrn.net)
	by psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1CaoVi-0004xm-4D
	for multi6@ops.ietf.org; Sun, 05 Dec 2004 05:00:38 +0000
Received: from hactrn.net (localhost [127.0.0.1])
	by cyteen.hactrn.net (Postfix) with ESMTP id 4BE766C1
	for <multi6@ops.ietf.org>; Sun,  5 Dec 2004 00:00:37 -0500 (EST)
To: multi6@ops.ietf.org
Subject: Weekly posting summary for multi6@ops.ietf.org
From: Rob Austein <sra@hactrn.net>
Date: Sun, 05 Dec 2004 00:00:37 -0500
Message-Id: <20041205050037.4BE766C1@cyteen.hactrn.net>
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=-0.4 required=5.0 tests=ADDRESS_IN_SUBJECT,AWL,
	BAYES_20 autolearn=no version=3.0.1
Sender: owner-multi6@ops.ietf.org
Precedence: bulk

    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 28.00% |    7 | 59.24% |    79116 | brc@zurich.ibm.com
 16.00% |    4 |  9.47% |    12644 | erik.nordmark@sun.com
 16.00% |    4 |  7.94% |    10607 | iljitsch@muada.com
  8.00% |    2 |  5.15% |     6876 | mohanp@sbcglobal.net
  8.00% |    2 |  4.83% |     6451 | jari.arkko@piuha.net
  8.00% |    2 |  3.68% |     4914 | margaret@thingmagic.com
  4.00% |    1 |  2.91% |     3886 | marcelo@it.uc3m.es
  4.00% |    1 |  2.68% |     3575 | kurtis@kurtis.pp.se
  4.00% |    1 |  2.47% |     3303 | shep@alum.mit.edu
  4.00% |    1 |  1.64% |     2189 | sra@hactrn.net
--------+------+--------+----------+------------------------
100.00% |   25 |100.00% |   133561 | Total

Grunchweather Associates provides this automatic summary on an at-whim
basis at the request of the MULTI6 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.



From owner-multi6@ops.ietf.org  Mon Dec  6 09:24:24 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16631
	for <multi6-archive@lists.ietf.org>; Mon, 6 Dec 2004 09:24:23 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD))
	id 1CbJlG-000HUk-Oq
	for multi6-data@psg.com; Mon, 06 Dec 2004 14:22:46 +0000
Received: from [195.212.29.153] (helo=mtagate4.de.ibm.com)
	by psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1CbJlF-000HUU-4m
	for multi6@ops.ietf.org; Mon, 06 Dec 2004 14:22:45 +0000
Received: from d12nrmr1507.megacenter.de.ibm.com (d12nrmr1507.megacenter.de.ibm.com [9.149.167.1])
	by mtagate4.de.ibm.com (8.12.10/8.12.10) with ESMTP id iB6EMivU173220
	for <multi6@ops.ietf.org>; Mon, 6 Dec 2004 14:22:44 GMT
Received: from d12av03.megacenter.de.ibm.com (d12av03.megacenter.de.ibm.com [9.149.165.213])
	by d12nrmr1507.megacenter.de.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id iB6EMbbq122664
	for <multi6@ops.ietf.org>; Mon, 6 Dec 2004 15:22:37 +0100
Received: from d12av03.megacenter.de.ibm.com (loopback [127.0.0.1])
	by d12av03.megacenter.de.ibm.com (8.12.11/8.12.11) with ESMTP id iB6EMh40006320
	for <multi6@ops.ietf.org>; Mon, 6 Dec 2004 15:22:43 +0100
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232])
	by d12av03.megacenter.de.ibm.com (8.12.11/8.12.11) with ESMTP id iB6EMhdr006311
	for <multi6@ops.ietf.org>; Mon, 6 Dec 2004 15:22:43 +0100
Received: from zurich.ibm.com (sig-9-145-249-221.de.ibm.com [9.145.249.221])
	by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id PAA87058
	for <multi6@ops.ietf.org>; Mon, 6 Dec 2004 15:22:31 +0100
Message-ID: <41B46B27.2000509@zurich.ibm.com>
Date: Mon, 06 Dec 2004 15:22:31 +0100
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: Multi6 <multi6@ops.ietf.org>
Subject: Re: mumti6dt drafts as WG drafts?
References: <41AC6D70.30204@zurich.ibm.com>
In-Reply-To: <41AC6D70.30204@zurich.ibm.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.1
Sender: owner-multi6@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

The comments on this didn't amount to significant objections, so
we will adopt the next versions of these drafts as WG drafts.

Authors - please tell the co-chairs what filenames you want
within draft-ietf-multi6-*, so that we can authorize them

    Brian

Brian E Carpenter wrote:
> In accordance with the consensus to proceed with the direction
> proposed by the design team, does anyone object to the next versions
> of the following drafts being formally adopted as WG drafts?
> This would mean they have names like draft-ietf-multi6-*
> 
> Please let us know this week if you object, and why.
> 
>     Multihoming Level 3 Shim Approach
>     (draft-nordmark-multi6dt-shim-00.txt)
>     Hash Based Addresses (HBA)
>     (draft-bagnulo-multi6dt-hba-00.txt)
>     Functional decomposition of the M6 protocol
>     (draft-bagnulo-multi6dt-functional-dec-00.txt)
>     Failure Detection and Locator Selection in Multi6
>     (draft-arkko-multi6dt-failure-detection-00.txt)
>     Multi6 Application Referral Issues
>     (draft-nordmark-multi6dt-refer-00.txt)
> 
> 
>    Brian
>    multi6 co-chair
> 



From owner-multi6@ops.ietf.org  Wed Dec  8 11:15:43 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10197
	for <multi6-archive@lists.ietf.org>; Wed, 8 Dec 2004 11:15:43 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD))
	id 1Cc4Rr-0001Bi-O1
	for multi6-data@psg.com; Wed, 08 Dec 2004 16:13:51 +0000
Received: from [192.71.80.74] (helo=laptop2.kurtis.pp.se)
	by psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1Cc4Ri-0001AN-TW
	for multi6@ops.ietf.org; Wed, 08 Dec 2004 16:13:43 +0000
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by laptop2.kurtis.pp.se (Postfix) with ESMTP id D44FF6C7354
	for <multi6@ops.ietf.org>; Wed,  8 Dec 2004 17:14:05 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v619)
Content-Transfer-Encoding: 7bit
Message-Id: <279455BF-4934-11D9-8D26-000A95928574@kurtis.pp.se>
Content-Type: text/plain; charset=US-ASCII; format=fixed
To: Multi6 List <multi6@ops.ietf.org>
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
Subject: Updated http://ops.ietf.org/multi6
Date: Wed, 8 Dec 2004 17:13:53 +0100
X-Pgp-Rfc2646-Fix: 1
X-Mailer: Apple Mail (2.619)
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,UPPERCASE_25_50 
	autolearn=no version=3.0.1
Sender: owner-multi6@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

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

	

I have updated the site above with the minutes and presentations from 
IETF61. I have also added Francis HBA implementation for download on 
the first page.

Best regards,

- - kurtis -

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.1

iQA/AwUBQbcoS6arNKXTPFCVEQJ9JQCgvIqgIoXxvutSBZhzUZ2P/FL+i/QAoM5r
4fsHEf7NOUgJbamHUC8nXXTi
=JS/O
-----END PGP SIGNATURE-----




From owner-multi6@ops.ietf.org  Sun Dec 12 00:05:03 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA15200
	for <multi6-archive@lists.ietf.org>; Sun, 12 Dec 2004 00:05:02 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD))
	id 1CdLqf-0009nw-Mz
	for multi6-data@psg.com; Sun, 12 Dec 2004 05:00:45 +0000
Received: from [66.92.66.68] (helo=cyteen.hactrn.net)
	by psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1CdLqU-0009md-NM
	for multi6@ops.ietf.org; Sun, 12 Dec 2004 05:00:34 +0000
Received: from hactrn.net (localhost [127.0.0.1])
	by cyteen.hactrn.net (Postfix) with ESMTP id C6CEE3B0
	for <multi6@ops.ietf.org>; Sun, 12 Dec 2004 00:00:33 -0500 (EST)
To: multi6@ops.ietf.org
Subject: Weekly posting summary for multi6@ops.ietf.org
From: Rob Austein <sra@hactrn.net>
Date: Sun, 12 Dec 2004 00:00:33 -0500
Message-Id: <20041212050033.C6CEE3B0@cyteen.hactrn.net>
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=-0.7 required=5.0 tests=ADDRESS_IN_SUBJECT,AWL,
	BAYES_00 autolearn=no version=3.0.1
Sender: owner-multi6@ops.ietf.org
Precedence: bulk

    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 33.33% |    1 | 45.45% |     3681 | brc@zurich.ibm.com
 33.33% |    1 | 30.52% |     2472 | sra@hactrn.net
 33.33% |    1 | 24.03% |     1946 | kurtis@kurtis.pp.se
--------+------+--------+----------+------------------------
100.00% |    3 |100.00% |     8099 | Total

Grunchweather Associates provides this automatic summary on an at-whim
basis at the request of the MULTI6 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.



From owner-multi6@ops.ietf.org  Fri Dec 17 01:15:16 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA28900
	for <multi6-archive@lists.ietf.org>; Fri, 17 Dec 2004 01:15:14 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD))
	id 1CfBKx-000PKh-Lm
	for multi6-data@psg.com; Fri, 17 Dec 2004 06:11:35 +0000
Received: from [159.226.39.7] (helo=ict.ac.cn)
	by psg.com with smtp (Exim 4.43 (FreeBSD))
	id 1CfBKs-000PK3-Kk
	for multi6@ops.ietf.org; Fri, 17 Dec 2004 06:11:31 +0000
Received: (qmail 27923 invoked by uid 507); 17 Dec 2004 06:11:10 -0000
Received: from unknown (HELO ThinkPadX31) (liumin@159.226.39.104)
  by ict.ac.cn with SMTP; 17 Dec 2004 06:11:10 -0000
From: "Liu Min" <liumin@ict.ac.cn>
To: <multi6@ops.ietf.org>
Subject: FW: I-D ACTION:draft-liumin-multi6-loadsharing-00.txt
Date: Fri, 17 Dec 2004 14:11:21 +0800
Message-ID: <000301c4e3ff$3e102e70$4b74a8c0@ThinkPadX31>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0004_01C4E442.4C336E70"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham 
	version=3.0.1
Sender: owner-multi6@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0004_01C4E442.4C336E70
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

This document outlines a potential solution to multihoming in order to
stimulate discussion. Any comments will be appreciated.=20
=20
Best Wishes,
=20

Liu Min
=20
Institute of Computing Technology
Chinese Academy of Sciences
Tel: (86-10) 6256 5533-9240=20
E-mail: liumin@ict.ac.cn


-----Original Message-----
From: i-d-announce-bounces@ietf.org =
[mailto:i-d-announce-bounces@ietf.org]
On Behalf Of Internet-Drafts@ietf.org
Sent: Friday, December 17, 2004 4:55 AM
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-liumin-multi6-loadsharing-00.txt

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


	Title		: Load Sharing in Multihomed Host
	Author(s)	: M. Liu
	Filename	: draft-liumin-multi6-loadsharing-00.txt
	Pages		: 14
	Date		: 2004-12-16
=09
In order to reach the goal of load sharing and traffic engineering in
   multihoming, there must be some mechanism for the local host to
   make a selection of the "best" source locator to used. Obviously the
   selection includes the objective to select a currently viable path.
   What's more, it also includes the objective to select a path with
   larger bandwidth, which is more difficult to judge than reachability.
   In this memo, we propose a simple mechanism to determine the
   availability and bandwidth condition between a multihomed host and
   its ISP. It will help to share the load among multiple paths and
   provide better performance for the host's traffic. This mechanism
   could be part of traffic engineering functions, which could be used
   as the basis of locator selection before initial session
   establishment and aslo could be used to trigger locator swithes to
   avoid loss of connectivity, long delay or large loss rate.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-liumin-multi6-loadsharing-00.tx=
t

To remove yourself from the I-D Announcement list, send a message to=20
i-d-announce-request@ietf.org with the word unsubscribe in the body of =
the
message. =20
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce=20
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the =
username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-liumin-multi6-loadsharing-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html=20
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-liumin-multi6-loadsharing-00.txt".
=09
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
	=09
	=09
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

------=_NextPart_000_0004_01C4E442.4C336E70
Content-Type: Message/External-body;
	name="ATT00027.dat"
Content-Disposition: attachment;
	filename="ATT00027.dat"
Content-Transfer-Encoding: 7bit

Content-Type: text/plain
Content-ID: <2004-12-16162615.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-liumin-multi6-loadsharing-00.txt

------=_NextPart_000_0004_01C4E442.4C336E70
Content-Type: Message/External-body;
	name="draft-liumin-multi6-loadsharing-00.txt"
Content-Disposition: attachment;
	filename="draft-liumin-multi6-loadsharing-00.txt"
Content-Transfer-Encoding: 7bit

Content-Type: text/plain
Content-ID: <2004-12-16162615.I-D@ietf.org>


------=_NextPart_000_0004_01C4E442.4C336E70
Content-Type: text/plain;
	name="ATT00030.txt"
Content-Disposition: attachment;
	filename="ATT00030.txt"
Content-Transfer-Encoding: 7bit

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce

------=_NextPart_000_0004_01C4E442.4C336E70--





From owner-multi6@ops.ietf.org  Sun Dec 19 00:06:10 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17969
	for <multi6-archive@lists.ietf.org>; Sun, 19 Dec 2004 00:06:09 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD))
	id 1CftBT-00075I-1W
	for multi6-data@psg.com; Sun, 19 Dec 2004 05:00:43 +0000
Received: from [66.92.66.68] (helo=cyteen.hactrn.net)
	by psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1CftBN-00074i-Vc
	for multi6@ops.ietf.org; Sun, 19 Dec 2004 05:00:38 +0000
Received: from hactrn.net (localhost [127.0.0.1])
	by cyteen.hactrn.net (Postfix) with ESMTP id 51C8E108
	for <multi6@ops.ietf.org>; Sun, 19 Dec 2004 00:00:33 -0500 (EST)
To: multi6@ops.ietf.org
Subject: Weekly posting summary for multi6@ops.ietf.org
From: Rob Austein <sra@hactrn.net>
Date: Sun, 19 Dec 2004 00:00:33 -0500
Message-Id: <20041219050033.51C8E108@cyteen.hactrn.net>
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=-0.7 required=5.0 tests=ADDRESS_IN_SUBJECT,AWL,
	BAYES_00 autolearn=no version=3.0.1
Sender: owner-multi6@ops.ietf.org
Precedence: bulk

    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 50.00% |    1 | 75.35% |     6324 | liumin@ict.ac.cn
 50.00% |    1 | 24.65% |     2069 | sra@hactrn.net
--------+------+--------+----------+------------------------
100.00% |    2 |100.00% |     8393 | Total

Grunchweather Associates provides this automatic summary on an at-whim
basis at the request of the MULTI6 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.



From owner-multi6@ops.ietf.org  Sun Dec 26 00:03:45 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07412
	for <multi6-archive@lists.ietf.org>; Sun, 26 Dec 2004 00:03:45 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD))
	id 1CiQWN-000Knf-W4
	for multi6-data@psg.com; Sun, 26 Dec 2004 05:00:47 +0000
Received: from [66.92.66.68] (helo=cyteen.hactrn.net)
	by psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1CiQWJ-000KnE-21
	for multi6@ops.ietf.org; Sun, 26 Dec 2004 05:00:43 +0000
Received: from hactrn.net (localhost [127.0.0.1])
	by cyteen.hactrn.net (Postfix) with ESMTP id A9D1A29
	for <multi6@ops.ietf.org>; Sun, 26 Dec 2004 00:00:41 -0500 (EST)
To: multi6@ops.ietf.org
Subject: Weekly posting summary for multi6@ops.ietf.org
From: Rob Austein <sra@hactrn.net>
Date: Sun, 26 Dec 2004 00:00:41 -0500
Message-Id: <20041226050041.A9D1A29@cyteen.hactrn.net>
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=0.6 required=5.0 tests=ADDRESS_IN_SUBJECT,AWL,
	BAYES_50 autolearn=no version=3.0.1
Sender: owner-multi6@ops.ietf.org
Precedence: bulk

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

Grunchweather Associates provides this automatic summary on an at-whim
basis at the request of the MULTI6 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.



From owner-multi6@ops.ietf.org  Mon Dec 27 15:41:50 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20330
	for <multi6-archive@lists.ietf.org>; Mon, 27 Dec 2004 15:41:49 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD))
	id 1Cj1dl-0002VB-Ta
	for multi6-data@psg.com; Mon, 27 Dec 2004 20:38:53 +0000
Received: from [132.151.1.176] (helo=ietf.org)
	by psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1Cj1dg-0002TT-Qx
	for multi6@ops.ietf.org; Mon, 27 Dec 2004 20:38:49 +0000
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20013;
	Mon, 27 Dec 2004 15:38:46 -0500 (EST)
Message-Id: <200412272038.PAA20013@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
Cc: multi6@ops.ietf.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-multi6-functional-dec-00.txt
Date: Mon, 27 Dec 2004 15:38:45 -0500
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,MIME_BOUND_NEXTPART,
	NO_REAL_NAME autolearn=no version=3.0.1
Sender: owner-multi6@ops.ietf.org
Precedence: bulk

--NextPart

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

	Title		: Functional decomposition of the M6 protocol
	Author(s)	: M. Bagnulo, J. Arkko
	Filename	: draft-ietf-multi6-functional-dec-00.txt
	Pages		: 18
	Date		: 2004-12-27
	
In this note we will present a functional decomposition of the M6
   protocol i.e.  the protocol for preserving established communications
   in multihomed environments.  We will do so by describing a protocol
   walkthrough, presenting which functions have to be performed at each
   stage and the messages required to accomplish them.  The functional
   decomposition presented in this draft is based on the general
   functional analysis of multihoming approaches presented in [3].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-multi6-functional-dec-00.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-multi6-functional-dec-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-multi6-functional-dec-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2004-12-27154923.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-multi6-functional-dec-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-multi6-functional-dec-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2004-12-27154923.I-D@ietf.org>

--OtherAccess--

--NextPart--





From owner-multi6@ops.ietf.org  Mon Dec 27 15:41:56 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20348
	for <multi6-archive@lists.ietf.org>; Mon, 27 Dec 2004 15:41:55 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD))
	id 1Cj1dx-0002ad-Sa
	for multi6-data@psg.com; Mon, 27 Dec 2004 20:39:05 +0000
Received: from [132.151.1.176] (helo=ietf.org)
	by psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1Cj1dk-0002Ux-Qk
	for multi6@ops.ietf.org; Mon, 27 Dec 2004 20:38:53 +0000
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20042;
	Mon, 27 Dec 2004 15:38:50 -0500 (EST)
Message-Id: <200412272038.PAA20042@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
Cc: multi6@ops.ietf.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-multi6-hba-00.txt
Date: Mon, 27 Dec 2004 15:38:50 -0500
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,MIME_BOUND_NEXTPART,
	NO_REAL_NAME autolearn=no version=3.0.1
Sender: owner-multi6@ops.ietf.org
Precedence: bulk

--NextPart

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

	Title		: Hash Based Addresses (HBA)
	Author(s)	: M. Bagnulo
	Filename	: draft-ietf-multi6-hba-00.txt
	Pages		: 26
	Date		: 2004-12-27
	
This memo describes a mechanism to provide a secure binding between
   the multiple addresses with different prefixes available to a host
   within a multihomed site.  The main idea is that information about
   the multiple prefixes is included within the addresses themselves.
   This is achieved by generating the interface identifiers of the
   addresses of a host as hashes of the available prefixes and a random
   number.  Then, the multiple addresses are generated by prepending the
   different prefixes to the generated interface identifiers.  The
   result is a set of addresses, called Hash Based Addresses (HBAs),
   that are inherently bound.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-multi6-hba-00.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-multi6-hba-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-multi6-hba-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2004-12-27154930.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-multi6-hba-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-multi6-hba-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2004-12-27154930.I-D@ietf.org>

--OtherAccess--

--NextPart--





