[Planetlab-devel] IPv6 support for MyPLC

Bound, Jim Jim.Bound at hp.com
Tue Nov 7 20:06:38 EST 2006 

ack most dont use v4 options for IP.
/jim 

> -----Original Message-----
> From: McGeer, Patrick C 
> Sent: Tuesday, November 07, 2006 8:03 PM
> To: Bound, Jim; 'Marc E. Fiuczynski'; 'devel at lists.planet-lab.org'
> Subject: RE: [Planetlab-devel] IPv6 support for MyPLC
> 
> I was talking to Steve Schwab yesterday, and he pointed out a 
> hole in the v4 implementation of  ER signalling which is easy 
> to fix in v6.  Essentially, unless there's an audit trail (at 
> least, original request and current value) of guaranteed-rate 
> rate requests then we can't authenticate and prevent 
> bandwidth hijacking.  Since the v6 header permits chaining of 
> option fields, this is easily fixed in v6.  In v4, it's a bear...
> Rick
> 
> -----Original Message-----
> From: Bound, Jim
> Sent: Tuesday, November 07, 2006 4:53 PM
> To: Bound, Jim; McGeer, Patrick C; 'Marc E. Fiuczynski'; 
> 'devel at lists.planet-lab.org'
> Subject: RE: [Planetlab-devel] IPv6 support for MyPLC
> 
> one other data point.  if ipsec is used via v4 and only one 
> address then a decrypt must happen before the ports are seen 
> to pass to correct vserver.  with ipv6 it will be possible 
> for each vserver to perform their own decrypt in each vserver 
> thus meaning each vserver could have peer-to-peer 
> communications with their own ipsec per their own IPv6 
> address.  thus the communications is even in manys definition 
> more pure end-to-end (and mine as fyi).  nice advantage of 
> IPv6 in this case.
> 
> /jim 
> 
> > -----Original Message-----
> > From: Bound, Jim
> > Sent: Tuesday, November 07, 2006 7:46 PM
> > To: McGeer, Patrick C; 'Marc E. Fiuczynski'; 
> > 'devel at lists.planet-lab.org'
> > Subject: RE: [Planetlab-devel] IPv6 support for MyPLC
> > 
> > OK this is complex and VM issue interfacing to the network.
> > 
> > ifconfig configures interfaces on NIC cards.  the interface is 
> > typically a hardware interface.  So assume your assigning 
> one address 
> > to the interface but then have some form of custom handler 
> that looks 
> > at ports to determine or identify which VM Server gets the 
> packet in 
> > the IP Stack?
> > 
> > For IPv6 for a link it can support multiple prefixes per 
> link. So lets 
> > say on PLL vserver is its own link.  There could be multple 
> prefixes 
> > for one NIC all using the same EUI for IPv6.  Depending on the PLL 
> > prefix you select will identify what each link vserver 
> uses.  Thus I 
> > think stateless autoconfig can work just need good router 
> that handles 
> > the node discovery in front of PLL vserver node.  All the 
> choices marc 
> > listed for DNS are a decision to be made.  Just so you know 
> years ago 
> > we moved all the IPv6 node discovery ICMPv6 packets up to 
> user space 
> > and then from there did DynDNS (yours truly wrote that code :--)).
> > 
> > But PLL is using Linux right not UNIX variant?
> > 
> > Bottom line this is very doable but it will take some 
> tinkering with 
> > the interface to the vserver incantations and sounds like some code 
> > changes?
> > 
> > /jim
> > 
> > > -----Original Message-----
> > > From: McGeer, Patrick C
> > > Sent: Tuesday, November 07, 2006 7:35 PM
> > > To: Bound, Jim; 'Marc E. Fiuczynski'; 'devel at lists.planet-lab.org'
> > > Subject: RE: [Planetlab-devel] IPv6 support for MyPLC
> > > 
> > > 1. Yes, there are multiple (often, >= 20) vservers/machine.
> > > 2. I'll let Marc describe how IP config is done.  Or can we
> > get enough
> > > info just by logging into an arbitrary PL node and 
> running ifconfig?
> > > 
> > > -----Original Message-----
> > > From: Bound, Jim
> > > Sent: Tuesday, November 07, 2006 4:31 PM
> > > To: McGeer, Patrick C; 'Marc E. Fiuczynski'; 
> > > 'devel at lists.planet-lab.org'
> > > Subject: RE: [Planetlab-devel] IPv6 support for MyPLC
> > > 
> > > Rick,
> > > 
> > > OK yes v6 makes that much better.
> > > 
> > > So are there multiple vservers per machine?
> > > 
> > > If you have a paper that explains how IP config is done I
> > can go read
> > > that too?  If answer is yes to the above next questions :--)
> > > 
> > > thx
> > > /jim
> > > 
> > > > -----Original Message-----
> > > > From: McGeer, Patrick C
> > > > Sent: Tuesday, November 07, 2006 7:26 PM
> > > > To: Bound, Jim; Marc E. Fiuczynski; devel at lists.planet-lab.org
> > > > Subject: RE: [Planetlab-devel] IPv6 support for MyPLC
> > > > 
> > > > Jim,
> > > > One of the problems that PlanetLab has is that we only
> > have one v4
> > > > address per machine (gee, think more address bits would
> > solve this
> > > > problem?).  So the ugly choices are to share the port
> > space (which
> > > > we're doing), or do some hideous on-box NAT thing.
> > > > 
> > > > The cool thing about v6 (well, one cool thing about v6) is
> > > that we can
> > > > give each sliver (aka, each virtual machine) its own v6
> > > address.  So
> > > > we haven't faced this issue in v4 because
> > > > v4 is too limited to give us the possibility.
> > > > 
> > > > -- Rick
> > > > 
> > > > -----Original Message-----
> > > > From: devel-bounces at planet-lab.org 
> > > > [mailto:devel-bounces at planet-lab.org] On Behalf Of Bound, Jim
> > > > Sent: Tuesday, November 07, 2006 3:35 PM
> > > > To: Marc E. Fiuczynski; devel at lists.planet-lab.org
> > > > Subject: RE: [Planetlab-devel] IPv6 support for MyPLC
> > > > 
> > > > How does it work with IPv4 today?  
> > > > 
> > > > I don't how the vserver configures its IP address and if
> > it uses an
> > > > IPv6 implementation it must know node discovery thus
> > > stateless could
> > > > work.
> > > > 
> > > > DHCPv6 assumes their is a DHCPv6 client on the vserver?
> > > > 
> > > > /jim
> > > > 
> > > > > -----Original Message-----
> > > > > From: devel-bounces at planet-lab.org 
> > > > > [mailto:devel-bounces at planet-lab.org] On Behalf Of Marc E.
> > > > Fiuczynski
> > > > > Sent: Tuesday, November 07, 2006 5:59 PM
> > > > > To: devel at lists.planet-lab.org
> > > > > Subject: [Planetlab-devel] IPv6 support for MyPLC
> > > > > 
> > > > > [This thread was on started on a separate mailing list. 
> > > > I've shut down
> > > > > that mailing list and would like to continue on the
> > devel mailing
> > > > > list.]
> > > > > 
> > > > > We are still plugging along on the required kernel fixes to
> > > > support a
> > > > > unique
> > > > > IPv6 address per sliver (i.e., a vserver or virtual 
> machine) on 
> > > > > PlanetLab.
> > > > > While this seems to be making happy progress, there are at
> > > > least two
> > > > > issues that we need to resolve for which it would be
> > great to get
> > > > > feedback /
> > > > > thoughts:
> > > > > 
> > > > > 1) What IPv6 address should be assigned to a sliver 
> (static or 
> > > > > autoconf'd)?
> > > > > 
> > > > > and
> > > > > 
> > > > > 2) How to get the IPv6 addresses assigned to slivers into DNS?
> > > > > 
> > > > > Marc
> > > > > 
> > > > > _______________________________________________
> > > > > Devel mailing list
> > > > > Devel at lists.planet-lab.org
> > > > > https://lists.planet-lab.org/mailman/listinfo/devel
> > > > > 
> > > > 
> > > > _______________________________________________
> > > > Devel mailing list
> > > > Devel at lists.planet-lab.org
> > > > https://lists.planet-lab.org/mailman/listinfo/devel
> > > > 
> > > 
>

More information about the Devel mailing list