From owner-multi6@ops.ietf.org Sun Jan 2 00:03:38 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA23306 for ; Sun, 2 Jan 2005 00:03:38 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1Ckxr9-0005oz-Ac for multi6-data@psg.com; Sun, 02 Jan 2005 05:00:43 +0000 Received: from [66.92.66.68] (helo=cyteen.hactrn.net) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1Ckxr5-0005nU-F4 for multi6@ops.ietf.org; Sun, 02 Jan 2005 05:00:39 +0000 Received: from hactrn.net (localhost [127.0.0.1]) by cyteen.hactrn.net (Postfix) with ESMTP id AE747694 for ; Sun, 2 Jan 2005 00:00:38 -0500 (EST) To: multi6@ops.ietf.org Subject: Weekly posting summary for multi6@ops.ietf.org From: Rob Austein Date: Sun, 02 Jan 2005 00:00:38 -0500 Message-Id: <20050102050038.AE747694@cyteen.hactrn.net> X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com X-Spam-Status: No, score=0.8 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 --------+------+--------+----------+------------------------ 66.67% | 2 | 84.15% | 10317 | internet-drafts@ietf.org 33.33% | 1 | 15.85% | 1943 | sra@hactrn.net --------+------+--------+----------+------------------------ 100.00% | 3 |100.00% | 12260 | 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 Tue Jan 4 15:34:21 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16154 for ; Tue, 4 Jan 2005 15:34:21 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1ClvLl-0008sh-8w for multi6-data@psg.com; Tue, 04 Jan 2005 20:32:17 +0000 Received: from [132.151.1.176] (helo=ietf.org) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1ClvLY-0008rK-CD for multi6@ops.ietf.org; Tue, 04 Jan 2005 20:32:04 +0000 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15879; Tue, 4 Jan 2005 15:31:58 -0500 (EST) Message-Id: <200501042031.PAA15879@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-v4-multihoming-03.txt Date: Tue, 04 Jan 2005 15:31:58 -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 : IPv4 Multihoming Motivation, Practices and Limitations Author(s) : J. Abley, et al. Filename : draft-ietf-multi6-v4-multihoming-03.txt Pages : 13 Date : 2005-1-4 Multihoming is an essential component of service for many sites which are part of the Internet. This document describes some implementation strategies for multihoming with IPv4 and enumerates features for comparison with other multihoming proposals (particularly those related to IPv6). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-multi6-v4-multihoming-03.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-v4-multihoming-03.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-v4-multihoming-03.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: <2005-1-4153216.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-multi6-v4-multihoming-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-multi6-v4-multihoming-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-1-4153216.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-multi6@ops.ietf.org Wed Jan 5 02:14:21 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17644 for ; Wed, 5 Jan 2005 02:14:21 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1Cm5LW-000ET0-VV for multi6-data@psg.com; Wed, 05 Jan 2005 07:12:42 +0000 Received: from [207.17.137.119] (helo=borg.juniper.net) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1ClbNs-000AyW-7L for multi6@ops.ietf.org; Mon, 03 Jan 2005 23:13:08 +0000 Received: from unknown (HELO alpha.jnpr.net) (172.24.18.126) by borg.juniper.net with ESMTP; 03 Jan 2005 15:13:07 -0800 X-BrightmailFiltered: true X-Ironport-AV: i="3.88,97,1102320000"; d="scan'217,208"; a="114855538:sNHT40987772" Received: from hadron.jnpr.net ([172.24.15.25]) by alpha.jnpr.net with Microsoft SMTPSVC(6.0.3790.211); Mon, 3 Jan 2005 15:13:07 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4F1E9.C8D16E38" Subject: Re: I-D ACTION:draft-arifumi-multi6-sas-policy-dist-00.txt Date: Mon, 3 Jan 2005 15:13:07 -0800 Message-ID: Thread-Topic: Re: I-D ACTION:draft-arifumi-multi6-sas-policy-dist-00.txt Thread-Index: AcTx6ci3cJuJwL9qQoSlcj+bi6xL0g== From: "Changming Liu" To: X-OriginalArrivalTime: 03 Jan 2005 23:13:07.0453 (UTC) FILETIME=[C8F722D0:01C4F1E9] 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=BAYES_00,HTML_40_50, HTML_MESSAGE,HTML_TEXT_AFTER_BODY,HTML_TEXT_AFTER_HTML autolearn=no version=3.0.1 Sender: owner-multi6@ops.ietf.org Precedence: bulk This is a multi-part message in MIME format. ------_=_NextPart_001_01C4F1E9.C8D16E38 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Another case that SAS may be useful is for the firewall tranversal. In case that the ISP deploys some kind of stateful firewall (like in managed firewall services), the forwarding traffic and returning traffic should go through the same firewall or the return traffic may be blocked. If ISP1's assigned address is used as the source address and the traffic is forwarded via ISP2 and the traffic will routed back through ISP1 (the destination is now the source address assigned by ISP1), the firewall in ISP1 will belcok the traffic. SAS will ensure that traffic go through each ISP will have the correct source address so that return traffic can come back from the same ISP. Changming Liu =20 Juniper Networks 1194 N. Mathilda Ave.=20 Sunnyvale, CA 94089-1213 Http: www.juniper.net =20 =20 =20 Arifumi Matsumoto wrote:=20 Hi Brian, thank you for comments. On 2004/11/05, at 21:29, Brian E Carpenter wrote: 3.1 Multihome Site with Global-Closed Mixed Connectivity =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D | Internet | =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D | 2001:db8::/32 | 3ffe:1800::/32 +----+-+ +-+----+ | ISP1 | | ISP2 | (Closed Network) +----+-+ +-+----+ | | 2001:db8:a::/48 | | 3ffe:1800:a::/48 (DHCP-PD') ++-------++ (DHCP-PD') | Gateway | +----+----+ | 2001:db8:a:1::/64 | 3ffe:1800:a:1::/64 | (RA'/DHCP') ------+---+---------- | +-+----+ 2001:db8:a:1:[EUI64] | Host | 3ffe:1800:a:1:[EUI64] +------+ =09 =09 =09 =09 I'm afraid I don't see why this case is of interest to multi6. It is a case where the user site is connected to one ISP and to one WGP (walled garden provider). This is not site multihoming in the sense of multi6. As far as I can see, a longest match is sufficient to tell the host which source prefix to use. =09 =09 =09 Actually longest match isn't sufficient. If a packet is destined for a closed network, an appropriate source address is chosen automatically by longest match. On the other hand, a packet is destined for somewhere in the Internet, it is not always true. For example, when a packet is destined for 3ffe:1801::1 in the Internet, the source address will be the one delegated by ISP2(WGP). In the end, the reply packet for it never returns because of the wall. =09 Yes, correct. It needs to be a bit more complex than longest match - it's exact match on the /32 for ISP2 and you *will* need a priority policy to achieve that. Walled Gardens are bad things anyway, so I wonder if we should solve this? =09 Anyway, I agree that this case may not be the scope of multi6. 3.2 Host with Multiple Home Addresses and Connectivity to Two Global Networks =09 =09 =09 This is the case of interest to multi6. ... Note that the end nodes are notified of an address-selection policy that includes prefix ::/0 by both ISPs, hence a specific source address for ::/0 can't be determined in the Label-Rule judgment phase described in RFC3484. So, these entries for prefix ::/0 won't actually be stored in the policy table, and this policy table won't have any effect on source-address selection for packets that match ::/0. The source address in these cases will be determined by following rules listed in RFC3484, such as longest match with the destination address. =09 =09 =09 Exactly. And it is this case - when two ISPs both offer connectivity to ::/0 - that multi6 has to solve. That seems to be the case you don't help with. =09 =09 =09 Though I didn't include them in this version of my I-D, we are thinking of some other solutions. For those hosts that can support ECMP(equal cost multi-path) or some other special mechanisms for multihoming, it would be helpful to notify all the default routes and all the SAS Policies for default routes as I mentioned in I-D. =09 Well, I think the multi6 conclusion is that we need active reachability checking anyway. The most that SAS policy can do is decide the order in which reachability is checked. Therefore, I still think that SAS policy is a secondary component for multi6. Brian For normal hosts, however, it would be better not to notify multiple routes for the same destination network. So, it should be configurable on routers not to announce multiple routes but to choose one. The configuration will be like prioritizing ISPs. It may be useful to define a new DHCP option for Solicit message that explicitly requests for multiple routes for the same destination network. -- Arifumi Matsumoto Ubiquitous Computing Project NTT Information Sharing Platform Laboratories E-mail: arifumi@nttv6.net ________________________________ Changming Liu =20 Juniper Networks 1194 N. Mathilda Ave.=20 Sunnyvale, CA 94089-1213 Http: www.juniper.net =20 Tel: (408) 936-8010 =20 ------_=_NextPart_001_01C4F1E9.C8D16E38 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message

Another case that SAS may be useful is for the firewall tranversal. In = case that the ISP deploys some kind = of stateful firewall (like in managed = firewall=20 services), the forwarding traffic and returning traffic should go = through the=20 same firewall or the return traffic may be blocked. If ISP1's assigned = address=20 is used as the source address and the traffic is forwarded via ISP2 and = the=20 traffic will routed = back through ISP1 (the=20 destination is now the source address assigned by ISP1), the = firewall in=20 ISP1 will belcok the traffic. SAS will = ensure=20 that traffic go through each ISP will have the correct source address so = that=20 return traffic can come back from the same ISP.

Changming Liu
 
Juniper = Networks
1194 N. Mathilda Ave. =
Sunnyvale, CA = 94089-1213
Http: www.juniper.net
 
 
Arifumi Matsumoto wrote: = 
Hi Brian,
thank you for comments.

On =
2004/11/05, at 21:29, Brian E Carpenter wrote:

3.1 Multihome Site with =
Global-Closed Mixed Connectivity
                  =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
                  |  Internet  |
                  =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
                       |
         2001:db8::/32 |         3ffe:1800::/32
                  +----+-+   +-+----+
                  | ISP1 |   | ISP2 | (Closed Network)
                  +----+-+   +-+----+
                       |       |
       2001:db8:a::/48 |       | 3ffe:1800:a::/48
         (DHCP-PD')   ++-------++   (DHCP-PD')
                      | Gateway |
                      +----+----+
                           |  2001:db8:a:1::/64
                           |  3ffe:1800:a:1::/64
                           |        (RA'/DHCP')
                 ------+---+----------
                       |
                     +-+----+ 2001:db8:a:1:[EUI64]
                     | Host | 3ffe:1800:a:1:[EUI64]
                     +------+




I'm afraid I don't see why this case is of =
interest to multi6.
It is a case where the user site is connected to one ISP and
to one WGP (walled garden provider). This is not site multihoming
in the sense of multi6. As far as I can see, a longest match is
sufficient to tell the host which source prefix to use.



Actually longest match isn't sufficient.
If a packet is destined for a closed network,
an appropriate source address is chosen
automatically by longest match.
On the other hand, a packet is destined for
somewhere in the Internet, it is not always
true. For example, when a packet is destined for
3ffe:1801::1 in the Internet, the source address
will be the one delegated by ISP2(WGP). In the
end, the reply packet for it never returns because
of the wall.


Yes, correct. It needs =
to be a bit more complex than
longest match - it's exact match on the /32 for ISP2
and you *will* need a priority policy to achieve that.

Walled Gardens are bad things =
anyway, so I wonder if
we should solve this?


Anyway, I agree that this case may =
not be the scope
of multi6.


3.2 Host with Multiple Home =
Addresses and Connectivity to Two Global
   Networks



This is the case of interest to =
multi6.

...

     Note that the end nodes are =
notified of an address-selection policy
     that includes prefix ::/0 by both ISPs, hence a specific source
     address for ::/0 can't be determined in the Label-Rule judgment
     phase described in RFC3484. So, these entries for prefix ::/0 won't
     actually be stored in the policy table, and this policy table won't
     have any effect on source-address selection for packets that match
     ::/0. The source address in these cases will be determined by
     following rules listed in RFC3484, such as longest match with the
     destination address.



Exactly. And it is this case - when two ISPs both =
offer connectivity to
::/0 - that multi6 has to solve. That seems to be the case you don't
help with.



Though I didn't include them in this version of my =
I-D,
we are thinking of some other solutions. For those hosts
that can support ECMP(equal cost multi-path) or some
other special mechanisms for multihoming, it would
be helpful to notify all the default routes and all the
SAS Policies for default routes as I mentioned in I-D.


Well, I think the =
multi6 conclusion is that we need active
reachability checking anyway. The most that SAS policy can
do is decide the order in which reachability is checked.

Therefore, I still think that =
SAS policy is a secondary
component for multi6.

   Brian

For normal hosts, however, it would be =
better not to
notify multiple routes for the same destination network.
So, it should be configurable on routers not to announce
multiple routes but to choose one. The configuration will
be like prioritizing ISPs.

It may be =
useful to define a new DHCP option for Solicit
message that explicitly requests for multiple routes for
the same destination network.

--
Arifumi Matsumoto
    Ubiquitous Computing Project
    NTT Information Sharing Platform Laboratories
    E-mail: arifumi@nttv6.net



Changming Liu
 
Juniper = Networks
1194 N. Mathilda Ave. =
Sunnyvale, CA = 94089-1213
Http: www.juniper.net
Tel:  (408) = 936-8010
 
