Interesting timing on this message, but see below: > -----Original Message----- > From: Joe Touch [mailto:to...@isi.edu] > Sent: Tuesday, May 16, 2017 4:13 PM > To: Templin, Fred L <fred.l.temp...@boeing.com> > Cc: int-area@ietf.org > Subject: Re: [Int-area] I-D Action: draft-ietf-intarea-tunnels-05.txt > > HI Fred, > > I'm in the process of the next update, and wanted to clarify the following: > > > On 3/28/2017 9:36 AM, Templin, Fred L wrote: > > 18) Section 4.3.3, For Multipoint Tunnels, please cite AERO, as > > well as ISATAP [RFC5214] and 6over4 [RFC2529]. They define > > an NBMA multipoint tunnel framework that has been around a > > lot longer than the other examples cited. > That section doesn't list examples of multipoint tunnels per se. It > lists systems that use multipoint tunnels (LISP, TRILL) and discusses > mechanisms that support multipoint tunnels (LANE, etc.).
AERO embraces the tunnel as a link in the spirit of your document while LISP does not. AERO defines "AERO interface" and "AERO link" - LISP goes out of its way to avoid saying anything about interfaces or links. > I'm not sure there's a clearly good, original ref for multipoint tunnels > - the concept has been around in some form since basically the notion of > a tunnel. RFC2529 is the first I am aware of. Fred > Joe > > _______________________________________________ Int-area mailing list Int-area@ietf.org https://www.ietf.org/mailman/listinfo/int-area
