Re: [Sip] I-D Action: draft-kaplan-sip-four-oh-00.txt

[Hadriel Kaplan <HKaplan at acmepacket.com>]

Hmmm... I thought RFC 1149 was at a lower layer, so UDP just rides on IP on top of Avian.  Really, it's essentially just another wireless layer-1, which I guess would be "WiFly" instead of WiFi.  I'll leave it to Dan's draft-wing-it to handle how one does that, if we need a sipping-style use-case.

But I really think RFC 1149 is for the birds, and would pigeon-hole us into one specific path.  That would create a chicken-and-egg problem, because without 1149 being popular, people would not flock to SIPv4, and that would fowl up 1149 becoming popular.  I'd rather duck that issue, and instead home-in on publishing a SIPv4 draft to sow the seeds, and letting it fly, and we can smooth any ruffled feathers later.  That way people can migrate to SIPv4 now, until the final published doc is grounded.  If SIPv4 and WiFly come home to roost we can crow about it later, but for now we need to let SIPv4 out of the cage, with space to stretch its wings and take off.

-hadriel


> -----Original Message-----
> From: Vijay K. Gurbani [mailto:vkg at alcatel-lucent.com]
> Sent: Wednesday, April 02, 2008 2:19 PM
> To: Hadriel Kaplan
> Cc: sip at ietf.org; Bob Penfield
> Subject: Re: [Sip] I-D Action: draft-kaplan-sip-four-oh-00.txt
>
> Hadriel Kaplan wrote:
> > Greetings,
> > Given today's relative importance in history - being the date Swiss
> farmers had their largest spaghetti crop harvest, Sweden introduced color
> television, the USSR connected Kremvax to Usenet, the Alabama state
> government changed the value of Pi to 3.0, and much more - we took it upon
> ourselves to write up and submit a new Internet-Draft for an update to RFC
> 3261 (and a bunch of other RFCs): P2P2PSIP, a.k.a. SIP v4.0.
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-kaplan-sip-four-oh-00.txt
>
> Hadriel: Given the problems we have had with UDP, I think your draft
> should deprecate UDP in favor of carrying IP datagrams on avian
> carriers (RFC 1149).  The benefits are many, and the frame format
> is very simple:
>
>     The IP datagram is printed, on a small scroll of paper, in
>     hexadecimal, with each octet separated by whitestuff and blackstuff.
>     The scroll of paper is wrapped around one leg of the avian carrier.
>     A band of duct tape is used to secure the datagram's edges.  The
>     bandwidth is limited to the leg length.  The MTU is variable, and
>     paradoxically, generally increases with increased carrier age.  A
>     typical MTU is 256 milligrams.  Some datagram padding may be needed.
>
>     Upon receipt, the duct tape is removed and the paper copy of the
>     datagram is optically scanned into a electronically transmittable
>     form.
>
> - vijay
> --
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
> 2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA)
> Email: vkg at {alcatel-lucent.com,bell-labs.com,acm.org}
> WWW:   http://www.alcatel-lucent.com/bell-labs
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip