Fwd: I-D ACTION:draft-huitema-shim6-ingress-filtering-00.txt
marcelo bagnulo braun <marcelo@it.uc3m.es> Fri, 23 September 2005 09:19 UTC
Envelope-to: shim6-data@psg.com
Delivery-date: Fri, 23 Sep 2005 09:19:33 +0000
Mime-Version: 1.0 (Apple Message framework v622)
Content-Transfer-Encoding: 7bit
Message-Id: <d0c9338167f32e33777bc143a322ed1c@it.uc3m.es>
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
To: shim6 <shim6@psg.com>
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
Subject: Fwd: I-D ACTION:draft-huitema-shim6-ingress-filtering-00.txt
Date: Fri, 23 Sep 2005 11:19:24 +0200
Hi, We would like to submit the following draft for consideration to the working group. The goal of this document is to provide ingress filtering compatibility for multihomed sites, fitting in the charter in the item described as: In addition to the network layer shim solution, the shim6 WG is specifically chartered to work on: o Solutions for site exit router selection that work 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 site exit router selection and the associated address selection process should work whether or not the peer site supports the shim6 protocol. In particular, the approach proposed in the draft provides support for legacy hosts (within and outside the the multihomed site) allowing this legacy hosts to be able to properly communicate without being affected by the availability of multiple prefixes/ISPs in the site, as required in RFC 3582: The solution should not destroy IPv6 connectivity for a legacy host implementing RFC 3513 [4] , RFC 2460 [1] , RFC 3493 [5], and other basic IPv6 specifications current in April 2003. That is to say, if a host can work in a single-homed site, it should still be able to work in a multihomed site, even if it cannot benefit from site- multihoming. It would be compatible with this goal for such a host to lose connectivity if a site lost connectivity to one transit provider, despite the fact that other transit provider connections were still operational. So, we would like to know if the working group would be willing to take on this document and continue with this approach. Regards, marcelo Inicio mensaje reenviado: > De: Internet-Drafts@ietf.org > Fecha: 23 de septiembre de 2005 00:50:01 GMT+02:00 > Para: i-d-announce@ietf.org > Asunto: I-D ACTION:draft-huitema-shim6-ingress-filtering-00.txt > Responder a: internet-drafts@ietf.org > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > > Title : Ingress filtering compatibility for IPv6 multihomed sites > Author(s) : C. Huitema, et al. > Filename : draft-huitema-shim6-ingress-filtering-00.txt > Pages : 17 > Date : 2005-9-22 > > The note presents a set of mechanisms to provide ingress filtering > compatibility for legacy hosts in IPv6 multihomed sites. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-huitema-shim6-ingress- > filtering-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-huitema-shim6-ingress-filtering-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-huitema-shim6-ingress-filtering-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. > Content-Type: text/plain > Content-ID: <2005-9-22162625.I-D@ietf.org> > > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/i-d-announce
- Fwd: I-D ACTION:draft-huitema-shim6-ingress-filteā¦ marcelo bagnulo braun