Re: List merging?

Greg Vaudreuil <gvaudre@NRI.Reston.VA.US> Thu, 15 November 1990 15:22 UTC

Received: from nri by NRI.NRI.Reston.VA.US id aa05492; 15 Nov 90 10:22 EST
To: Frank Kastenholz <kasten%europa.interlan.com@relay.cs.net>
cc: frame-relay@NRI.Reston.VA.US, kwe%buitb.bu.edu@relay.cs.net, smds@NRI.Reston.VA.US, iplpdn@NRI.Reston.VA.US, gvaudre@NRI.Reston.VA.US
Subject: Re: List merging?
In-reply-to: Your message of Thu, 15 Nov 90 08:28:08 -0500. <9011151328.AA00160@europa.InterLan.Com>
Date: Thu, 15 Nov 90 10:20:57 -0500
From: Greg Vaudreuil <gvaudre@NRI.Reston.VA.US>
Message-ID: <9011151022.aa05492@NRI.NRI.Reston.VA.US>

From the manager of these lists.....

The frame-relay mailing list was created only because of popular
interest, not for any particular purpose.  As such, I have no problem
mashing this list into others.  First, I have two observations.

IP over Frame Relay seems to have two parts to the solution.  

1) IP framing over Frame Relay.  I understand frame-relay to be
   essentially a point to point service, and I have heard that PPP can
   be extended to include frame-relay support.  To the best of my
   knowlege (Stev Knowles?) this has not been exaustively explored.
   and will need to be to get this service up.  Inquire on the PPP
   mailing list....

   Mailing list: ietf-ppp@ucdavis.edu
   Request list: ietf-ppp-request@ucdavis.edu

2) Routing and Address Resolution are identical problems to those
   encountered in X.25, SMDS, and ISDN.  For this work, the IPLPDN
   mailing list is the place to go.  

   Mailing list: iplpdn@nri.reston.va.us
   Request list: iplpdn-request@nri.reston.va.us

   If there are no strong objections, I will fold the frame-relay list
   into the iplpdn list.  (cursory viewing shows a 60% overlap
   including the usual list of exploders....) Lets say I'll take comments
   till Wednesday.  (send to frame-relay-request PLEASE!!! I get too
   much direct mail as it is and the ability to pick is golden)

Comments? (no flames)

Greg V.