<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2627" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=631553616-13062005><FONT face=Arial
color=#0000ff size=2>Jane,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=631553616-13062005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=631553616-13062005><FONT face=Arial
color=#0000ff size=2>Did you put those in the public or private area? All
I can see in the public document library is a folder with 'Meetings [sic]
Info"</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=631553616-13062005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN
class=631553616-13062005> <FONT
face=Arial color=#0000ff size=2>--keith</FONT></SPAN></DIV><BR>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sois-tcons-bounces@mailman.ccsds.org
[mailto:sois-tcons-bounces@mailman.ccsds.org] <B>On Behalf Of </B>Jane K.
Marquart<BR><B>Sent:</B> Monday, June 13, 2005 12:04 PM<BR><B>To:</B> Richard
Schnurr; Scott,Keith L.; sois-tcons@mailman.ccsds.org<BR><B>Subject:</B> RE:
[Sois-tcons] White paper contribution.<BR></FONT><BR></DIV>
<DIV></DIV>All,<BR><BR>I uploaded the 2 documents to <BR><A
href="http://public.ccsds.org/sites/cwe/sois-tcons/Documents.aspx"
eudora="autourl">http://public.ccsds.org/sites/cwe/sois-tcons/Documents.aspx</A><BR><BR>I
couldn't create a new folder. Kept getting errors. I also put this
e-mail on the discussion board so as not to lose it. Let's try to keep
all correspondence there from now on.<BR>Thanks!<BR><BR><BR><BR>At 05:38 PM
6/10/2005 -0400, Richard Schnurr wrote:<BR>
<BLOCKQUOTE cite="" type="cite">Hi Keith,<BR> <BR>In some ways I am the
scribe but I will try to answer anyway.<BR><BR>IP/NP is the current
networking layer of choice for SOIS. In some ways IP/NP could be given
to SIS since all the QOS stuff other than the QOS tagging is below. This
would simplify SOIS's life since we would simply hand this function over to
SIS.<BR><BR>The IP/NP layer does perform the routing between OBL.<BR><BR>The
span of an OBL is defined by the user. IE if multiple networks of the
same type are available the bridging of those networks would be
implementation specific. This is necessary from a fault tollerance
perspective.<BR><BR>Remember some of the Bus/Lan are networks onto
themselves (for example) JWST is using a SpaceWire network to move data
without IP.<BR><BR>The TCONS-API is better than sockets from my perspective
since it captures the close interaction between network messages and
software actions in its call back interface however Jane is the one to
discuss this and Scott's white paper on the messaging service must be
interpreted and implemented.<BR><BR>On the other hand the SOIS API is
non-normative since hardware devices would not implement.<BR><BR>Yes, TCONS
currently makes no claims to support QOS over multiple OBL's (heterogenious
or not - IE two separately scheduled SpaceWire networks would not support
end to end QOS). Although doing so would not be hard if both OBL's
were in the same schedule domain.<BR><BR>Steve, put the copyright notice on
the document during the shutdown period. He will have to comment on
why.<BR><BR>As far as I am concerned the document is copyright of the CCSDS
since all of this is a group derived work. Otherwise it would be ITAR
:).<BR><BR>The US government has the same write to copyright as anyone
else. The current court rulings indicate that US copyright occurs when
pen is placed to paper with or without registration. I am less
familiar with the laws of Greece. Lets not get into this legal
stuff.<BR><BR>If my clarifications lead to needed changes let me
know.<BR><BR>Cheers,<BR>Rick<BR><BR>At 04:22 PM 6/10/2005, Scott,Keith L.
wrote:<BR>
<BLOCKQUOTE cite="" type="cite"><FONT face=arial color=#0000ff size=2>So
if I understand correctly, the architectural elements say that:</FONT>
<UL><FONT face=arial color=#0000ff size=2>TCONS (in conjunction with/via
OBL) provides QoS over individual subnets, and that for traffic that
spans heterogeneous subnets, IP is the networking layer? [Architectural
Elements (2,3)] Application interfaces to 'TCONS' are via sockets and/or
a TCONS-specific API. TCONS makes no claims to support QoS over paths
containing multiple OBLs</FONT> </UL><FONT face=arial color=#0000ff
size=2>The inclusion of TCP/IP in the green SOIS box on slide 1 is sort of
odd (since IP/TCP would normally be a SIS thing). But taking as
given that TCONS is a world unto itself in order to provide time-critical
services, and needs a network layer to span heterogeneous subnets, it sort
of makes sense.</FONT><BR> <BR><FONT face=arial color=#0000ff
size=2>BTW: I believe that works by the U.S. Gov't are not eligible for
copyright protection, and I'm not sure what legal standing 'The TCONS
Working Group' has wrt copyright. I'd be sort of interested if you
know more about this.</FONT><BR> <BR><FONT face=arial color=#0000ff
size=2> --keith</FONT>
<HR>
<DL><FONT face=tahoma size=2>
<DD>From: sois-tcons-bounces@mailman.ccsds.org [<A
href="mailto:sois-tcons-bounces@mailman.ccsds.org"
eudora="autourl">mailto:sois-tcons-bounces@mailman.ccsds.org</A>] On
Behalf Of Richard Schnurr
<DD>Sent: Friday, June 10, 2005 11:38 AM
<DD>To: sois-tcons@mailman.ccsds.org
<DD>Subject: [Sois-tcons] White paper contribution.</FONT>
<DD>Hi all,
<DD>OK, based on the last call I drafted the beginnings of a white
paper.<BR><BR>
<DD>I kept it short - hopefully you can all read the whole
thing.<BR><BR>
<DD>If we all agree to this structure and the descriptions I think we
can restart the books.<BR><BR>
<DD>BTW, it would not hurt my feelings if we deleted the OBL service
interface and simply defined a Intra-network service interface (This is
what I did in this white paper). Not clear that the OBL interface
is usable since on board a spacecraft we are time critical and OBL is a
on demand type of service not coordinated with anything else.<BR><BR>
<DD>Also, the OBL service interface seems to get in the way more than it
helps. For example some OBL's support protocol multiplexing.
For those that do the Intra-Net should map directly. We already
have IP addresses. It would seem that mapping directly from IP
addresses to OBL addresses is what is usually done and makes sense.
<BR><BR>
<DD>For these reasons I am proposing that the OBL service interface be
deleted and replaced with a private interface to the Intra-networking
service.<BR><BR>
<DD>Please read my section on address mapping. It makes sense to
me I think it can be implemented and it is in line with existing IP
implementations.<BR><BR>
<DD>Steve, I modified the picture to remove the OBL service interface
and to move address resolution inside and between the Intra-networking
service and OBL. (In case you cannot open the figure again).<BR><BR>
<DD>If we stick to what is written here I think I can actually see a way
to implement this consistently across various bus. This is the
first time I have had such clarity and I am going on vacation before any
of you spoil it.<BR><BR>
<DD>I am on vacation next week. So this and the modified diagrams
are my contribution to the white paper.<BR><BR>
<DD>Rick<BR><BR>
<DD>PS I did not use the message board because I do not have my
password. Someone can post this if they like. If you reply
to this message Please: do not reply inline - add your response to
the top. After one pass of the in line comments I cannot follow
and on a mailing list like this the likely hood that I will get many
reply's is almost surely one.
<DD>As always correct my thinking as
required.<BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR></DD></DL></BLOCKQUOTE>
<DL></DL>Richard G Schnurr Jr<BR>Chief Architect<BR>Electrical Systems
Center<BR>Applied Engineering and Technology Directorate<BR>NASA GSFC Code
560.0<BR>Greenbelt MD 20771<BR><BR>(301)-286-1852
<BR>_______________________________________________<BR>Sois-tcons mailing
list<BR>Sois-tcons@mailman.ccsds.org<BR><A
href="http://mailman.ccsds.org/mailman/listinfo/sois-tcons"
eudora="autourl">http://mailman.ccsds.org/mailman/listinfo/sois-tcons</A></BLOCKQUOTE><BR>Jane
</BLOCKQUOTE></BODY></HTML>