[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RAM] Request to advance RFC4214 to Proposed Standard
- To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
- Subject: Re: [RAM] Request to advance RFC4214 to Proposed Standard
- From: Tim Chown <tjc@ecs.soton.ac.uk>
- Date: Wed, 28 Mar 2007 17:01:52 +0100
- Cc: Brian E Carpenter <brc@zurich.ibm.com>, Fred Baker <fred@cisco.com>, Ron Bonica <rbonica@juniper.net>, Jari Arkko <jari.arkko@piuha.net>, v6ops@ops.ietf.org, Lindqvist Erik Kurt <kurtis@kurtis.pp.se>
- In-reply-to: <39C363776A4E8C4A94691D2BD9D1C9A101774842@XCH-NW-7V2.nw.nos.boeing.com>
- Mail-followup-to: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Brian E Carpenter <brc@zurich.ibm.com>, Fred Baker <fred@cisco.com>, Ron Bonica <rbonica@juniper.net>, Jari Arkko <jari.arkko@piuha.net>, v6ops@ops.ietf.org, Lindqvist Erik Kurt <kurtis@kurtis.pp.se>
- References: <39C363776A4E8C4A94691D2BD9D1C9A101774817@XCH-NW-7V2.nw.nos.boeing.com> <39C363776A4E8C4A94691D2BD9D1C9A101774818@XCH-NW-7V2.nw.nos.boeing.com> <4606177E.9070405@piuha.net> <4606444E.1030409@zurich.ibm.com> <E631EE1C-4A87-4F3E-94E7-C141066979EF@cisco.com> <39C363776A4E8C4A94691D2BD9D1C9A101774836@XCH-NW-7V2.nw.nos.boeing.com> <460A5ECC.1080503@zurich.ibm.com> <39C363776A4E8C4A94691D2BD9D1C9A10177483C@XCH-NW-7V2.nw.nos.boeing.com> <460A8AED.1050800@zurich.ibm.com> <39C363776A4E8C4A94691D2BD9D1C9A101774842@XCH-NW-7V2.nw.nos.boeing.com>
- User-agent: Mutt/1.4i
On Wed, Mar 28, 2007 at 08:51:48AM -0700, Templin, Fred L wrote:
> Brian,
>
> > Actually the VE work was directly triggered by the 6over4 draft;
> > it was a student of Lixia Zhang, and the 6over4 authors encouraged
> > him!
>
> Thanks for setting the record straight on this; another reason
> to recycle RFC4214 would be to simply get our references to past
> works updated accordingly.
The reason we didn't use ISATAP in early deployment phases here is that
we simply didn't want arbitrary automatic tunnelling between links
within our site. We have a preference to manage and structure the
connectivity. If the auto-tunnelling were all on one link, then we
may as well use native IPv6. Instead we managed the connectivity between
the early adopter links. We wouldn't use 6over4 in our environment for
the same reason, although IPv4 multicast is available.
That said, I can see how there may be a useful application of ISATAP
for manets, and would be interested in seeing an example deployment plan
or scenario.
--
Tim