From: Paul A. <pau...@gm...> - 2006-12-20 18:10:18
|
---------- Forwarded message ---------- From: New port requests via RT <ian...@ia...> Date: Dec 20, 2006 1:06 PM Subject: [IANA #50010] AutoReply: Application for port-number: owserver This message has been automatically generated in response to the creation of a ticket regarding: "Application for port-number: owserver", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [IANA #50010]. Please include the string: [IANA #50010] ------------------------------------------------------------------------- Application for User Registered Port Number Name : Paul Alfille Protocol Number : TCP Message Formats : The full explanation is at http://www.owfs.org/index.php?page=owserver-protocol Basically messages are variable length, with a 6 word (24 byte) header, and a variable "payload" There are two main types of messages: to owserver, and from owserver. (Request and Reply). Client Header: (network byte order, 6 words): A. Version B. Payload (length of variable reagion in bytes) C. Type (read,write,directory,presence) D. Measurement scales and other flags E. Size of data sent/expected F. Offset to read/write Server Header: (network byte order, 6 words): A. Version B. Payload (length of variable reagion in bytes) C. return code (<0 for error) D. Measurement scales and other flags E. Size of data sent/expected F. Offset to read/write The variable region varies with message type: Read: send path, return value Write: send path/value return just header Presence: Send path, return just header Dir: send path, return multiple messages. 1. directory element (multiple) 2. "I'm alive" if taking too long (payload <0) 3. end or list (payload=0) There is one elaboration. owserver to owserver messages have a set of unique 16byte tags added to the end, to prevent loops. The number of tags is encoded in the version. Message Types : Request and Reply, only. There is no "cancel" message. Message opcodes : read write directory presence "I'm alive" Message Sequences : A client sends a single request (directory list, value retrieval, value set, device presence) and receives a single response. The directory request is a little different. There is a single request, and multiple responses (1 per entry). The protocol is stateless. There is a "still alive" message if the response will take longer than 1 second. Protocol functions : Communication between programs and owserver -- extending the 1-wire system across the network and allowing multiple programs/clients to safely use the same 1-wire devices. Broadcast or Multicast used ? no How and what for Broadcast or Multicast is used (if used): owserver has mdns support with a protocol "_owserver._tcp" allocated, but that function is not part of this request. It is only for owserver discovery. This proposed "well known port" would not respond to either broadcast or multicast requests, it is a pure tcp client server unicast system, used for data transfer. Description : The OWFS (One-Wire File System) is an open source suite of programs that allow easy access to Dallas Semiconductor's 1-wire chips. The home page is www.owfs.org and the code is found at owfs.sourceforge.net The OWFS suite includes programs that talk to the 1-wire bus (more on that in the next paragraph), and programs that act as intermediaries or provide other modes of access to the bus (ftp servers, web servers, virtual file systems, shell programs, language bindings for perl, C, php, python, tcl). We are asking for a port for communication between the members of the OWFS suite. More on 1-wire itself: These chips are used in security, monitoring, control and automation. The 1-wire system is interesting because the devices are very inexpensive, uniquely numbered and indivually addressable, even with the simple wire scheme (a combined data/power line and a ground). OWFS makes the entire 1-wire system accessible using a filesystem metaphore: devices are directories, and properties (like temperature, voltage, memory) are files. The OWFS suite extends the funtion and span of the 1-wire bus by using a tcp server (owserver) that can either talk to a physical 1-wire bus, or to other owservers. Programs can connect to owserver and thus access the full function of 1-wire over the network. The actual physical aspects are abstracted (for instance, 1-wire adapters are USB, serial, i2c, tcp, in multiple flavors and vendors). The suite operates on multiple platforms (linux, osx, freebsd, windows). In short, we propose to allocate a well-known port number to owserver for data transfer between elements of the OWFS suite. We expect that a known port will make configuration easier. Name of the port : One-Wire Filesystem Server Short name of the port : owserver |
From: Paul A. <pau...@gm...> - 2007-01-23 01:16:29
|
Great news, 4304 is out default port. I'll modify the programs and examples to use it. In general, if no port is specified, 4304 will be assumed. Paul Alfille ---------- Forwarded message ---------- From: Pearl Liang via RT <ian...@ia...> Date: Jan 21, 2007 8:29 PM Subject: [IANA #50010] Application for port-number: owserver (Assigned-4304) To: pau...@gm... Dear Paul Alfille: We have assigned the following user port number(s) with you as the point of contact: owserver 4304/tcp One-Wire Filesystem Server owserver 4304/udp One-Wire Filesystem Server # Paul Alfille <pau...@gm...> January 2007 See: http://www.iana.org/assignments/port-numbers Please notify IANA if there is any change in contact information by completing the following template: http://www.iana.org/cgi-bin/mod_portno.pl This ticket [IANA #50010] is considered resolved. Best regards, Pearl Liang IANA |
From: Jan K. <jj...@gm...> - 2007-01-24 11:43:17
|
Am Dienstag, 23. Januar 2007 02:16 schrieb Paul Alfille: > Great news, 4304 is out default port. I'll modify the programs and exampl= es > to use it. In general, if no port is specified, 4304 will be assumed. > That's indeed great news. owserver has a default port now and will be put=20 into /etc/services files soon... ^__^; I think, owserver should be modified that way the port option is checked=20 first, then it looks for an owserver entry in /etc/services, and if that=20 entry is not present it uses the hardcoded port number 4304. Kind regards Jan =2D-=20 Moore's Gesetz: Alle 18 Monate halbiert sich die Gr=C3=B6=C3=9Fe der Hardwa= re, und ihre Geschwindigkeit verdoppelt sich. Gates' Gesetz: Alle 18 Monate verdoppelt sich die Gr=C3=B6=C3=9Fe der Softw= are, und ihre Geschwindigkeit halbiert sich. |
From: Gregg L. <gre...@gm...> - 2007-01-23 01:26:48
|
On 1/22/07, Paul Alfille <pau...@gm...> wrote: > Great news, 4304 is out default port. I'll modify the programs and examples > to use it. In general, if no port is specified, 4304 will be assumed. > > Paul Alfille > > ---------- Forwarded message ---------- > From: Pearl Liang via RT <ian...@ia...> > Date: Jan 21, 2007 8:29 PM > Subject: [IANA #50010] Application for port-number: owserver (Assigned-4304) > To: pau...@gm... > > Dear Paul Alfille: > > We have assigned the following user port number(s) with you as the point of > contact: > > owserver 4304/tcp One-Wire Filesystem Server > owserver 4304/udp One-Wire Filesystem Server > # Paul Alfille <pau...@gm...> January > 2007 > > See: http://www.iana.org/assignments/port-numbers > > Please notify IANA if there is any change in contact information by > completing the following template: > > http://www.iana.org/cgi-bin/mod_portno.pl > > This ticket [IANA #50010] is considered resolved. > > Best regards, > > Pearl Liang > IANA > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > Owfs-developers mailing list > Owf...@li... > https://lists.sourceforge.net/lists/listinfo/owfs-developers > > > Hello! Good news indeed. However Paul wasn't the software originally written to allow for any port to be selected? For example the help lines show examples at 3001 or 3008. I always choose both. But yes go ahead and modify the appropriate code. -- Gregg C Levine gre...@gm... "This signature was once found posting rude messages in English in the Moscow subway." |
From: Paul A. <pau...@gm...> - 2007-01-23 01:47:49
|
On 1/22/07, Gregg Levine <gre...@gm...> wrote: > > On 1/22/07, Paul Alfille <pau...@gm...> wrote: > > Great news, 4304 is out default port. I'll modify the programs and > examples > > to use it. In general, if no port is specified, 4304 will be assumed. > Good news indeed. > However Paul wasn't the software originally written to allow for any > port to be selected? For example the help lines show examples at 3001 > or 3008. I always choose both. But yes go ahead and modify the > appropriate code. > The port is assignable, as always. This just aids configuration in the simpler cases (just like assuming a web server at port 80 makes life easier). Paul Alfille |