I just noticed that Chris's email mentioned that one of the points for
debate was whether the XCON 'protocol' should be Binary, Text, or Both.
I just wanted to mention that, as well as a text encoding, Lumas also has
binary encoding rules.
As already mentioned, there is already code to convert a Lumas definition
into ABNF, and conceivably code could be written to convert Lumas into
ASCII-art style drawings similar to that used in BFCP.
Hence, by using a higher level of abstraction like Lumas you can make
such details as text vs. binary vs. ABNF vs. ASCII-art an implementation
detail!
As before, more info on Lumas is at: http://www.tech-know-ware.com/lumas
Regards,
Pete.
P.S. Further to my previous e-mail, to give you another idea of how a
standard Lumas text message might look compared to other encodings, I've
dug out a file I created a long time back that compares an old SIP
message encoded using 'ABNF', Lumas and XML. Obviously in the latter 2
cases there are a number of ways that the encoding could have been done,
so they should be considered for guidance only! Note also that in the
case of Lumas and XML, line breaks have no significance so the line
breaks shown are effectively pretty-print issues. Additionally, if I was
doing a Lumas encoding of SIP I would have used shorter tag/header names
more along the lines of SDP, but again, that's an implementation issue.
----------------- 'ABNF' ---------------------
INVITE sip:watson at boston.bell-tel.com SIP/2.0
Via: SIP/2.0/UDP kton.bell-tel.com
From: A. Bell <sip:a.g.bell at bell-tel.com>
To: T. Watson <sip:watson at bell-tel.com>
Call-ID: 3298420296 at kton.bell-tel.com
CSeq: 1 INVITE
Subject: Mr. Watson, come here.
Content-Type: application/sdp
Content-Length: 111
v=0
o=bell 53655765 2353687637 IN IP4 128.3.4.5
s=Mr. Watson, come here.
c=IN IP4 kton.bell-tel.com
m=audio 3456 RTP/AVP 0 3 4 5
--------------- LUMAS ------------------------
INVITE={sip:watson at boston.bell-tel.com SIP/2.0
Via={SIP/2.0/UDP kton.bell-tel.com}
From={sip:a.g.bell at bell-tel.com "A. Bell"}
To={sip:watson at bell-tel.com "T. Watson"}
Call-ID=3298420296 at kton.bell-tel.com
CSeq={1 INVITE }
Subject="Mr. Watson, come here."
Content-Type=application/sdp
}
SDP={
v=0
o={bell 53655765 2353687637 IN=IP4=128.3.4.5}
s="Mr. Watson, come here."
c={IN=IP4=kton.bell-tel.com}
m={audio 3456 RTP=AVP 0,3,4,5}
}
--------------- XML ----------------------
<SIP proto="SIP/2.0">
<INVITE uri="sip:watson at boston.bell-tel.com">
<Via proto="SIP/2.0/UDP" return="kton.bell-tel.com"/>
<From name="A. Bell" addr="sip:a.g.bell at bell-tel.com"/>
<To name="T. Watson" addr="sip:watson at bell-tel.com"/>
<Call-ID>3298420296 at kton.bell-tel.com</Call-ID>
<CSeq seq="1" method="INVITE">
<Subject>Mr. Watson, come here.</subject>
<Content-Type value="application/sdp"/>
<Content-Length value="111"/>
</INVITE>
<SDP v="0"
<o username="bell" sesseionid="53655765" version="2353687637 nettype="IN"
addrtype="IP4" address="128.3.4.5"/>
<s>Mr. Watson, come here.</s>
<c nettype="IN" addrtype="IP4" address="kton.bell-tel.com"/>
<m type="audio" port="3456" transport="RTP/AVP">
<m>0</m><m>3</m><m>4</m><m>5</m>
</sdp>
</SIP>
--
=============================================
Pete Cordell
Tech-Know-Ware Ltd
for XML to C++ data binding visit
http://www.tech-know-ware.com/lmx
(or http://www.xml2cpp.com)
=============================================
_______________________________________________
XCON mailing list
XCON at ietf.org
https://www1.ietf.org/mailman/listinfo/xcon
