On Jul 27, 2011, at 7:31 AM, Mark Townsley <m...@townsley.net> wrote: > > On Jul 27, 2011, at 7:09 AM, Fred Baker wrote: > >> >> On Jul 26, 2011, at 6:49 PM, Brian E Carpenter wrote: >> >>> Since 6to4 is a transition mechanism it has no long term future *by >>> definition*. Even if someone chooses to design a v2, who is going to >>> implement it? >> >> Actually, I think one could argue pretty effectively that 6rd is 6to4-bis. > > +1 > > - Mark +2 > >> _______________________________________________ >> v6ops mailing list >> v6...@ietf.org >> https://www.ietf.org/mailman/listinfo/v6ops > > _______________________________________________ > Ietf mailing list > Ietf@ietf.org > https://www.ietf.org/mailman/listinfo/ietf > _______________________________________________ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
- Re: 6to4v2 (as in ripv2)? Keith Moore
- RE: 6to4v2 (as in ripv2)? Michel Py
- Re: RE: 6to4v2 (as in ripv2)? Cameron Byrne
- Re: [v6ops] 6to4v2 (as in rip... John Mann (ITS)
- Re: [v6ops] 6to4v2 (as in rip... Keith Moore
- Re: [v6ops] 6to4v2 (as in rip... Mark Townsley
- Re: [v6ops] 6to4v2 (as in rip... Cameron Byrne
- Re: [v6ops] 6to4v2 (as in rip... Mark Andrews
- Re: [v6ops] 6to4v2 (as in rip... Erik Kline
- Re: [v6ops] 6to4v2 (as in rip... Douglas Otis
- Re: [v6ops] 6to4v2 (as in rip... Thomas Nadeau
- Re: draft-ietf-v6ops-6to4-to-historic (ye... Brian E Carpenter
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) John Leslie
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Martin Rex
- RE: draft-ietf-v6ops-6to4-to-historic (yet again) Christian Huitema
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Mark Andrews
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Cameron Byrne
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Mykyta Yevstifeyev
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Roger Jørgensen
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Tim Chown