=00 ------_=_NextPart_001_01C4F1E9.C8D16E38-- From owner-multi6@ops.ietf.org Wed Jan 5 03:35:24 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12569 for ; Wed, 5 Jan 2005 03:35:23 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1Cm6bz-000OuO-DG for multi6-data@psg.com; Wed, 05 Jan 2005 08:33:47 +0000 Received: from [195.212.29.150] (helo=mtagate1.de.ibm.com) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1Cm6bg-000OtA-Sa for multi6@ops.ietf.org; Wed, 05 Jan 2005 08:33:29 +0000 Received: from d12nrmr1507.megacenter.de.ibm.com (d12nrmr1507.megacenter.de.ibm.com [9.149.167.1]) by mtagate1.de.ibm.com (8.12.10/8.12.10) with ESMTP id j058XRug212910 for ; Wed, 5 Jan 2005 08:33:27 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 j058Y2Dv149190 for ; Wed, 5 Jan 2005 09:34:02 +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 j058XRb9009124 for ; Wed, 5 Jan 2005 09:33:27 +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 j058XQWS009117 for ; Wed, 5 Jan 2005 09:33:27 +0100 Received: from zurich.ibm.com (sig-9-146-221-174.de.ibm.com [9.146.221.174]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id JAA86588 for ; Wed, 5 Jan 2005 09:33:26 +0100 Message-ID: <41DBA656.1060306@zurich.ibm.com> Date: Wed, 05 Jan 2005 09:33:26 +0100 From: Brian E Carpenter 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@ops.ietf.org Subject: Re: I-D ACTION:draft-ietf-multi6-v4-multihoming-03.txt References: <200501042031.PAA15879@ietf.org> In-Reply-To: <200501042031.PAA15879@ietf.org> 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 This version is intended to resolve all the WG Last Call comments and includes a lot of editorial improvements too. In a day or two it will be forwarded to the IESG for Informational publication, unless anyone objects very quickly. Brian co-chair hat on Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Site Multihoming in IPv6 Working Group of the IETF. > > Title : IPv4 Multihoming Motivation, Practices and Limitations > Author(s) : J. Abley, et al. > Filename : draft-ietf-multi6-v4-multihoming-03.txt > Pages : 13 > Date : 2005-1-4 > > Multihoming is an essential component of service for many sites which > are part of the Internet. This document describes some > implementation strategies for multihoming with IPv4 and enumerates > features for comparison with other multihoming proposals > (particularly those related to IPv6). > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-multi6-v4-multihoming-03.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-v4-multihoming-03.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-v4-multihoming-03.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. > > > ------------------------------------------------------------------------ > > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/i-d-announce From owner-multi6@ops.ietf.org Wed Jan 5 07:42:03 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29012 for ; Wed, 5 Jan 2005 07:42:03 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1CmARU-0000bp-K1 for multi6-data@psg.com; Wed, 05 Jan 2005 12:39:12 +0000 Received: from [195.212.29.136] (helo=mtagate3.uk.ibm.com) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CmARA-0000Ux-RV for multi6@ops.ietf.org; Wed, 05 Jan 2005 12:38:53 +0000 Received: from d06nrmr1507.portsmouth.uk.ibm.com (d06nrmr1507.portsmouth.uk.ibm.com [9.149.38.233]) by mtagate3.uk.ibm.com (8.12.10/8.12.10) with ESMTP id j05Cco5M377586 for ; Wed, 5 Jan 2005 12:38:50 GMT Received: from d06av03.portsmouth.uk.ibm.com (d06av03.portsmouth.uk.ibm.com [9.149.37.213]) by d06nrmr1507.portsmouth.uk.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j05CdCV1068542 for ; Wed, 5 Jan 2005 12:39:12 GMT Received: from d06av03.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av03.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id j05Ccn2K032107 for ; Wed, 5 Jan 2005 12:38:49 GMT Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d06av03.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id j05CcnY8032090 for ; Wed, 5 Jan 2005 12:38:49 GMT Received: from zurich.ibm.com (sig-9-146-221-174.de.ibm.com [9.146.221.174]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id NAA304332 for ; Wed, 5 Jan 2005 13:38:48 +0100 Message-ID: <41DBDFCA.5000201@zurich.ibm.com> Date: Wed, 05 Jan 2005 13:38:34 +0100 From: Brian E Carpenter 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 Subject: Re: I-D ACTION:draft-ietf-multi6-functional-dec-00.txt References: <200412272038.PAA20013@ietf.org> In-Reply-To: <200412272038.PAA20013@ietf.org> 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 Personal comments: Substantive: ------------ I think this is OK to hand over to the proposed successor WG as it is, but I have a few small comments anyway... > 4. Locator set management ... > There are two possible approaches to the addition and removal of > locators: atomic and differential approaches. Atomic approaches > essentially send the complete locators set each time that a variation > in the locator set occurs. In this case, there is only one message > exchange defined i.e. a message that informs about the new locator > set and an acknowledgment message. Differential messages send the > differences between the existing locator set and the new one. In > this case, a message for adding a new locator and another message for > deleting locators have to be defined. Both messages can be > acknowledged. The atomic approach imposes additional overhead, since > all the locator set has to be exchanged each time... On the other hand, the atomic approach doesn't need acknowledgement messages, since it can work like soft state - you simply repeat the atomic message at suitable intervals. That makes it quite a bit simpler. > 6. Removal of M6 session state ... > In the unilateral approach, each node discards the information about > the other node without coordination with the other node based on some > local timers and heuristics. No packet exchange is required for > this. In this case, it would be possible that one of the nodes has > discarded the state while the other node still hasn't. In this case, > an error message may be required to inform about the situation. Again, this is like soft state. I don't think you need an error message when state is lost - you just need to systematically restart the whole M6 procedure, just like when a session is initiated. Editorial: ---------- > 2.1 Initial contact ... > ...then the M6 protocol has to be used even to perform the > initial contact between the two nodes, starting by the capabilities > detection procedure described in section 2.1.2. Do you mean section 3.1? > 3.1.3 Host-Based Dynamic Discovery ... > For instance, lets assume hosts A and B communicate over two separate > links without going through the Internet. Lets further assume the s/let us/lets/ > 3.1.4 Timing > > Capability detection needs to occurr prior to or at the same time as s/occur/occurr/ > 5. Re-homing procedure ... > the Reachability Test is also a mechanism to prevent thrid-party > flooding attacks. s/third/thrid/ > > The Reachability Test exchange includes the following packets: > > Reachability Test (RT) packet: including the random nonce and > maybe information related to the initial key/cookie/hash chain s/a random nonce/the random nonce/ [since this is the first time you mention the nonce] > 7. Security considerations > > The security requirements of each message exchange considered in this > note are detailed in the same section where the message exchange is > analyzed. Add something like: The security threats to be considered are described in [XXX]. Brian From owner-multi6@ops.ietf.org Wed Jan 5 07:45:22 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29246 for ; Wed, 5 Jan 2005 07:45:22 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1CmAX3-0001gl-RM for multi6-data@psg.com; Wed, 05 Jan 2005 12:44:57 +0000 Received: from [195.212.29.135] (helo=mtagate2.uk.ibm.com) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CmAWv-0001fS-4n for multi6@ops.ietf.org; Wed, 05 Jan 2005 12:44:49 +0000 Received: from d06nrmr1507.portsmouth.uk.ibm.com (d06nrmr1507.portsmouth.uk.ibm.com [9.149.38.233]) by mtagate2.uk.ibm.com (8.12.10/8.12.10) with ESMTP id j05CimpN146836 for ; Wed, 5 Jan 2005 12:44:48 GMT Received: from d06av03.portsmouth.uk.ibm.com (d06av03.portsmouth.uk.ibm.com [9.149.37.213]) by d06nrmr1507.portsmouth.uk.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j05CjAV1049624 for ; Wed, 5 Jan 2005 12:45:10 GMT Received: from d06av03.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av03.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id j05Cila1008997 for ; Wed, 5 Jan 2005 12:44:47 GMT Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d06av03.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id j05Cil7l008971 for ; Wed, 5 Jan 2005 12:44:47 GMT Received: from zurich.ibm.com (sig-9-146-221-174.de.ibm.com [9.146.221.174]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id NAA304202 for ; Wed, 5 Jan 2005 13:44:46 +0100 Message-ID: <41DBE131.9030501@zurich.ibm.com> Date: Wed, 05 Jan 2005 13:44:33 +0100 From: Brian E Carpenter 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 Subject: Re: I-D ACTION:draft-ietf-multi6-hba-00.txt References: <200412272038.PAA20042@ietf.org> In-Reply-To: <200412272038.PAA20042@ietf.org> 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 Personal comments: I believe this is also ready to hand over to the future WG. Just a couple of remarks. 1. You don't discuss the DNS at all - it clearly isn't a requirement for the HBA mechanism itself to have any DNS entries, but surely in reality at least one of the addresses will have to go into DNS? 2. A related point - in the discussion in 7.1 of MITM attacks, the attack you describe only makes sense if the other end has no independent check of *any* of the addresses in the address set. If even one of them is (for example) in a trusted AAAA record, a MITM is excluded, I think. Brian From owner-multi6@ops.ietf.org Thu Jan 6 08:01:53 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04837 for ; Thu, 6 Jan 2005 08:01:53 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1CmXEN-0001q1-ST for multi6-data@psg.com; Thu, 06 Jan 2005 12:59:11 +0000 Received: from [171.71.176.71] (helo=sj-iport-2.cisco.com) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CmXEM-0001pn-Up for multi6@ops.ietf.org; Thu, 06 Jan 2005 12:59:10 +0000 Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-2.cisco.com with ESMTP; 06 Jan 2005 05:07:30 -0800 Received: from imail.cisco.com (imail.cisco.com [128.107.200.91]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j06Cx7jw000103; Thu, 6 Jan 2005 04:59:07 -0800 (PST) Received: from [212.254.247.5] (ams-clip-vpn-dhcp306.cisco.com [10.61.65.50]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j06CuPOC000512; Thu, 6 Jan 2005 04:56:25 -0800 Message-ID: <41DD3617.3060406@cisco.com> Date: Thu, 06 Jan 2005 13:59:03 +0100 From: Eliot Lear User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brian E Carpenter CC: Tim Chown , Multi6 Subject: Re: Multi6 WG Last Call (2 of 3) draft-ietf-multi6-things-to-think-about-00.txt References: <4176E3B7.4090806@zurich.ibm.com> <20041028160213.GG15055@login.ecs.soton.ac.uk> <41812616.9090506@cisco.com> <41820461.1020608@zurich.ibm.com> In-Reply-To: <41820461.1020608@zurich.ibm.com> X-Enigmail-Version: 0.89.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs"; t:"1105016187.81553"; x:"432200"; a:"rsa-sha1"; b:"nofws:230"; e:"Iw=="; n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw" "eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU" "tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc="; s:"kZwmMKF/dDJRr15j9pjUZgbmqhLlAZcZmZOO2AqTuhwbSTZHDr5hPn5G8J724" "dj+Q9V1SpkQSvPYZiDdZAQV2vVmVtrXo3hdoNySYv5b53Mf5QGXsrX4SLArMD" "KlUFb8L3UaSt+9zPMZVuy/TjmMRv9A2DSeJSgpn9topwV7X7Q="; c:"Date: Thu, 06 Jan 2005 13:59:03 +0100"; c:"From: Eliot Lear "; c:"Subject: Re: Multi6 WG Last Call (2 of 3) draft-ietf-multi6-things-to" "-think-about-00.txt" IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com"; c:"message from imail.cisco.com verified; " 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=BAYES_20 autolearn=ham version=3.0.1 Sender: owner-multi6@ops.ietf.org Precedence: bulk Content-Transfer-Encoding: 7bit Catching up a bit... Brian E Carpenter wrote: > Will the solution add or change actions during a site renumbering > procedure? As it turns out there is text along these lines in 6.5. New draft out shortly. Eliot From owner-multi6@ops.ietf.org Thu Jan 6 15:48:26 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15057 for ; Thu, 6 Jan 2005 15:48:25 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1CmeX7-000LmN-8Q for multi6-data@psg.com; Thu, 06 Jan 2005 20:47:01 +0000 Received: from [132.151.1.176] (helo=ietf.org) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CmeWv-000LkQ-LS for multi6@ops.ietf.org; Thu, 06 Jan 2005 20:46: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 PAA14895; Thu, 6 Jan 2005 15:46:46 -0500 (EST) Message-Id: <200501062046.PAA14895@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-things-to-think-about-01.txt Date: Thu, 06 Jan 2005 15:46:46 -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 : Things MULTI6 Developers should think about Author(s) : E. Lear Filename : draft-ietf-multi6-things-to-think-about-01.txt Pages : 19 Date : 2005-1-6 This document specifies a set of questions that authors should be prepared to answer as part of a solution to multihoming with IPv6. The questions do not assume that multihoming is the only problem of interest, nor do they demand a more general solution either. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-multi6-things-to-think-about-01.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-things-to-think-about-01.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-things-to-think-about-01.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: <2005-1-6161532.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-multi6-things-to-think-about-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-multi6-things-to-think-about-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-1-6161532.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-multi6@ops.ietf.org Thu Jan 6 15:48:33 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15081 for ; Thu, 6 Jan 2005 15:48:32 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1CmeWx-000Lki-Eq for multi6-data@psg.com; Thu, 06 Jan 2005 20:46:51 +0000 Received: from [132.151.1.176] (helo=ietf.org) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CmeWm-000LjA-Ky for multi6@ops.ietf.org; Thu, 06 Jan 2005 20:46:41 +0000 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14880; Thu, 6 Jan 2005 15:46:37 -0500 (EST) Message-Id: <200501062046.PAA14880@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-architecture-03.txt Date: Thu, 06 Jan 2005 15:46:37 -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 : Architectural Approaches to Multi-Homing for IPv6 Author(s) : G. Huston Filename : draft-ietf-multi6-architecture-03.txt Pages : 38 Date : 2005-1-6 This memo provides an analysis of the architectural aspects of multi-homing support for the IPv6 protocol suite. The purpose of this analysis is to provide a taxonomy for classification of various proposed approaches to multi-homing. It is also an objective of this exercise to identify common aspects of this domain of study, and also to provide a framework that can allow exploration of some of the further implications of various architectural extensions that are intended to support multi-homing. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-multi6-architecture-03.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-architecture-03.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-architecture-03.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: <2005-1-6161526.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-multi6-architecture-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-multi6-architecture-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-1-6161526.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-multi6@ops.ietf.org Fri Jan 7 03:05:41 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23903 for ; Fri, 7 Jan 2005 03:05:40 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1Cmp6p-000BHH-6k for multi6-data@psg.com; Fri, 07 Jan 2005 08:04:35 +0000 Received: from [195.212.29.136] (helo=mtagate3.uk.ibm.com) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1Cmp6n-000BGw-Jt for multi6@ops.ietf.org; Fri, 07 Jan 2005 08:04:34 +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 j0784W5M126868 for ; Fri, 7 Jan 2005 08:04:32 GMT Received: from d06av02.portsmouth.uk.ibm.com (d06av02.portsmouth.uk.ibm.com [9.149.37.228]) by d06nrmr1407.portsmouth.uk.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j0784rDa145856 for ; Fri, 7 Jan 2005 08:04:53 GMT Received: from d06av02.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av02.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id j0784VTw021027 for ; Fri, 7 Jan 2005 08:04:32 GMT Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d06av02.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id j0784Vi7021016 for ; Fri, 7 Jan 2005 08:04:31 GMT Received: from zurich.ibm.com (sig-9-145-130-83.de.ibm.com [9.145.130.83]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id JAA249672 for ; Fri, 7 Jan 2005 09:04:30 +0100 Message-ID: <41DE4278.4090107@zurich.ibm.com> Date: Fri, 07 Jan 2005 09:04:08 +0100 From: Brian E Carpenter 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@ops.ietf.org Subject: Re: I-D ACTION:draft-ietf-multi6-things-to-think-about-01.txt References: <200501062046.PAA14895@ietf.org> In-Reply-To: <200501062046.PAA14895@ietf.org> 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 This version is intended to resolve all the WG Last Call comments. In a day or two it will be forwarded to the IESG for Informational publication, unless anyone objects very quickly. Brian co-chair hat on Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Site Multihoming in IPv6 Working Group of the IETF. > > Title : Things MULTI6 Developers should think about > Author(s) : E. Lear > Filename : draft-ietf-multi6-things-to-think-about-01.txt > Pages : 19 > Date : 2005-1-6 > > This document specifies a set of questions that authors should be > prepared to answer as part of a solution to multihoming with IPv6. > The questions do not assume that multihoming is the only problem of > interest, nor do they demand a more general solution either. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-multi6-things-to-think-about-01.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-things-to-think-about-01.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-things-to-think-about-01.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. From owner-multi6@ops.ietf.org Fri Jan 7 03:05:48 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23931 for ; Fri, 7 Jan 2005 03:05:48 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1Cmp68-000BBT-F2 for multi6-data@psg.com; Fri, 07 Jan 2005 08:03:52 +0000 Received: from [195.212.29.153] (helo=mtagate4.de.ibm.com) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1Cmp65-000BAz-Nk for multi6@ops.ietf.org; Fri, 07 Jan 2005 08:03:50 +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 j0783lvU226486 for ; Fri, 7 Jan 2005 08:03:47 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 j0784LER140738 for ; Fri, 7 Jan 2005 09:04:21 +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 j0783k6a004167 for ; Fri, 7 Jan 2005 09:03:46 +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 j0783k3M004162 for ; Fri, 7 Jan 2005 09:03:46 +0100 Received: from zurich.ibm.com (sig-9-145-130-83.de.ibm.com [9.145.130.83]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id JAA46302 for ; Fri, 7 Jan 2005 09:03:45 +0100 Message-ID: <41DE424B.7070704@zurich.ibm.com> Date: Fri, 07 Jan 2005 09:03:23 +0100 From: Brian E Carpenter 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@ops.ietf.org Subject: Re: I-D ACTION:draft-ietf-multi6-architecture-03.txt References: <200501062046.PAA14880@ietf.org> In-Reply-To: <200501062046.PAA14880@ietf.org> 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 This version is intended to resolve all the WG Last Call comments. In a day or two it will be forwarded to the IESG for Informational publication, unless anyone objects very quickly. Brian co-chair hat on Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Site Multihoming in IPv6 Working Group of the IETF. > > Title : Architectural Approaches to Multi-Homing for IPv6 > Author(s) : G. Huston > Filename : draft-ietf-multi6-architecture-03.txt > Pages : 38 > Date : 2005-1-6 > > This memo provides an analysis of the architectural aspects of > multi-homing support for the IPv6 protocol suite. The purpose of > this analysis is to provide a taxonomy for classification of various > proposed approaches to multi-homing. It is also an objective of this > exercise to identify common aspects of this domain of study, and also > to provide a framework that can allow exploration of some of the > further implications of various architectural extensions that are > intended to support multi-homing. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-multi6-architecture-03.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-architecture-03.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-architecture-03.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. > > > ------------------------------------------------------------------------ > > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/i-d-announce From owner-multi6@ops.ietf.org Fri Jan 7 15:42:43 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22685 for ; Fri, 7 Jan 2005 15:42:42 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1Cn0u1-000BSZ-Om for multi6-data@psg.com; Fri, 07 Jan 2005 20:40:09 +0000 Received: from [132.151.1.176] (helo=ietf.org) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1Cn0tz-000BSK-J5 for multi6@ops.ietf.org; Fri, 07 Jan 2005 20:40:07 +0000 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21594; Fri, 7 Jan 2005 15:40:03 -0500 (EST) Message-Id: <200501072040.PAA21594@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-multihoming-threats-03.txt Date: Fri, 07 Jan 2005 15:39:24 -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 : Threats relating to IPv6 multihoming solutions Author(s) : E. Nordmark Filename : draft-ietf-multi6-multihoming-threats-03.txt Pages : 35 Date : 2005-1-7 This document lists security threats related to IPv6 multihoming. Multihoming can introduce new opportunities to redirect packets to different, unintended IP addresses. The intent is to look at how IPv6 multihoming solutions might make the Internet less secure than the current Internet, without studying any proposed solution but instead looking at threats that are inherent in the problem itself. The threats in this document build upon the threats discovered and discussed as part of the Mobile IPv6 work. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-multi6-multihoming-threats-03.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-multihoming-threats-03.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-multihoming-threats-03.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: <2005-1-7152221.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-multi6-multihoming-threats-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-multi6-multihoming-threats-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-1-7152221.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-multi6@ops.ietf.org Sun Jan 9 00:03:52 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02720 for ; Sun, 9 Jan 2005 00:03:51 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1CnVBv-000Bca-Gf for multi6-data@psg.com; Sun, 09 Jan 2005 05:00:39 +0000 Received: from [66.92.66.68] (helo=cyteen.hactrn.net) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CnVBr-000Bc1-QQ for multi6@ops.ietf.org; Sun, 09 Jan 2005 05:00:35 +0000 Received: from hactrn.net (localhost [127.0.0.1]) by cyteen.hactrn.net (Postfix) with ESMTP id D2536679 for ; Sun, 9 Jan 2005 00:00:34 -0500 (EST) To: multi6@ops.ietf.org Subject: Weekly posting summary for multi6@ops.ietf.org From: Rob Austein Date: Sun, 09 Jan 2005 00:00:34 -0500 Message-Id: <20050109050034.D2536679@cyteen.hactrn.net> X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com X-Spam-Status: No, score=0.3 required=5.0 tests=ADDRESS_IN_SUBJECT,AWL, BAYES_40 autolearn=no version=3.0.1 Sender: owner-multi6@ops.ietf.org Precedence: bulk Messages | Bytes | Who --------+------+--------+----------+------------------------ 41.67% | 5 | 37.29% | 25407 | brc@zurich.ibm.com 33.33% | 4 | 29.76% | 20273 | internet-drafts@ietf.org 8.33% | 1 | 25.11% | 17111 | cliu@juniper.net 8.33% | 1 | 4.83% | 3288 | lear@cisco.com 8.33% | 1 | 3.01% | 2053 | sra@hactrn.net --------+------+--------+----------+------------------------ 100.00% | 12 |100.00% | 68132 | 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 Jan 9 05:12:45 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04138 for ; Sun, 9 Jan 2005 05:12:45 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1Cna1u-000I8R-MB for multi6-data@psg.com; Sun, 09 Jan 2005 10:10:38 +0000 Received: from [195.212.29.137] (helo=mtagate4.uk.ibm.com) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1Cna1r-000I8E-EI for multi6@ops.ietf.org; Sun, 09 Jan 2005 10:10:35 +0000 Received: from d06nrmr1407.portsmouth.uk.ibm.com (d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185]) by mtagate4.uk.ibm.com (8.12.10/8.12.10) with ESMTP id j09AAYSZ170892 for ; Sun, 9 Jan 2005 10:10:34 GMT Received: from d06av04.portsmouth.uk.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 j09AAtDN152312 for ; Sun, 9 Jan 2005 10:10:55 GMT Received: from d06av04.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av04.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id j09AAXnL026487 for ; Sun, 9 Jan 2005 10:10:34 GMT Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d06av04.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id j09AAXH3026483; Sun, 9 Jan 2005 10:10:33 GMT Received: from zurich.ibm.com (sig-9-145-254-43.de.ibm.com [9.145.254.43]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id LAA25150; Sun, 9 Jan 2005 11:10:22 +0100 Message-ID: <41E1030E.5010605@zurich.ibm.com> Date: Sun, 09 Jan 2005 11:10:22 +0100 From: Brian E Carpenter 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@ops.ietf.org CC: Bert Wijnen , David Kessens Subject: Re: I-D ACTION:draft-ietf-multi6-multihoming-threats-03.txt References: <200501072040.PAA21594@ietf.org> In-Reply-To: <200501072040.PAA21594@ietf.org> 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 Please note that this version is intended to resolve IESG comments. Brian Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Site Multihoming in IPv6 Working Group of the IETF. > > Title : Threats relating to IPv6 multihoming solutions > Author(s) : E. Nordmark > Filename : draft-ietf-multi6-multihoming-threats-03.txt > Pages : 35 > Date : 2005-1-7 > > This document lists security threats related to IPv6 multihoming. > Multihoming can introduce new opportunities to redirect packets to > different, unintended IP addresses. > > The intent is to look at how IPv6 multihoming solutions might make > the Internet less secure than the current Internet, without studying > any proposed solution but instead looking at threats that are > inherent in the problem itself. The threats in this document build > upon the threats discovered and discussed as part of the Mobile IPv6 > work. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-multi6-multihoming-threats-03.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-multihoming-threats-03.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-multihoming-threats-03.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. > > > ------------------------------------------------------------------------ > > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/i-d-announce From owner-multi6@ops.ietf.org Sun Jan 9 13:54:02 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29149 for ; Sun, 9 Jan 2005 13:54:02 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1CniAN-000Kkf-G3 for multi6-data@psg.com; Sun, 09 Jan 2005 18:51:55 +0000 Received: from [128.9.160.161] (helo=boreas.isi.edu) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CniAL-000Kk3-FR for multi6@ops.ietf.org; Sun, 09 Jan 2005 18:51:53 +0000 Received: from [192.168.1.47] (lsanca1-ar42-4-61-185-150.lsanca1.dsl-verizon.net [4.61.185.150]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j09IoOQ03907; Sun, 9 Jan 2005 10:50:24 -0800 (PST) Message-ID: <41E17CEC.1080104@isi.edu> Date: Sun, 09 Jan 2005 10:50:20 -0800 From: Joe Touch User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brian E Carpenter CC: multi6@ops.ietf.org, Bert Wijnen , David Kessens Subject: Re: I-D ACTION:draft-ietf-multi6-multihoming-threats-03.txt References: <200501072040.PAA21594@ietf.org> <41E1030E.5010605@zurich.ibm.com> In-Reply-To: <41E1030E.5010605@zurich.ibm.com> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigB3D66C18762AD6E723109789" X-ISI-4-30-3-MailScanner: Found to be clean X-MailScanner-From: touch@isi.edu 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 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigB3D66C18762AD6E723109789 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Is there a summary of these comments and how they were 'resolved'? Brian E Carpenter wrote: > Please note that this version is intended to resolve IESG comments. > > Brian > > Internet-Drafts@ietf.org wrote: > >> A New Internet-Draft is available from the on-line Internet-Drafts >> directories. >> This draft is a work item of the Site Multihoming in IPv6 Working >> Group of the IETF. >> >> Title : Threats relating to IPv6 multihoming solutions >> Author(s) : E. Nordmark >> Filename : draft-ietf-multi6-multihoming-threats-03.txt >> Pages : 35 >> Date : 2005-1-7 >> >> This document lists security threats related to IPv6 multihoming. >> Multihoming can introduce new opportunities to redirect packets to >> different, unintended IP addresses. >> >> The intent is to look at how IPv6 multihoming solutions might make >> the Internet less secure than the current Internet, without studying >> any proposed solution but instead looking at threats that are >> inherent in the problem itself. The threats in this document build >> upon the threats discovered and discussed as part of the Mobile IPv6 >> work. >> >> A URL for this Internet-Draft is: >> http://www.ietf.org/internet-drafts/draft-ietf-multi6-multihoming-threats-03.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-multihoming-threats-03.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-multihoming-threats-03.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. >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> I-D-Announce mailing list >> I-D-Announce@ietf.org >> https://www1.ietf.org/mailman/listinfo/i-d-announce --------------enigB3D66C18762AD6E723109789 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFB4XzsE5f5cImnZrsRAkt3AJ463oOfRoBn+ByQ3RXUxDQTEXSQowCgnyjF P+q+SUx4KgwgeDOdGFgxfMA= =1wU4 -----END PGP SIGNATURE----- --------------enigB3D66C18762AD6E723109789-- From owner-multi6@ops.ietf.org Sun Jan 9 15:00:12 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02329 for ; Sun, 9 Jan 2005 15:00:11 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1CnjDF-0003cn-Co for multi6-data@psg.com; Sun, 09 Jan 2005 19:58:57 +0000 Received: from [204.127.202.56] (helo=sccrmhc12.comcast.net) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CnjDA-0003c2-Hh for multi6@ops.ietf.org; Sun, 09 Jan 2005 19:58:52 +0000 Received: from dfnjgl21 (c-24-1-97-29.client.comcast.net[24.1.97.29]) by comcast.net (sccrmhc12) with SMTP id <2005010919585101200oosi1e>; Sun, 9 Jan 2005 19:58:51 +0000 Message-ID: <047801c4f685$e4cd0060$0400a8c0@DFNJGL21> Reply-To: "Spencer Dawkins" From: "Spencer Dawkins" To: References: <200501072040.PAA21594@ietf.org> <41E1030E.5010605@zurich.ibm.com> <41E17CEC.1080104@isi.edu> Subject: Re: I-D ACTION:draft-ietf-multi6-multihoming-threats-03.txt Date: Sun, 9 Jan 2005 14:00:38 -0600 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 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 Content-Transfer-Encoding: 7bit This wasn't the question Joe asked, but if you are curious about diffs between versions of an ID, there are several sites that present them. I use http://bgp.potaroo.net/ietf/html/xids-wgm.html, which provides diffs from one version to the next, in both single-document and side-by-side flavors. Click on the "sharp" signs to see the diffs. Joe's question was actually what the IESG comments were, and how they were addressed. There is an appendix A ("changes since previous draft") in the document, that says the changes were to address IESG comments, and the ID tracker actually has some detail on IESG comments, at https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=11954&rfc_flag=0. I haven't tried to match all this up yet, but wanted to pass URLs along for other reviewers. Spencer From owner-multi6@ops.ietf.org Mon Jan 10 02:50:06 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26681 for ; Mon, 10 Jan 2005 02:50:06 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1CnuGs-000Dng-AF for multi6-data@psg.com; Mon, 10 Jan 2005 07:47:26 +0000 Received: from [195.212.29.136] (helo=mtagate3.uk.ibm.com) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CnuGp-000DmO-J1 for multi6@ops.ietf.org; Mon, 10 Jan 2005 07:47:24 +0000 Received: from d06nrmr1507.portsmouth.uk.ibm.com (d06nrmr1507.portsmouth.uk.ibm.com [9.149.38.233]) by mtagate3.uk.ibm.com (8.12.10/8.12.10) with ESMTP id j0A7lH5M290810 for ; Mon, 10 Jan 2005 07:47:17 GMT Received: from d06av01.portsmouth.uk.ibm.com (d06av01.portsmouth.uk.ibm.com [9.149.37.212]) by d06nrmr1507.portsmouth.uk.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j0A7lfUj066076 for ; Mon, 10 Jan 2005 07:47:41 GMT Received: from d06av01.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av01.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id j0A7lHn9009040 for ; Mon, 10 Jan 2005 07:47:17 GMT Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d06av01.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id j0A7lGbh009037 for ; Mon, 10 Jan 2005 07:47:17 GMT Received: from zurich.ibm.com (sig-9-145-132-117.de.ibm.com [9.145.132.117]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id IAA77140 for ; Mon, 10 Jan 2005 08:47:16 +0100 Message-ID: <41E23300.6010203@zurich.ibm.com> Date: Mon, 10 Jan 2005 08:47:12 +0100 From: Brian E Carpenter 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@ops.ietf.org Subject: Re: I-D ACTION:draft-ietf-multi6-multihoming-threats-03.txt References: <200501072040.PAA21594@ietf.org> <41E1030E.5010605@zurich.ibm.com> <41E17CEC.1080104@isi.edu> <047801c4f685$e4cd0060$0400a8c0@DFNJGL21> In-Reply-To: <047801c4f685$e4cd0060$0400a8c0@DFNJGL21> 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 I'll leave Erik to respond in detail as the author, but indeed the ID tracker pointer that Spencer gave is the best (in fact, the only) way to view IESG comments. I don't think any of the updates are likely to be contentious. Brian Spencer Dawkins wrote: > This wasn't the question Joe asked, but if you are curious about diffs > between versions of an ID, there are several sites that present them. I > use http://bgp.potaroo.net/ietf/html/xids-wgm.html, which provides diffs > from one version to the next, in both single-document and side-by-side > flavors. Click on the "sharp" signs to see the diffs. > > Joe's question was actually what the IESG comments were, and how they > were addressed. > > There is an appendix A ("changes since previous draft") in the document, > that says the changes were to address IESG comments, and the ID tracker > actually has some detail on IESG comments, at > https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=11954&rfc_flag=0. > > > I haven't tried to match all this up yet, but wanted to pass URLs along > for other reviewers. > > Spencer > > > > From owner-multi6@ops.ietf.org Mon Jan 10 05:11:27 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05476 for ; Mon, 10 Jan 2005 05:11:27 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1CnwV4-0006wn-F5 for multi6-data@psg.com; Mon, 10 Jan 2005 10:10:14 +0000 Received: from [192.18.42.14] (helo=nwkea-mail-2.sun.com) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CnwUt-0006vb-EC for multi6@ops.ietf.org; Mon, 10 Jan 2005 10:10:03 +0000 Received: from bebop.France.Sun.COM ([129.157.174.15]) by nwkea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id j0AA9tpv028956; Mon, 10 Jan 2005 02:09:56 -0800 (PST) Received: from localhost (punchin-nordmark.SFBay.Sun.COM [192.9.61.11]) by bebop.France.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,v2.2) with SMTP id j0AA9m53010727; Mon, 10 Jan 2005 11:09:50 +0100 (MET) Date: Mon, 10 Jan 2005 01:42:52 -0800 (PST) From: Erik Nordmark Reply-To: Erik Nordmark Subject: Re: I-D ACTION:draft-ietf-multi6-multihoming-threats-03.txt To: Joe Touch Cc: Brian E Carpenter , multi6@ops.ietf.org, Bert Wijnen , David Kessens In-Reply-To: "Your message with ID" <41E17CEC.1080104@isi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII 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 > Is there a summary of these comments and how they were 'resolved'? The complete set of IESG comments are in the datatracker The draft contains a change log which indicates how the larger comments were addresses, but doesn't specify the details of all the editorial fixes they asked for. Erik From owner-multi6@ops.ietf.org Mon Jan 10 10:35:22 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26590 for ; Mon, 10 Jan 2005 10:35:22 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1Co1YA-000LXZ-HU for multi6-data@psg.com; Mon, 10 Jan 2005 15:33:46 +0000 Received: from [202.99.23.227] (helo=people.com.cn) by psg.com with smtp (Exim 4.43 (FreeBSD)) id 1Co1Y7-000LXB-MO for multi6@ops.ietf.org; Mon, 10 Jan 2005 15:33:44 +0000 Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jm441e31e1a; Mon, 10 Jan 2005 23:36:23 +0800 Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jmd41ddc55c; Fri, 07 Jan 2005 05:35:48 +0800 Received: from megatron.ietf.org([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jmf41de1b80; Fri, 07 Jan 2005 05:35:40 +0800 Received: from megatron.ietf.org([132.151.6.71]) by people.com.cn(AIMC 2.9.5.8) with SMTP id AISP action; Fri, 07 Jan 2005 05:35:40 +0800 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cmedu-0003py-Hr; Thu, 06 Jan 2005 15:54:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CmeWu-0007rs-Rt for i-d-announce@megatron.ietf.org; Thu, 06 Jan 2005 15:46:48 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14895; Thu, 6 Jan 2005 15:46:46 -0500 (EST) Message-Id: <200501062046.PAA14895@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Thu, 06 Jan 2005 15:46:46 -0500 Cc: multi6@ops.ietf.org Subject: I-D ACTION:draft-ietf-multi6-things-to-think-about-01.txt X-BeenThere: i-d-announce@ietf.org X-Mailman-Version: 2.1.5 Reply-To: internet-drafts@ietf.org List-Id: i-d-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , X-AIMC-AUTH: (null) X-AIMC-MAILFROM: i-d-announce-bounces@ietf.org X-AIMC-AUTH: (null) X-AIMC-MAILFROM: i-d-announce-bounces@ietf.org X-AIMC-AUTH: (null) X-AIMC-MAILFROM: Internet-Drafts@ietf.org X-Auto-Forward: jaglee@people.com.cn jag@kw.com.cn 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 : Things MULTI6 Developers should think about Author(s) : E. Lear Filename : draft-ietf-multi6-things-to-think-about-01.txt Pages : 19 Date : 2005-1-6 This document specifies a set of questions that authors should be prepared to answer as part of a solution to multihoming with IPv6. The questions do not assume that multihoming is the only problem of interest, nor do they demand a more general solution either. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-multi6-things-to-think-about-01.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-things-to-think-about-01.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-things-to-think-about-01.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: <2005-1-6161532.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-multi6-things-to-think-about-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-multi6-things-to-think-about-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-1-6161532.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce --NextPart-- From owner-multi6@ops.ietf.org Tue Jan 11 08:04:10 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20110 for ; Tue, 11 Jan 2005 08:04:10 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1CoLdy-00069l-To for multi6-data@psg.com; Tue, 11 Jan 2005 13:01:06 +0000 Received: from [195.212.29.137] (helo=mtagate4.uk.ibm.com) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CoLdw-00069G-9g for multi6@ops.ietf.org; Tue, 11 Jan 2005 13:01:04 +0000 Received: from d06nrmr1507.portsmouth.uk.ibm.com (d06nrmr1507.portsmouth.uk.ibm.com [9.149.38.233]) by mtagate4.uk.ibm.com (8.12.10/8.12.10) with ESMTP id j0BD11SZ373736 for ; Tue, 11 Jan 2005 13:01:01 GMT Received: from d06av01.portsmouth.uk.ibm.com (d06av01.portsmouth.uk.ibm.com [9.149.37.212]) by d06nrmr1507.portsmouth.uk.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j0BD1Orv074300 for ; Tue, 11 Jan 2005 13:01:25 GMT Received: from d06av01.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av01.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id j0BD10RP021901 for ; Tue, 11 Jan 2005 13:01:00 GMT Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d06av01.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id j0BD0xuP021859; Tue, 11 Jan 2005 13:00:59 GMT Received: from zurich.ibm.com (sig-9-145-251-103.de.ibm.com [9.145.251.103]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id OAA82088; Tue, 11 Jan 2005 14:00:58 +0100 Message-ID: <41E3CE09.5090907@zurich.ibm.com> Date: Tue, 11 Jan 2005 14:00:57 +0100 From: Brian E Carpenter Reply-To: shim6@psg.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 CC: Margaret Wasserman Subject: Mailing list and draft charter for new multihoming BOF/WG Content-Type: multipart/mixed; boundary="------------040300090505060009050907" 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, MIME_SUSPECT_NAME autolearn=ham version=3.0.1 Sender: owner-multi6@ops.ietf.org Precedence: bulk This is a multi-part message in MIME format. --------------040300090505060009050907 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi, As promised, Kurtis and I have drafted a charter for the proposed WG to standardize the IPv6 multihoming shim layer. The (perhaps temporary) mailing list is shim6@psg.com Join by sending a message to majordomo@psg.com containing one line: subscribe shim6 and respond as necessary to the confirmation message. The draft charter is attached. Please DO NOT discuss it on this (multi6) list - if you want to discuss it, please join the shim6 list and discuss it there. Be aware that if you reply to this message, your reply will be sent to the shim6 list. It would be a good idea to subscribe first! We will request a shim6 BOF at the next IETF, and also start the process of forming at WG. But first, we need your comments on the draft charter. Regards Brian and Kurtis P.S. The final three multi6 deliverables were submitted to the IESG today. That's draft-ietf-multi6-v4-multihoming-03 draft-ietf-multi6-architecture-03.txt draft-ietf-multi6-things-to-think-about-01.txt --------------040300090505060009050907 Content-Type: unknown/exe; name="draft-shim6-charter-20050111.txt" Content-Disposition: inline; filename="draft-shim6-charter-20050111.txt" Content-Transfer-Encoding: 7bit Site multiHoming by IPv6 interMediation (shim6) Description of Working Group: The shim6 WG is to produce specfifications for a complete IPv6 site multihoming solutions based on the architecture developed by the IETF multi6 WG. The multi6 WG was tasked with investigating solutions to the site multihoming problem that will allow the global routing system to scale. The outcome of the multi6 WG is a specific network layer shim architecture for addressing and address handling of sites and nodes. This includes switching to different locator addresses when connectivity changes, but without the changes of address being visible to upper layers, which see a fixed Upper Layer Identifier address (ULID). The shim6 WG is to complete this work with the required protocol developments and complete the architecture and security analysis of the required protocols. The background documents to be considered by the WG include: RFC 3582 draft-ietf-multi6-things-to-think-about-01.txt draft-ietf-multi6-multihoming-threats-03.txt The input documents that the WG will use as the basis for its design are: draft-huston-solution-stilltobewritten draft-ietf-multi6-functional-dec-00.txt draft-ietf-multi6-l3shim-00.txt [to be published shortly] draft-ietf-multi6-failure-detection-00.txt [to be published shortly] draft-ietf-multi6-hba-00.txt draft-ietf-multi6-app-refer-00.txt [Comment - We specifically omitted the IPv4 document and Geoff's architecture analysis - we're assuming that will be replaced for the new WG by his solution architecture.] The shim6 WG is to submit, as standards track RFCs, specifications with enough details to allow full interoperable implementations of the shim layer appproach to multihoming as agreed on by the multi6 WG. These implementations should have the ability to take advantage of multihoming without adding to the growth of the global routing table, by using the aggregates already announced by their upstream providers. Since the solution requires state to be maintained at both ends of a communication, the protocol specification and the state machine will be designed somewhat independently. Some state transitions may result from external events such as failure detection rather than from protocol events. More work items and milestones might need to be added at a later date to complete all implementation details needed. In addition to the basic network layer shim solution, the shim6 WG is specifically chartered to do work on o A solution for site exit router selection that works when each ISP uses ingress filtering, i.e. when the chosen site exit needs to be related to the source address chosen by the host. This solution should work whether or not the peer site supports the shim6 protocol. o Explore how congestion control and other QoS and traffic engineering issues may interact with the use of multiple locators at both ends. o Investigate relationship between Upper Layer Identifiers (ULIDs) and Unique Local Addresses. o ICMP error demuxing for locator failure discovery. o If necessary, develop and specify formats and structure for - Cryptographically protected locators - Carrying the flow label across the shim layer defined in the multi6 architecture. The WG will consider whether the proposed model is exposed to any security threats in addition to those documented in draft-ietf-multi6-multihoming-threats-03.txt. In any case, the specifications must specifically refer to all applicable threats and describe how they are handled, with the requirement being that the resulting solution not introduce any threats that make the security any less than in today's Internet. The WG will not consider items outside the above scope, such as interaction with mobility, transport level solutions, or alternative identifier formats. [What other topics are explicitly out of scope?] Milestones MAY 05 First draft of architectural and protocol document MAY 05 First draft on cryptographic locators, if required MAY 05 First draft on state managment SEP 05 WG last-call on architectural/protocol document NOV 05 Submit complete architectural/protocol document to IESG NOV 05 WG last-call on cryptographic locators, if required JAN 06 WG last-call on state management JAN 06 Submit draft on cryptographic locators to the IESG, if required MAR 06 Submit draft on state management to the IESG --------------040300090505060009050907-- From owner-multi6@ops.ietf.org Tue Jan 11 11:16:14 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04760 for ; Tue, 11 Jan 2005 11:16:14 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1CoOfn-000Cig-At for multi6-data@psg.com; Tue, 11 Jan 2005 16:15:11 +0000 Received: from [163.117.136.122] (helo=smtp02.uc3m.es) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CoOff-000CcI-0s for multi6@ops.ietf.org; Tue, 11 Jan 2005 16:15:03 +0000 Received: from smtp02.uc3m.es (localhost [127.0.0.1]) by localhost.uc3m.es (Postfix) with ESMTP id 4F2EF32C17; Tue, 11 Jan 2005 17:15:01 +0100 (CET) Received: from [163.117.139.55] (unknown [163.117.139.55]) by smtp02.uc3m.es (Postfix) with ESMTP id 397D032C30; Tue, 11 Jan 2005 17:15:01 +0100 (CET) In-Reply-To: <41DBE131.9030501@zurich.ibm.com> References: <200412272038.PAA20042@ietf.org> <41DBE131.9030501@zurich.ibm.com> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: Content-Transfer-Encoding: quoted-printable Cc: Multi6 From: marcelo bagnulo braun Subject: Re: I-D ACTION:draft-ietf-multi6-hba-00.txt Date: Tue, 11 Jan 2005 17:15:00 +0100 To: Brian E Carpenter 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 Brian, thanks for the comments. El 05/01/2005, a las 13:44, Brian E Carpenter escribi=F3: > Personal comments: > > I believe this is also ready to hand over to the future WG. > > Just a couple of remarks. > > 1. You don't discuss the DNS at all - it clearly isn't a requirement > for the HBA mechanism itself to have any DNS entries, but surely > in reality at least one of the addresses will have to go into DNS? > i guess so, but i don't see any HBA specific issues w.r.t. to DNS, i=20 guess that they are just like any other global address. Do you think i should state it explicitly in the draft? > 2. A related point - in the discussion in 7.1 of MITM attacks, the > attack you describe only makes sense if the other end has no=20 > independent > check of *any* of the addresses in the address set. If even one of > them is (for example) in a trusted AAAA record, a MITM is excluded, > I think. > good point, i will include this in the next version regards, marcelo > Brian > From owner-multi6@ops.ietf.org Tue Jan 11 11:29:10 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05694 for ; Tue, 11 Jan 2005 11:29:10 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1CoOsb-000Ev7-4E for multi6-data@psg.com; Tue, 11 Jan 2005 16:28:25 +0000 Received: from [163.117.136.122] (helo=smtp02.uc3m.es) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CoOsZ-000Eul-B1 for multi6@ops.ietf.org; Tue, 11 Jan 2005 16:28:23 +0000 Received: from smtp02.uc3m.es (localhost [127.0.0.1]) by localhost.uc3m.es (Postfix) with ESMTP id 42F8632CEC; Tue, 11 Jan 2005 17:28:22 +0100 (CET) Received: from [163.117.139.55] (unknown [163.117.139.55]) by smtp02.uc3m.es (Postfix) with ESMTP id 2AD8C32CD6; Tue, 11 Jan 2005 17:28:22 +0100 (CET) In-Reply-To: <41DBDFCA.5000201@zurich.ibm.com> References: <200412272038.PAA20013@ietf.org> <41DBDFCA.5000201@zurich.ibm.com> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: Content-Transfer-Encoding: quoted-printable Cc: Multi6 From: marcelo bagnulo braun Subject: Re: I-D ACTION:draft-ietf-multi6-functional-dec-00.txt Date: Tue, 11 Jan 2005 17:28:21 +0100 To: Brian E Carpenter 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 Brian, thanks for the comments, see below... El 05/01/2005, a las 13:38, Brian E Carpenter escribi=F3: > Personal comments: > > Substantive: > ------------ > > I think this is OK to hand over to the proposed successor WG as it > is, but I have a few small comments anyway... > >> 4. Locator set management > ... >> There are two possible approaches to the addition and removal of >> locators: atomic and differential approaches. Atomic approaches >> essentially send the complete locators set each time that a=20 >> variation >> in the locator set occurs. In this case, there is only one = message >> exchange defined i.e. a message that informs about the new = locator >> set and an acknowledgment message. Differential messages send the >> differences between the existing locator set and the new one. In >> this case, a message for adding a new locator and another message=20= >> for >> deleting locators have to be defined. Both messages can be >> acknowledged. The atomic approach imposes additional overhead,=20 >> since >> all the locator set has to be exchanged each time... > > On the other hand, the atomic approach doesn't need acknowledgement > messages, since it can work like soft state - you simply repeat the > atomic message at suitable intervals. That makes it quite a bit > simpler. > yes but this would require the periodic exchange of the full locator=20 set. If an ack is used, there is no need to resend the locator set=20 unless there is a change on the set. But in anycase, at this point the draft is just describing options, so=20= i guess we could also discuss these tow options (periodic refresh vs.=20 ack) >> 6. Removal of M6 session state > ... >> In the unilateral approach, each node discards the information=20 >> about >> the other node without coordination with the other node based on=20= >> some >> local timers and heuristics. No packet exchange is required for >> this. In this case, it would be possible that one of the nodes = has >> discarded the state while the other node still hasn't. In this=20 >> case, >> an error message may be required to inform about the situation. > > Again, this is like soft state. I don't think you need an error = message > when state is lost - you just need to systematically restart the whole > M6 procedure, just like when a session is initiated. > so, any message related to a non existent session would be silently=20 discarded? i guess that we should consider how this would affect the path=20 exploration procedure, for instance... i mean, how the end that still=20 has the session state would differentiate the case of a path outage=20 from the case of lack of session state.... i mean , the end that still=20= has the session state may attempt to explore all the possible paths=20 before giving up, or even may retry several rounds will al the=20 locators.... > Editorial: > ---------- > will fix thanks, marcelo >> 2.1 Initial contact > ... >> ...then the M6 protocol has to be used even to perform the >> initial contact between the two nodes, starting by the = capabilities >> detection procedure described in section 2.1.2. > > Do you mean section 3.1? > >> 3.1.3 Host-Based Dynamic Discovery > ... >> For instance, lets assume hosts A and B communicate over two=20 >> separate >> links without going through the Internet. Lets further assume the > > s/let us/lets/ > >> 3.1.4 Timing >> Capability detection needs to occurr prior to or at the same time=20= >> as > > s/occur/occurr/ > >> 5. Re-homing procedure > ... >> the Reachability Test is also a mechanism to prevent thrid-party >> flooding attacks. > > s/third/thrid/ > >> The Reachability Test exchange includes the following packets: >> Reachability Test (RT) packet: including the random nonce and >> maybe information related to the initial key/cookie/hash chain > > s/a random nonce/the random nonce/ > [since this is the first time you mention the nonce] > >> 7. Security considerations >> The security requirements of each message exchange considered in=20= >> this >> note are detailed in the same section where the message exchange = is >> analyzed. > > Add something like: > > The security threats to be considered are described in [XXX]. > > Brian > > > From owner-multi6@ops.ietf.org Tue Jan 11 15:39:41 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24647 for ; Tue, 11 Jan 2005 15:39:41 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1CoSmV-00057v-Su for multi6-data@psg.com; Tue, 11 Jan 2005 20:38:23 +0000 Received: from [132.151.1.176] (helo=ietf.org) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CoSmU-00057c-KZ for multi6@ops.ietf.org; Tue, 11 Jan 2005 20:38:22 +0000 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24556; Tue, 11 Jan 2005 15:38:19 -0500 (EST) Message-Id: <200501112038.PAA24556@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-app-refer-00.txt Date: Tue, 11 Jan 2005 15:38:19 -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 : Multi6 Application Referral Issues Author(s) : E. Nordmark Filename : draft-ietf-multi6-app-refer-00.txt Pages : 12 Date : 2005-1-11 In order to fully solve the scalable multihoming problem there is a need to separate the current IP address functionality into identifiers (which are used to identify e.g., TCP connections) and locators which are used to forward packets in the routing system. Such a separation has an impact on the current use of IP address in the application layer. This document presents these issues for the purposes of stimulating discussions. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-multi6-app-refer-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-app-refer-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-app-refer-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: <2005-1-11160626.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-multi6-app-refer-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-multi6-app-refer-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-1-11160626.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-multi6@ops.ietf.org Wed Jan 12 08:35:18 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12170 for ; Wed, 12 Jan 2005 08:35:18 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1CoidJ-0004TY-S0 for multi6-data@psg.com; Wed, 12 Jan 2005 13:33:57 +0000 Received: from [195.212.29.135] (helo=mtagate2.uk.ibm.com) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CoidI-0004Ro-F3 for multi6@ops.ietf.org; Wed, 12 Jan 2005 13:33:57 +0000 Received: from d06nrmr1407.portsmouth.uk.ibm.com (d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185]) by mtagate2.uk.ibm.com (8.12.10/8.12.10) with ESMTP id j0CDXtpN369986 for ; Wed, 12 Jan 2005 13:33:55 GMT Received: from d06av04.portsmouth.uk.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 j0CDYHBQ139060 for ; Wed, 12 Jan 2005 13:34:17 GMT Received: from d06av04.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av04.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id j0CDXteF008344 for ; Wed, 12 Jan 2005 13:33:55 GMT Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d06av04.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id j0CDXsoO008324; Wed, 12 Jan 2005 13:33:54 GMT Received: from zurich.ibm.com (sig-9-146-218-169.de.ibm.com [9.146.218.169]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id OAA46292; Wed, 12 Jan 2005 14:33:53 +0100 Message-ID: <41E52740.6050309@zurich.ibm.com> Date: Wed, 12 Jan 2005 14:33:52 +0100 From: Brian E Carpenter 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: marcelo bagnulo braun CC: Multi6 Subject: Re: I-D ACTION:draft-ietf-multi6-hba-00.txt References: <200412272038.PAA20042@ietf.org> <41DBE131.9030501@zurich.ibm.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit 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: 8bit marcelo bagnulo braun wrote: > Hi Brian, > > thanks for the comments. > > El 05/01/2005, a las 13:44, Brian E Carpenter escribió: > >> Personal comments: >> >> I believe this is also ready to hand over to the future WG. >> >> Just a couple of remarks. >> >> 1. You don't discuss the DNS at all - it clearly isn't a requirement >> for the HBA mechanism itself to have any DNS entries, but surely >> in reality at least one of the addresses will have to go into DNS? >> > > i guess so, but i don't see any HBA specific issues w.r.t. to DNS, i > guess that they are just like any other global address. > Do you think i should state it explicitly in the draft? If you don't, I will bet other people will ask the same question Brian > >> 2. A related point - in the discussion in 7.1 of MITM attacks, the >> attack you describe only makes sense if the other end has no independent >> check of *any* of the addresses in the address set. If even one of >> them is (for example) in a trusted AAAA record, a MITM is excluded, >> I think. >> > > good point, i will include this in the next version > regards, marcelo > >> Brian >> > > From owner-multi6@ops.ietf.org Wed Jan 12 09:04:19 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14739 for ; Wed, 12 Jan 2005 09:04:19 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1Coj6I-000Avf-Sm for multi6-data@psg.com; Wed, 12 Jan 2005 14:03:54 +0000 Received: from [131.228.20.27] (helo=mgw-x4.nokia.com) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1Coj6F-000AtS-LH for multi6@ops.ietf.org; Wed, 12 Jan 2005 14:03:51 +0000 Received: from esdks002.ntc.nokia.com (esdks002.ntc.nokia.com [172.21.138.121]) by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id j0CE3mT25894; Wed, 12 Jan 2005 16:03:49 +0200 (EET) X-Scanned: Wed, 12 Jan 2005 16:02:39 +0200 Nokia Message Protector V1.3.34 2004121512 - RELEASE Received: (from root@localhost) by esdks002.ntc.nokia.com (8.12.9/8.12.9) id j0CE2dvX031665; Wed, 12 Jan 2005 16:02:39 +0200 Received: from mgw-int1.ntc.nokia.com (172.21.143.96) by esdks002.ntc.nokia.com 00t53PDq; Wed, 12 Jan 2005 16:02:32 EET Received: from esebh002.NOE.Nokia.com (esebh002.ntc.nokia.com [172.21.138.77]) by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id j0CE2GU08039; Wed, 12 Jan 2005 16:02:16 +0200 (EET) Received: from [192.168.80.39] ([192.168.80.39]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Wed, 12 Jan 2005 16:02:12 +0200 From: "John Loughney" Reply-to: "John Loughney" To: "ext Brian E Carpenter" Cc: "marcelo bagnulo braun" , "Multi6" Subject: Re: I-D ACTION:draft-ietf-multi6-hba-00.txt Date: Wed, 12 Jan 2005 16:02:50 +0200 Message-ID: X-Mailer: EPOC Email Version 2.10 MIME-Version: 1.0 Content-Language: i-default Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-OriginalArrivalTime: 12 Jan 2005 14:02:12.0548 (UTC) FILETIME=[506CA840:01C4F8AF] 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: quoted-printable Marcelo, I agree with Brian. You should mention it explicitly. John -- original message -- Subject: Re: I-D ACTION:draft-ietf-multi6-hba-00.txt From: "ext Brian E Carpenter" Date: 01/12/2005 3:33 pm marcelo bagnulo braun wrote: > Hi Brian, >=20 > thanks for the comments. >=20 > El 05/01/2005, a las 13:44, Brian E Carpenter escribi=C3=B3: >=20 >> Personal comments: >> >> I believe this is also ready to hand over to the future WG. >> >> Just a couple of remarks. >> >> 1. You don't discuss the DNS at all - it clearly isn't a = requirement >> for the HBA mechanism itself to have any DNS entries, but surely >> in reality at least one of the addresses will have to go into DNS? >> >=20 > i guess so, but i don't see any HBA specific issues w.r.t. to DNS, i = > guess that they are just like any other global address. > Do you think i should state it explicitly in the draft? If you don't, I will bet other people will ask the same question Brian >=20 >> 2. A related point - in the discussion in 7.1 of MITM attacks, the >> attack you describe only makes sense if the other end has no = independent >> check of *any* of the addresses in the address set. If even one of >> them is (for example) in a trusted AAAA record, a MITM is = excluded, >> I think. >> >=20 > good point, i will include this in the next version > regards, marcelo >=20 >> Brian >> >=20 >=20 From owner-multi6@ops.ietf.org Wed Jan 12 09:21:13 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15783 for ; Wed, 12 Jan 2005 09:21:13 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1CojMj-000E2m-L1 for multi6-data@psg.com; Wed, 12 Jan 2005 14:20:53 +0000 Received: from [195.212.29.134] (helo=mtagate1.uk.ibm.com) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CojMh-000E2U-BJ for multi6@ops.ietf.org; Wed, 12 Jan 2005 14:20:51 +0000 Received: from d06nrmr1507.portsmouth.uk.ibm.com (d06nrmr1507.portsmouth.uk.ibm.com [9.149.38.233]) by mtagate1.uk.ibm.com (8.12.10/8.12.10) with ESMTP id j0CEKnVQ419182 for ; Wed, 12 Jan 2005 14:20:49 GMT Received: from d06av03.portsmouth.uk.ibm.com (d06av03.portsmouth.uk.ibm.com [9.149.37.213]) by d06nrmr1507.portsmouth.uk.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j0CELDP9068418 for ; Wed, 12 Jan 2005 14:21:13 GMT Received: from d06av03.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av03.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id j0CEKmF9027923 for ; Wed, 12 Jan 2005 14:20:48 GMT Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d06av03.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id j0CEKmg2027903; Wed, 12 Jan 2005 14:20:48 GMT Received: from zurich.ibm.com (sig-9-146-218-169.de.ibm.com [9.146.218.169]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id PAA46242; Wed, 12 Jan 2005 15:20:47 +0100 Message-ID: <41E5323E.3020804@zurich.ibm.com> Date: Wed, 12 Jan 2005 15:20:46 +0100 From: Brian E Carpenter 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 , Multi6 Subject: Re: I-D ACTION:draft-ietf-multi6-app-refer-00.txt References: <200501112038.PAA24556@ietf.org> In-Reply-To: <200501112038.PAA24556@ietf.org> 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 Just two points after a quick read: In section 3 you refer to centrally assigned ULAs. They are a *long* way behind locally assigned ULAs in the publication process, and still quite speculative. Also, why not discuss locally assigned ULAs? Since they have a birthday-paradox type of risk of ambiguity, they could be "interesting" if used in referrals, and will likely never have reverse DNS entries. (But that's another WG's problem.) In section 4 you say > ...it also > requires a mechanism by which the application can pass that > information to the protocol stack so that the multi6 protocol layer > has all the alternate locators available when establishing > communication. Thus we need to study the implications of a > setpeerlocators() type of API. If we use HBAs, wouldn't that simply mean passing a CGA Parameter Data Structure as the (opaque) referral object? But of course you can only pass that to a peer that understands it... How do you find out if the peer is multi6-capable? Brian From owner-multi6@ops.ietf.org Thu Jan 13 15:52:13 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14775 for ; Thu, 13 Jan 2005 15:52:12 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1CpBuT-000JNB-ER for multi6-data@psg.com; Thu, 13 Jan 2005 20:49:37 +0000 Received: from [132.151.1.176] (helo=ietf.org) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CpBuS-000JMs-Bt for multi6@ops.ietf.org; Thu, 13 Jan 2005 20:49:36 +0000 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14444; Thu, 13 Jan 2005 15:49:33 -0500 (EST) Message-Id: <200501132049.PAA14444@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-l3shim-00.txt Date: Thu, 13 Jan 2005 15:49:33 -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 : Multihoming L3 Shim Approach Author(s) : E. Nordmark, M. Bagnulo Filename : draft-ietf-multi6-l3shim-00.txt Pages : 27 Date : 2005-1-13 This document specifies a particular approach to IPv6 multihoming. The approach is based on using a multi6 shim placed between the IP endpoint sublayer and the IP routing sublayer, and, at least initially, using routable IP locators as the identifiers visible above the shim layer. The approach does not introduce a "stack name" type of identifier, instead it ensures that all upper layer protocols can operate unmodified in a multihomed setting while still seeing a stable IPv6 address. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-multi6-l3shim-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-l3shim-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-l3shim-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: <2005-1-13153532.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-multi6-l3shim-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-multi6-l3shim-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-1-13153532.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-multi6@ops.ietf.org Fri Jan 14 16:01:52 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17349 for ; Fri, 14 Jan 2005 16:01:52 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1CpYX1-0005JG-FQ for multi6-data@psg.com; Fri, 14 Jan 2005 20:58:55 +0000 Received: from [147.67.3.199] (helo=is3smtp04.cec.eu.int) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CpYX0-0005Iy-9Y for multi6@ops.ietf.org; Fri, 14 Jan 2005 20:58:54 +0000 Received: from mail pickup service by is3smtp04.cec.eu.int with Microsoft SMTPSVC; Fri, 14 Jan 2005 21:55:30 +0100 Received: from megatron.ietf.org ([132.151.6.71]) by is3smtp03.cec.eu.int with Microsoft SMTPSVC(5.0.2195.6713); Thu, 13 Jan 2005 22:42:44 +0100 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CpC1G-0001Ke-T8; Thu, 13 Jan 2005 15:56:38 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CpBuR-0005kk-Lk for i-d-announce@megatron.ietf.org; Thu, 13 Jan 2005 15:49:35 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14444; Thu, 13 Jan 2005 15:49:33 -0500 (EST) Message-Id: <200501132049.PAA14444@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Thu, 13 Jan 2005 15:49:33 -0500 Cc: multi6@ops.ietf.org Subject: I-D ACTION:draft-ietf-multi6-l3shim-00.txt X-BeenThere: i-d-announce@ietf.org X-Mailman-Version: 2.1.5 Reply-To: internet-drafts@ietf.org List-Id: i-d-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , X-OriginalArrivalTime: 13 Jan 2005 21:42:44.0609 (UTC) FILETIME=[D0D44F10:01C4F9B8] 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 : Multihoming L3 Shim Approach Author(s) : E. Nordmark, M. Bagnulo Filename : draft-ietf-multi6-l3shim-00.txt Pages : 27 Date : 2005-1-13 This document specifies a particular approach to IPv6 multihoming. The approach is based on using a multi6 shim placed between the IP endpoint sublayer and the IP routing sublayer, and, at least initially, using routable IP locators as the identifiers visible above the shim layer. The approach does not introduce a "stack name" type of identifier, instead it ensures that all upper layer protocols can operate unmodified in a multihomed setting while still seeing a stable IPv6 address. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-multi6-l3shim-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-l3shim-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-l3shim-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: <2005-1-13153532.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-multi6-l3shim-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-multi6-l3shim-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-1-13153532.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce --NextPart-- From owner-multi6@ops.ietf.org Sun Jan 16 00:03:24 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19900 for ; Sun, 16 Jan 2005 00:03:23 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1Cq2Wq-000Fu9-73 for multi6-data@psg.com; Sun, 16 Jan 2005 05:00:44 +0000 Received: from [66.92.66.68] (helo=cyteen.hactrn.net) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1Cq2Wm-000Fti-3n for multi6@ops.ietf.org; Sun, 16 Jan 2005 05:00:40 +0000 Received: from hactrn.net (localhost [127.0.0.1]) by cyteen.hactrn.net (Postfix) with ESMTP id 2771B709 for ; Sun, 16 Jan 2005 00:00:39 -0500 (EST) To: multi6@ops.ietf.org Subject: Weekly posting summary for multi6@ops.ietf.org From: Rob Austein Date: Sun, 16 Jan 2005 00:00:39 -0500 Message-Id: <20050116050039.2771B709@cyteen.hactrn.net> X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com X-Spam-Status: No, score=-0.2 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 --------+------+--------+----------+------------------------ 35.71% | 5 | 41.35% | 25649 | brc@zurich.ibm.com 14.29% | 2 | 16.35% | 10144 | internet-drafts@ietf.org 14.29% | 2 | 14.54% | 9016 | marcelo@it.uc3m.es 7.14% | 1 | 9.80% | 6078 | touch@isi.edu 7.14% | 1 | 6.26% | 3883 | john.loughney@nokia.com 7.14% | 1 | 4.29% | 2662 | spencer@mcsr-labs.org 7.14% | 1 | 3.83% | 2377 | erik.nordmark@sun.com 7.14% | 1 | 3.57% | 2216 | sra@hactrn.net --------+------+--------+----------+------------------------ 100.00% | 14 |100.00% | 62025 | 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 Jan 17 03:47:13 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA17459 for ; Mon, 17 Jan 2005 03:47:13 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1CqSV8-000BXb-Kr for multi6-data@psg.com; Mon, 17 Jan 2005 08:44:42 +0000 Received: from [131.228.20.22] (helo=mgw-x2.nokia.com) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CqSV7-000BXC-6y for multi6@ops.ietf.org; Mon, 17 Jan 2005 08:44:41 +0000 Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120]) by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id j0H8icE18896 for ; Mon, 17 Jan 2005 10:44:39 +0200 (EET) X-Scanned: Mon, 17 Jan 2005 10:51:41 +0200 Nokia Message Protector V1.3.34 2004121512 - RELEASE Received: (from root@localhost) by esdks001.ntc.nokia.com (8.12.9/8.12.9) id j0H8pfgg029683 for ; Mon, 17 Jan 2005 10:51:41 +0200 Received: from mgw-int1.ntc.nokia.com (172.21.143.96) by esdks001.ntc.nokia.com 00t8SfCh; Mon, 17 Jan 2005 10:51:40 EET Received: from esebh003.NOE.Nokia.com (esebh003.ntc.nokia.com [172.21.138.82]) by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id j0H8gTU12800 for ; Mon, 17 Jan 2005 10:42:29 +0200 (EET) Received: from [172.21.50.145] ([172.21.50.145]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Mon, 17 Jan 2005 10:42:25 +0200 Subject: multi6-functional-dec and re-homing From: Pasi Sarolahti To: multi6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-qOyfOOMC24E52ojClaVz" Organization: Nokia Research Center Message-Id: <1105951345.17012.31.camel@siddha.research.nokia.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Mon, 17 Jan 2005 10:42:25 +0200 X-OriginalArrivalTime: 17 Jan 2005 08:42:25.0503 (UTC) FILETIME=[781EAEF0:01C4FC70] 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 --=-qOyfOOMC24E52ojClaVz Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Folks, I was browsing the re-homing section of draft-ietf-multi6-functional-dec-00.txt, and currently it says the following: "...The reason for a re-homing is essentially that the current locator pair is no longer working. The re-homing procedure involves detecting that the locator pair currently in use is no longer working..." I think it would be good if the draft supported also scenarios where the current locator pair continues working, but changing the current locator pair becomes desirable due to availability of some more preferred access path, for example because the current path is much slower or more expensive than the newly available path. So what would you think if the above text would be replaced with something like the following? "The re-homing procedure is initiated when a new locator pair is to be used for the communication, and it can take place when there is a change in connectivity between the site and its transit providers. The re-homing procedure involves detecting a change in the site connectivity (for example, detecting that the current locator pair is no longer working), ...." This would support a larger set of possible re-homing scenarios, and I think it is compatible with the wordings of re-homing definition in draft-ietf-multi6-architecture-03.txt. I had a short off-list mail exchange with Marcelo and Jari and they agreed, but recommended to solicit the list opinion as well. Any thoughts? Thanks, - Pasi --=-qOyfOOMC24E52ojClaVz Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBB63pxoNa7NH1G2csRAihnAJwLJXj7rCc1XGkI83KUu/3PUh8wlwCfW4on FT5l3Gf7wAlnig8ODaE6Vu8= =AVpX -----END PGP SIGNATURE----- --=-qOyfOOMC24E52ojClaVz-- From owner-multi6@ops.ietf.org Mon Jan 17 04:41:34 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20439 for ; Mon, 17 Jan 2005 04:41:33 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1CqTNf-000HGY-2Y for multi6-data@psg.com; Mon, 17 Jan 2005 09:41:03 +0000 Received: from [193.0.3.220] (helo=laptop2.kurtis.pp.se) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CqTNb-000HGE-KH for multi6@ops.ietf.org; Mon, 17 Jan 2005 09:41:00 +0000 Received: from [127.0.0.1] (localhost [127.0.0.1]) by laptop2.kurtis.pp.se (Postfix) with ESMTP id 70B977241F8; Mon, 17 Jan 2005 10:42:18 +0100 (CET) In-Reply-To: <1105951345.17012.31.camel@siddha.research.nokia.com> References: <1105951345.17012.31.camel@siddha.research.nokia.com> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=fixed Message-Id: <0BA4D511-686C-11D9-A357-000A95928574@kurtis.pp.se> Content-Transfer-Encoding: 7bit Cc: multi6 From: Kurt Erik Lindqvist Subject: Re: multi6-functional-dec and re-homing Date: Mon, 17 Jan 2005 10:42:04 +0100 To: Pasi Sarolahti 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 2005-01-17, at 09.42, Pasi Sarolahti wrote: > This would support a larger set of possible re-homing scenarios, and I > think it is compatible with the wordings of re-homing definition in > draft-ietf-multi6-architecture-03.txt. > > I had a short off-list mail exchange with Marcelo and Jari and they > agreed, but recommended to solicit the list opinion as well. I have no objections to the text leaving this possibility open, but I have some more concerns about actually implementing this. - - kurtis - -----BEGIN PGP SIGNATURE----- Version: PGP 8.1 iQA/AwUBQeuIc6arNKXTPFCVEQIUnACeKWf8/4mCVNcip5BWNOGqfkYikd4AoMgU ZEpGXY8xns3oCTZJ1zsZj713 =KSV/ -----END PGP SIGNATURE----- From owner-multi6@ops.ietf.org Mon Jan 17 05:37:35 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24073 for ; Mon, 17 Jan 2005 05:37:34 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1CqUFT-000NWf-SL for multi6-data@psg.com; Mon, 17 Jan 2005 10:36:39 +0000 Received: from [195.212.29.150] (helo=mtagate1.de.ibm.com) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CqUFS-000NVY-8i for multi6@ops.ietf.org; Mon, 17 Jan 2005 10:36:38 +0000 Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate1.de.ibm.com (8.12.10/8.12.10) with ESMTP id j0HAaaug191744 for ; Mon, 17 Jan 2005 10:36:36 GMT Received: from d12av02.megacenter.de.ibm.com (d12av02.megacenter.de.ibm.com [9.149.165.228]) by d12nrmr1607.megacenter.de.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j0HAbX1e145902 for ; Mon, 17 Jan 2005 11:37:33 +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 j0HAaaJJ018912 for ; Mon, 17 Jan 2005 11:36:36 +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 j0HAaZiQ018874; Mon, 17 Jan 2005 11:36:35 +0100 Received: from zurich.ibm.com (sig-9-145-250-216.de.ibm.com [9.145.250.216]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id LAA92740; Mon, 17 Jan 2005 11:36:34 +0100 Message-ID: <41EB9531.6030604@zurich.ibm.com> Date: Mon, 17 Jan 2005 11:36:33 +0100 From: Brian E Carpenter 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: Kurt Erik Lindqvist CC: Pasi Sarolahti , multi6 Subject: Re: multi6-functional-dec and re-homing References: <1105951345.17012.31.camel@siddha.research.nokia.com> <0BA4D511-686C-11D9-A357-000A95928574@kurtis.pp.se> In-Reply-To: <0BA4D511-686C-11D9-A357-000A95928574@kurtis.pp.se> 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 Kurt Erik Lindqvist wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > On 2005-01-17, at 09.42, Pasi Sarolahti wrote: > > >>This would support a larger set of possible re-homing scenarios, and I >>think it is compatible with the wordings of re-homing definition in >>draft-ietf-multi6-architecture-03.txt. >> >>I had a short off-list mail exchange with Marcelo and Jari and they >>agreed, but recommended to solicit the list opinion as well. > > > I have no objections to the text leaving this possibility open, ditto > but I > have some more concerns about actually implementing this. In a sense, it's to leave this door open that I've been arguing over on shim6 that we should separate the state machine (and by implication, its APIs) from the shim6 protocol. Brian From owner-multi6@ops.ietf.org Mon Jan 17 06:21:58 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26267 for ; Mon, 17 Jan 2005 06:21:58 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1CqUus-0002FT-88 for multi6-data@psg.com; Mon, 17 Jan 2005 11:19:26 +0000 Received: from [131.228.20.27] (helo=mgw-x4.nokia.com) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CqUuq-0002F9-UT; Mon, 17 Jan 2005 11:19:25 +0000 Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159]) by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id j0HBJLc22365; Mon, 17 Jan 2005 13:19:22 +0200 (EET) X-Scanned: Mon, 17 Jan 2005 13:17:51 +0200 Nokia Message Protector V1.3.34 2004121512 - RELEASE Received: (from root@localhost) by esdks004.ntc.nokia.com (8.12.9/8.12.9) id j0HBHpEb028355; Mon, 17 Jan 2005 13:17:51 +0200 Received: from mgw-int1.ntc.nokia.com (172.21.143.96) by esdks004.ntc.nokia.com 00ZEjADo; Mon, 17 Jan 2005 13:17:50 EET Received: from esebh001.NOE.Nokia.com (esebh001.ntc.nokia.com [172.21.138.28]) by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id j0HBHYU05408; Mon, 17 Jan 2005 13:17:34 +0200 (EET) Received: from esebe009.NOE.Nokia.com ([172.21.138.41]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Mon, 17 Jan 2005 13:17:30 +0200 Received: from esebe105.NOE.Nokia.com ([172.21.143.53]) by esebe009.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Mon, 17 Jan 2005 13:17:29 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: multi6-functional-dec and re-homing Date: Mon, 17 Jan 2005 13:17:28 +0200 Message-ID: Thread-Topic: multi6-functional-dec and re-homing Thread-Index: AcT8hPSsFDiY3St/QT6zIwpkptIjnAAAK/qA From: To: , Cc: , , X-OriginalArrivalTime: 17 Jan 2005 11:17:29.0674 (UTC) FILETIME=[21D682A0:01C4FC86] 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,NO_REAL_NAME autolearn=no version=3.0.1 Sender: owner-multi6@ops.ietf.org Precedence: bulk Content-Transfer-Encoding: quoted-printable Brian, A short comment: > >>This would support a larger set of possible re-homing scenarios, and = I > >>think it is compatible with the wordings of re-homing definition in > >>draft-ietf-multi6-architecture-03.txt. > >> > >>I had a short off-list mail exchange with Marcelo and Jari and they > >>agreed, but recommended to solicit the list opinion as well. > >=20 > >=20 > > I have no objections to the text leaving this possibility open, >=20 > ditto >=20 > > but I=20 > > have some more concerns about actually implementing this. >=20 > In a sense, it's to leave this door open that I've been arguing > over on shim6 that we should separate the state machine (and by > implication, its APIs) from the shim6 protocol. This is really a shim6 discussion, but if that is what you mean by=20 the charter text, then I think the charter needs to be clarified. It sounds like you are talking about the re-homing events or triggers where, which I think should be documented seperate. However, in a classical state machine, you don't need to detail the events or triggers which cause the state change, but just the transitions between the states. I would support a document (in shim6) that covers the different re-homing events, etc. John From owner-multi6@ops.ietf.org Mon Jan 17 06:27:22 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26461 for ; Mon, 17 Jan 2005 06:27:21 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1CqV2G-0002yK-K1 for multi6-data@psg.com; Mon, 17 Jan 2005 11:27:04 +0000 Received: from [131.228.20.22] (helo=mgw-x2.nokia.com) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CqV2F-0002y5-Ki for multi6@ops.ietf.org; Mon, 17 Jan 2005 11:27:03 +0000 Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159]) by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id j0HBQxE27858; Mon, 17 Jan 2005 13:27:00 +0200 (EET) X-Scanned: Mon, 17 Jan 2005 13:26:28 +0200 Nokia Message Protector V1.3.34 2004121512 - RELEASE Received: (from root@localhost) by esdks004.ntc.nokia.com (8.12.9/8.12.9) id j0HBQSdQ024300; Mon, 17 Jan 2005 13:26:28 +0200 Received: from mgw-int1.ntc.nokia.com (172.21.143.96) by esdks004.ntc.nokia.com 00259JOZ; Mon, 17 Jan 2005 13:26:27 EET Received: from esebh003.NOE.Nokia.com (esebh003.ntc.nokia.com [172.21.138.82]) by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id j0HBQ3U14631; Mon, 17 Jan 2005 13:26:03 +0200 (EET) Received: from esebe016.NOE.Nokia.com ([172.21.138.55]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Mon, 17 Jan 2005 13:26:02 +0200 Received: from esebe105.NOE.Nokia.com ([172.21.143.53]) by esebe016.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Mon, 17 Jan 2005 13:26:02 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: multi6-functional-dec and re-homing Date: Mon, 17 Jan 2005 13:26:00 +0200 Message-ID: Thread-Topic: multi6-functional-dec and re-homing Thread-Index: AcT8ebzVFvO/IB1KSbm6uBebEAqzfgADNG7w From: To: , Cc: X-OriginalArrivalTime: 17 Jan 2005 11:26:02.0749 (UTC) FILETIME=[53A78AD0:01C4FC87] 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,NO_REAL_NAME autolearn=no version=3.0.1 Sender: owner-multi6@ops.ietf.org Precedence: bulk Content-Transfer-Encoding: quoted-printable Kurtis, > > This would support a larger set of possible re-homing scenarios, and = I > > think it is compatible with the wordings of re-homing definition in > > draft-ietf-multi6-architecture-03.txt. > > > > I had a short off-list mail exchange with Marcelo and Jari and they > > agreed, but recommended to solicit the list opinion as well. >=20 > I have no objections to the text leaving this possibility open, but I=20 > have some more concerns about actually implementing this. I think we discussed this at the interim last June, to some extent. I = think that defining what would be a 'more prefered path' would be. However, = that could be based on local policy and out of scope for standardizing. So, = in summary, I would support the text. John From owner-multi6@ops.ietf.org Fri Jan 21 00:37:17 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18756 for ; Fri, 21 Jan 2005 00:37:16 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1CrrQa-000Ca6-Gu for multi6-data@psg.com; Fri, 21 Jan 2005 05:33:48 +0000 Received: from [131.228.20.21] (helo=mgw-x1.nokia.com) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CrrQZ-000CZr-AC for multi6@ops.ietf.org; Fri, 21 Jan 2005 05:33:47 +0000 Received: from esdks003.ntc.nokia.com (esdks003.ntc.nokia.com [172.21.138.158]) by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id j0L5XfO15112; Fri, 21 Jan 2005 07:33:42 +0200 (EET) X-Scanned: Fri, 21 Jan 2005 07:32:30 +0200 Nokia Message Protector V1.3.34 2004121512 - RELEASE Received: (from root@localhost) by esdks003.ntc.nokia.com (8.12.9/8.12.9) id j0L5WUmj018404; Fri, 21 Jan 2005 07:32:30 +0200 Received: from mgw-int1.ntc.nokia.com (172.21.143.96) by esdks003.ntc.nokia.com 001ZnGYO; Fri, 21 Jan 2005 07:32:29 EET Received: from esebh001.NOE.Nokia.com (esebh001.ntc.nokia.com [172.21.138.28]) by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id j0L5WIU26506; Fri, 21 Jan 2005 07:32:18 +0200 (EET) Received: from dadhcp-172019068136.americas.nokia.com ([10.241.59.107]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Fri, 21 Jan 2005 07:32:17 +0200 Received: from dadhcp-172019068136.americas.nokia.com (localhost.localdomain [127.0.0.1]) by dadhcp-172019068136.americas.nokia.com (8.12.11/8.12.11) with ESMTP id j0L5WEXk009005; Thu, 20 Jan 2005 21:32:15 -0800 Received: (from david@localhost) by dadhcp-172019068136.americas.nokia.com (8.12.11/8.12.11/Submit) id j0L5W87q008995; Thu, 20 Jan 2005 21:32:08 -0800 Date: Thu, 20 Jan 2005 21:32:07 -0800 From: David Kessens To: multi6@ops.ietf.org Cc: Kurt Erik Lindqvist , Brian E Carpenter Subject: IESG evaluation of multi6 documents Message-ID: <20050121053207.GE6344@nokia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-OriginalArrivalTime: 21 Jan 2005 05:32:18.0088 (UTC) FILETIME=[926C4A80:01C4FF7A] 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 Please see below for an update on the three multi6 documents that we had on the IESG telechat agenda today. The following documents were approved: draft-ietf-multi6-things-to-think-about (Informational) draft-ietf-multi6-v4-multihoming (Informational) The following document was deferred for discussion during the next telechat in two weeks since several ADs requested some additional time to do a proper review: draft-ietf-multi6-architecture (Informational) I would like to thank everybody for all the work on these documents. We got quite a bit of positive feedback regarding the overall quality of all documents. David Kessens --- From owner-multi6@ops.ietf.org Sun Jan 23 00:04:29 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04182 for ; Sun, 23 Jan 2005 00:04:29 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1CsZrf-0003tr-PH for multi6-data@psg.com; Sun, 23 Jan 2005 05:00:43 +0000 Received: from [66.92.66.68] (helo=cyteen.hactrn.net) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CsZrd-0003tX-Ls for multi6@ops.ietf.org; Sun, 23 Jan 2005 05:00:41 +0000 Received: from hactrn.net (localhost [127.0.0.1]) by cyteen.hactrn.net (Postfix) with ESMTP id 18F4272C for ; Sun, 23 Jan 2005 00:00:41 -0500 (EST) To: multi6@ops.ietf.org Subject: Weekly posting summary for multi6@ops.ietf.org From: Rob Austein Date: Sun, 23 Jan 2005 00:00:41 -0500 Message-Id: <20050123050041.18F4272C@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_50 autolearn=no version=3.0.1 Sender: owner-multi6@ops.ietf.org Precedence: bulk Messages | Bytes | Who --------+------+--------+----------+------------------------ 28.57% | 2 | 31.33% | 7487 | john.loughney@nokia.com 14.29% | 1 | 19.46% | 4651 | pasi.sarolahti@nokia.com 14.29% | 1 | 14.80% | 3537 | brc@zurich.ibm.com 14.29% | 1 | 14.25% | 3406 | david.kessens@nokia.com 14.29% | 1 | 10.13% | 2421 | kurtis@kurtis.pp.se 14.29% | 1 | 10.03% | 2396 | sra@hactrn.net --------+------+--------+----------+------------------------ 100.00% | 7 |100.00% | 23898 | 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 Thu Jan 27 07:03:21 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23020 for ; Thu, 27 Jan 2005 07:03:21 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1Cu8IF-000Aff-No for multi6-data@psg.com; Thu, 27 Jan 2005 11:58:35 +0000 Received: from [148.88.0.66] (helo=errol.lancs.ac.uk) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1Cu8IC-000Aei-BV for multi6@ops.ietf.org; Thu, 27 Jan 2005 11:58:32 +0000 Received: from marl.lancs.ac.uk ([148.88.1.10]) by errol.lancs.ac.uk with esmtp (Exim 4.43) id 1Cu8IC-0004WY-Aq; Thu, 27 Jan 2005 11:58:32 +0000 Received: from in-egcsky000001.lancs.ac.uk ([194.80.36.29] helo=dunmore) by marl.lancs.ac.uk with esmtp (Exim 3.36 #1) id 1Cu8IB-0008Hi-00; Thu, 27 Jan 2005 11:58:31 +0000 From: "Martin Dunmore" To: Cc: "Graca Carvalho" , "Edwards, Christopher" Subject: Evaluation of Multihoming Solutions Date: Thu, 27 Jan 2005 11:58:32 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal 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: quoted-printable Hi, As part of the 6NET project (http://www.6net.org) we are producing a document that is attempting to evaluate the different multihoming = proposals that have surfaced in the last couple of years or so. The latest draft is publicly available on the 6NET website... http://www.6net.org/publications/other/multihoming.pdf (pdf version) http://www.6net.org/publications/other/multihoming.doc (ms word = version) The draft still has a few holes (see email below) but it would be = beneficial to get any feedback from people on the multi6 list. Regards, Martin -----Original Message----- From: owner-wp4@6net.org [mailto:owner-wp4@6net.org] On Behalf Of = Dunmore, Martin Sent: 25 January 2005 22:42 To: wp4@6net.org Subject: [6net wp4] D4.5.3 draft available I've placed the latest draft of D4.5.3 Evaluation of Multihoming = Solutions on the website in WP4/Contributions section. It still needs a bit of work and I'm hoping the chaps that are savvy = with multihoming can give me some feedback and/or contribute some more text. In particular we need to ask... Is the structure ok? Have I missed any important solutions? Some proposals have expired as internet drafts... does that mean we = should leave them out?=20 The main section I could do with some help on is the conclusions section where I'm hoping to evaluate the various proposals based on the goals in rfc3852 and then suggest some sensible way forward for people wishing to = do multihoing in IPv6. It's a little empty at the moment as I've not had = time to analyse and cross reference everything. The few sections with missing text aren't much of a problem as I can = fill them in myself. Although if anyone has text they can offer... please = feel free ;-) Other than that it needs general spit and polish and filling in a few blanks! Perhaps also some more diagrams. Regards, Martin ---------------------------------------- Dr Martin Dunmore=20 Research Associate=20 Computing Department InfoLab 21, South Drive Lancaster University Lancaster, LA1 4WA UK Tel: +44 (0)1524 510382=20 Fax: +44 (0)1524 510492=20 Mob: +44 (0)7866 676930 ------------------------------------------ From owner-multi6@ops.ietf.org Thu Jan 27 10:27:21 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17737 for ; Thu, 27 Jan 2005 10:27:20 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1CuBUA-000PtC-Sz for multi6-data@psg.com; Thu, 27 Jan 2005 15:23:06 +0000 Received: from [192.35.17.28] (helo=goliath.siemens.de) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CuBU7-000PsT-3i for multi6@ops.ietf.org; Thu, 27 Jan 2005 15:23:03 +0000 Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by goliath.siemens.de (8.12.6/8.12.6) with ESMTP id j0RFLf07029594; Thu, 27 Jan 2005 16:21:41 +0100 Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99]) by mail2.siemens.de (8.12.6/8.12.6) with ESMTP id j0RFLeiQ000890; Thu, 27 Jan 2005 16:21:41 +0100 Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2657.72) id ; Thu, 27 Jan 2005 16:21:40 +0100 Message-ID: <2A8DB02E3018D411901B009027FD3A3F04686A1B@mchp905a.mch.sbs.de> From: Tschofenig Hannes To: "'Martin Dunmore'" , multi6@ops.ietf.org Cc: Graca Carvalho , "Edwards, Christopher" Subject: AW: Evaluation of Multihoming Solutions Date: Thu, 27 Jan 2005 16:21:38 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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: quoted-printable hi martin,=20 you might also be interested to take a look at the following document: http://www.ietf.org/internet-drafts/draft-nagarajan-multi6-comparison-00= .txt ciao hannes > -----Urspr=FCngliche Nachricht----- > Von: Martin Dunmore [mailto:m.dunmore@lancaster.ac.uk]=20 > Gesendet: Donnerstag, 27. Januar 2005 12:59 > An: multi6@ops.ietf.org > Cc: Graca Carvalho; Edwards, Christopher > Betreff: Evaluation of Multihoming Solutions >=20 >=20 > Hi, >=20 > As part of the 6NET project (http://www.6net.org) we are producing a > document that is attempting to evaluate the different=20 > multihoming proposals > that have surfaced in the last couple of years or so. >=20 > The latest draft is publicly available on the 6NET website... > http://www.6net.org/publications/other/multihoming.pdf (pdf version) > http://www.6net.org/publications/other/multihoming.doc (ms=20 > word version) >=20 > The draft still has a few holes (see email below) but it=20 > would be beneficial > to get any feedback from people on the multi6 list. >=20 > Regards, > Martin >=20 >=20 > -----Original Message----- > From: owner-wp4@6net.org [mailto:owner-wp4@6net.org] On=20 > Behalf Of Dunmore, > Martin > Sent: 25 January 2005 22:42 > To: wp4@6net.org > Subject: [6net wp4] D4.5.3 draft available >=20 >=20 > I've placed the latest draft of D4.5.3 Evaluation of=20 > Multihoming Solutions > on the website in WP4/Contributions section. >=20 > It still needs a bit of work and I'm hoping the chaps that=20 > are savvy with > multihoming can give me some feedback and/or contribute some=20 > more text. >=20 > In particular we need to ask... >=20 > Is the structure ok? > Have I missed any important solutions? > Some proposals have expired as internet drafts... does that=20 > mean we should > leave them out?=20 >=20 > The main section I could do with some help on is the=20 > conclusions section > where I'm hoping to evaluate the various proposals based on=20 > the goals in > rfc3852 and then suggest some sensible way forward for people=20 > wishing to do > multihoing in IPv6. It's a little empty at the moment as I've=20 > not had time > to analyse and cross reference everything. >=20 > The few sections with missing text aren't much of a problem=20 > as I can fill > them in myself. Although if anyone has text they can offer...=20 > please feel > free ;-) >=20 > Other than that it needs general spit and polish and filling in a few > blanks! Perhaps also some more diagrams. >=20 > Regards, > Martin > ---------------------------------------- > Dr Martin Dunmore=20 > Research Associate=20 > Computing Department > InfoLab 21, South Drive > Lancaster University > Lancaster, LA1 4WA > UK > Tel: +44 (0)1524 510382=20 > Fax: +44 (0)1524 510492=20 > Mob: +44 (0)7866 676930 > ------------------------------------------ >=20 >=20 From owner-multi6@ops.ietf.org Fri Jan 28 16:42:02 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20994 for ; Fri, 28 Jan 2005 16:42:02 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1CudpH-000Ar0-6s for multi6-data@psg.com; Fri, 28 Jan 2005 21:38:47 +0000 Received: from [38.119.112.20] (helo=mail1.ambroseshoemaker.com) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CudpD-000Aqj-9G for multi6@ops.ietf.org; Fri, 28 Jan 2005 21:38:43 +0000 Received: from [204.157.180.218] ([204.157.180.218]) by mail1.ambroseshoemaker.com (Netscape Messaging Server 4.15) with ESMTP id IB1QQJ00.C70; Fri, 28 Jan 2005 16:37:31 -0500 Message-ID: <41FAB0DC.8010304@hotnic.net> Date: Fri, 28 Jan 2005 16:38:36 -0500 From: Kevin Loch User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.8a2) Gecko/20040715 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Martin Dunmore CC: multi6@ops.ietf.org Subject: Re: Evaluation of Multihoming Solutions References: In-Reply-To: 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 Martin Dunmore wrote: > Hi, > > As part of the 6NET project (http://www.6net.org) we are producing a > document that is attempting to evaluate the different multihoming proposals > that have surfaced in the last couple of years or so. Martin, You may be interested in this draft which was updated today: http://www.ietf.org/internet-drafts/draft-loch-multi6-alternate-path-encoding-03.txt which involves routers recognizing alternate prefixes encoded in the interface id portion of an address. The -03 update primarily involves recording and avoidance of unavailable paths. Kevin Loch From owner-multi6@ops.ietf.org Sun Jan 30 00:04:22 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA15624 for ; Sun, 30 Jan 2005 00:04:21 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.43 (FreeBSD)) id 1Cv7CT-000ClR-Jx for multi6-data@psg.com; Sun, 30 Jan 2005 05:00:41 +0000 Received: from [66.92.66.68] (helo=cyteen.hactrn.net) by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1Cv7CP-000Ckk-IW for multi6@ops.ietf.org; Sun, 30 Jan 2005 05:00:37 +0000 Received: from hactrn.net (localhost [127.0.0.1]) by cyteen.hactrn.net (Postfix) with ESMTP id BF87F74B for ; Sun, 30 Jan 2005 00:00:36 -0500 (EST) To: multi6@ops.ietf.org Subject: Weekly posting summary for multi6@ops.ietf.org From: Rob Austein Date: Sun, 30 Jan 2005 00:00:36 -0500 Message-Id: <20050130050036.BF87F74B@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 --------+------+--------+----------+------------------------ 25.00% | 1 | 35.49% | 4801 | hannes.tschofenig@siemens.com 25.00% | 1 | 30.00% | 4058 | m.dunmore@lancaster.ac.uk 25.00% | 1 | 17.59% | 2380 | kloch@hotnic.net 25.00% | 1 | 16.91% | 2288 | sra@hactrn.net --------+------+--------+----------+------------------------ 100.00% | 4 |100.00% | 13527 | 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.