RE : RE : [lwip-devel] additional/optional protocols

[Frédéric BERNON]

Isn't it SIP (Session Initiation Protocol)? For application protocols, I 
usually implement them from RFC. Lot of them are easy to implement, if you 
don't want to be at 100% RFC compliant... 
  
====================================
Frédéric BERNON 
HYMATOM SA 
Chef de projet informatique 
Microsoft Certified Professional 
Tél. : +33 (0)4-67-87-61-10 
Fax. : +33 (0)4-67-70-85-44 
Email : address@hidden 
Web Site : http://www.hymatom.fr 
====================================
P Avant d'imprimer, penser à l'environnement
 


-----Message d'origine-----
De : address@hidden [mailto:address@hidden De la part de Decker, Paul
Envoyé : mercredi 23 mai 2007 23:19
À : lwip-devel
Objet : RE: RE : [lwip-devel] additional/optional protocols


Hi Frederic,

Thank you for the quick answer, it is very good information to know.  I think 
SIG is a voip protocol, but I haven't researched it enough yet to know.  With 
the others that are on the application layer, do you know of any projects 
similar to lwip that have implemented these?

Best regards,

Paul Decker
Analog Devices



-----Original Message-----
From: address@hidden [mailto:address@hidden On Behalf Of Frédéric BERNON
Sent: Wednesday, May 23, 2007 5:01 PM
To: lwip-devel
Subject: RE : [lwip-devel] additional/optional protocols

Hi Paul,

For IGMP, it include in current CVS HEAD, due to the fact there is some real 
interactions with internal components of the stack. We have already talk to add 
in contrib modules some kind of sources using raw or sequential api.

A DNS client could be something to share, because it's something than everyone 
could need. From memory, Jim Pettinato has ported the uIP resolver to lwIP. You 
can ask him if he can share it with you. Look for the thread "BSD API tcp echo 
server port" in April, in mailing list archives... 

PPPoE could be an extension because I think like classic PPP, there is real 
interaction with the stack.

But SNTP, SMTP, RTP, Telnet, FTP, TFTP are only working with the lwIP's API, 
and not with other parts. So, I don't think it is in the scope of lwIP. But 
it's my point of view, wait for others answers...

About SIG, what kind of protocol is it? 
  
====================================
Frédéric BERNON
HYMATOM SA
Chef de projet informatique
Microsoft Certified Professional
Tél. : +33 (0)4-67-87-61-10
Fax. : +33 (0)4-67-70-85-44
Email : address@hidden
Web Site : http://www.hymatom.fr ====================================
P Avant d'imprimer, penser à l'environnement
 


-----Message d'origine-----
De : address@hidden [mailto:address@hidden De la part de Decker, Paul Envoyé : 
mercredi 23 mai 2007 22:12 À : lwip-devel Objet : [lwip-devel] 
additional/optional protocols


Hello everyone, 

I apologize in advance if this is going to the wrong group, if so, please 
kindly identify where a question like this would generally be posted.

As some of you know, we have made a port of the LwIP sources to our Blackfin 
processors.  At this time, we have not submitted our port back to the LwIP 
community, however, this is something we are looking at doing.

We are also looking at various other projects and extensions to deliver with 
our LwIP offering.  Some of these ideas include support for protocols such as 
DNS(client), SNTP, SMTP, PPPoE, RTP, SIG and IGMP.  We are also looking at 
various applications and protocols such as Telenet, FTP, TFTP, and POP3.

Now for the question(s).   Do you have any recommendations on these?
Such as, are there already existing ports of these which have a similar BSD 
style license?  Are there any plans or desires to move any of these into the 
lwIP deliverable package?  


Thanks in advance and
Best regards,
Paul Decker
Analog Devices


_______________________________________________
lwip-devel mailing list
address@hidden http://lists.nongnu.org/mailman/listinfo/lwip-devel


_______________________________________________
lwip-devel mailing list
address@hidden http://lists.nongnu.org/mailman/listinfo/lwip-devel

Frédéric BERNON.vcf
Description: Frédéric BERNON.vcf