Re: [6lowapp] SIP and 6LoWPAN & Some General Suggestions

[Shidan <[e-mail]>]

Thanks for the info Carsten, that makes sense.
We have submitted the motivational I-D for SIP as a 6LoWAPP protocol and it
can be found here:
http://www.ietf.org/id/draft-roychowdhury-6lowappsip-00.txt

<http://www.ietf.org/id/draft-roychowdhury-6lowappsip-00.txt>---
Shidan Gouran

On Sat, Oct 17, 2009 at 6:07 PM, Carsten Bormann <[e-mail]> wrote:

> On Oct 17, 2009, at 23:36, Shidan wrote:
>
>  SIGCOMP
>>
>
> SigComp (RFC 3320) is essentially a virtual machine for shipping
> decompression code to a peer.
> Constrained nodes (as in 8 MHz 10K RAM) won't be able to run such a virtual
> machine, I'd say.
>
> Actually, the whole idea of using complex encodings full of encoding
> alternatives (the fact that any of these are text-based is secondary to
> that) and then compressing them with a data compression algorithm is
> something that may be appropriate out of backwards compatibility, but not
> for a new design that emphasizes minimal code complexity.
>
> Apart from this little nit (sorry, I was involved in RFC 3320), I'm looking
> forward to your draft.
>
> BTW, right now the score is:
>
> 16 Oct 2009  draft-martocci-6lowapp-building-applications
> 16 Oct 2009  draft-shelby-6lowapp-encoding
> 14 Oct 2009  draft-schmitt-6lowapp-ipfix-ws
> 11 Sep 2009  draft-frank-6lowapp-chopan
> 13 Jul 2009  draft-bormann-6lowpan-6lowapp-problem
>
> 48 more hours to go...
>
> Gruesse, Carsten
>
>