Re: RFC4214(bis)

[Fred Baker <fred@cisco.com>]

You're not listening.

On Mar 28, 2007, at 7:32 PM, Templin, Fred L wrote:

> FYI, RFC4214(bis) has been sent to internet-drafts@ietf.org
> and is available here until it shows up in the I-D repository:
>
>   http://www.geocities.com/osprey67/isatap/isatap-bis-00.txt
>
> Workgroup item?
>
> Fred
> fred.l.templin@boeing.com
>
> > -----Original Message-----
> > From: Templin, Fred L
> > Sent: Wednesday, March 28, 2007 7:55 AM
> > To: Fred Baker
> > Cc: Brian E Carpenter; Ron Bonica; Jari Arkko;
> > townsley@cisco.com; v6ops@ops.ietf.org; Lindqvist Erik Kurt
> > Subject: RE: [RAM] Request to advance RFC4214 to Proposed Standard
> >
> > Fred,
> >
> > > -----Original Message-----
> > > From: Fred Baker [mailto:fred@cisco.com]
> > > Sent: Wednesday, March 28, 2007 12:03 AM
> > > To: Templin, Fred L
> > > Cc: Brian E Carpenter; Ron Bonica; Jari Arkko;
> > > v6ops@ops.ietf.org; Lindqvist Erik Kurt
> > > Subject: Re: [RAM] Request to advance RFC4214 to Proposed Standard
> > >
> > > Good to know, and certainly a good thing. Until Ron tells me
> > > otherwise, that's as far as I'm going in this discussion.
> >
> > IMHO, there seems to be enough interest here such that I would
> > now like to formally re-open my request to advance RFC4214 as
> > standards-track (recall that in my 3/27/07 message to the RAM
> > list I said that I was suspending the request pending further
> > discussion).
> >
> > Should we wait to see what the ADs have to say about it now?
> >
> > Thanks - Fred
> > fred.l.templin@boeing.com
> >
> > > On Mar 28, 2007, at 12:05 AM, Templin, Fred L wrote:
> > >
> > > > Fred,
> > > >
> > > > Responding only to this one point for now:
> > > >
> > > > > In short, this is not just "an" approach to coexistence; if the
> > > > > IPv6 Operations Working Group is going to put its
> > imprimatur on a
> > > > > technology, I would want to know that we were recommending the
> > > > > *right* one.
> > > >
> > > > What ISATAP is good for is providing a link for connecting dual-
> > > > stack routers within Mobile Ad-Hoc Networks (MANETs), as well as
> > > > mechanisms for autoconfiguration and discovery of multiple
> > > Internet
> > > > gateways. It is important to note that the term "MANET"
> > could mean
> > > > anything from mobile platforms (planes, trains and
> > > automobiles), to
> > > > a home network, to a singleton node with an aribtarily-complex
> > > > network of physical or virtual nodes within. For other examples,
> > > > please see the thread on "Real-life Deploymnet of MANETs" on the
> > > > MANET mailing list:
> > http://www1.ietf.org/mail-archive/web/manet/current/msg09029.html
> > > > Informational aspects of the operation of ISATAP are
> > documented in
> > > > "MANET Autoconfiguration"; see:
> > > >
> > > >   http://www.ietf.org/internet-drafts/draft-templin-autoconf-
> > > > dhcp-07.txt
> > > >
> > > > but please note that this work (as well as ISATAP itself)
> > derived
> > > > from an earlier work titled: "Virtual Ethernet".
> > > >
> > > > Important point is that for the use-case of dual-stack routers
> > > > communicating within a MANET, ISATAP already provides a
> > mechanism
> > > > that satisfies the needs of the IETF AUTOCONF wg and the
> > so-called
> > > > "MANEMO" interest group. Plus, it is shipping in major
> > vendor OS's
> > > > today.
> > > >
> > > > Thanks - Fred
> > > > fred.l.templin@boeing.com