[net2-wg] IP stack name

[Martin Turon]

A more generic suggestion would be slip: Sockets over Low-power Internet
Protocol.  That would imply that TCP and UDP are rolled into the
package, and get rid of the institution, though the sound of sending out
little blip packets resonates better with me.  The namespace is probably
pretty packed by now and prone to collisions with other projects.

Martin 

__________________________________________________
Martin Turon  |  Crossbow Technology, Inc.


-----Original Message-----
From: Martin Turon 
Sent: Friday, January 16, 2009 12:16 PM
To: 'Omprakash Gnawali'; Philip Levis
Cc: net2-wg
Subject: RE: [net2-wg] IP stack name

Blip is certainly a cool name (Berkeley Low-Power Internet Protocol).
The "L" could also stand for lowpan and you could add the IP version too
as in blip6.  I see what you are saying about the institution, but it
just clarifies that origin of the implementation.  People don't seem to
get too worked up about BSD, and it would not be too unlike the way ARM
documents still say the core is based on a "Harvard Architecture"...

Martin 

__________________________________________________
Martin Turon  |  Crossbow Technology, Inc.


-----Original Message-----
From: net2-wg-bounces at millennium.berkeley.edu
[mailto:net2-wg-bounces at millennium.berkeley.edu] On Behalf Of Omprakash
Gnawali
Sent: Thursday, January 15, 2009 10:29 PM
To: Philip Levis
Cc: net2-wg
Subject: Re: [net2-wg] IP stack name

Sure, it would be up to him. But I wanted to say that institution name
in the name might make potential contributors feel a bit unwelcome.

- om_p

On Thu, Jan 15, 2009 at 10:25 PM, Philip Levis <pal at cs.stanford.edu>
wrote:
> I think the name is ultimately up to Stephen, but let's see if we can
help
> him come up with a good name. :)
>
> Phil
>
> On Jan 15, 2009, at 10:00 PM, Omprakash Gnawali wrote:
>
>> We need to come up with a short (and hopefully descriptive) name for
>> the IP stack. Steve had suggested bip or blip (Berkeley IP stack). I
>> prefer something like tcpipv6 or even tcpip considering it will have
>> the full network/transport services. Maybe tcp in tcpip is bit of a
>> stretch. Do people have some other ideas?
>>
>> - om_p
>> _______________________________________________
>> net2-wg mailing list
>> net2-wg at millennium.berkeley.edu
>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/net2-wg
>
>
_______________________________________________
net2-wg mailing list
net2-wg at millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/net2-wg