[TechEditor] FW: 211.0

Stepanova, Natalya (GSFC-580.0)[MCSG Technologies, Inc] natalya.stepanova at nasa.gov
Fri Nov 7 16:45:01 EST 2025


Where we left things off with Data Link Layer

[cid94090*image005.jpg at 01DB7974.AFFCF740]

Natalya Stepanova
Technical Writer
Codes 581, 583, 589
Contractor, MCSG Technologies
NASA Goddard Space Flight Center
Building 23 | Room TBD
M: 361.945.5515
natalya.stepanova at nasa.gov<mailto:natalya.stepanova at nasa.gov>
talyana at gmail.com


From: "Kazz, Greg (US 312B)" <greg.j.kazz at jpl.nasa.gov>
Date: Monday, September 29, 2025 at 4:24 PM
To: "Stepanova, Natalya (GSFC-580.0)[MCSG Technologies, Inc]" <natalya.stepanova at nasa.gov>
Subject: Re: 211.0

I’m good with it. It’s good for agency review now.

thanks,
Greg

From: Stepanova, Natalya (GSFC-580.0)[MCSG Technologies, Inc] <natalya.stepanova at nasa.gov>
Date: Monday, September 29, 2025 at 10:15 AM
To: Kazz, Greg (US 312B) <greg.j.kazz at jpl.nasa.gov>
Subject: Re: 211.0
But you didn’t like my rewrite? I think I actually preserved most of the information as is, but made it slightly more readable by breaking different scenarios into bullets and reducing the wordiness a bit and make more concise, active, and direct (“it may be required that security services be applied”, for example, is full of passive voice constructions that are not necessary).

[cid:image003.jpg at 01DC5005.D9409860]

Natalya Stepanova
Technical Writer
Codes 581, 583, 589
Contractor, MCSG Technologies
NASA Goddard Space Flight Center
Building 23 | Room TBD
M: 361.945.5515
natalya.stepanova at nasa.gov<mailto:natalya.stepanova at nasa.gov>
talyana at gmail.com


From: "Kazz, Greg (US 312B)" <greg.j.kazz at jpl.nasa.gov>
Date: Monday, September 29, 2025 at 12:30 PM
To: "Stepanova, Natalya (GSFC-580.0)[MCSG Technologies, Inc]" <natalya.stepanova at nasa.gov>
Subject: Re: 211.0

In re-reading B1.1 and B1.2 below, I overstated the “I have no idea part”. It has been sometime since I last saw these sections. Most likely, they were simply added in the review process.  They are not unreasonable. And I am glad they both point out that they are beyond the scope of this specific document. So really I don’t have a problem with either of those sections (B1.1, B1.2). They are providing a general warning to the user about IP datagram traffic and security concerns.

I believe at this point we can go ahead and move this document forward for agency review.

thanks,
Greg

From: Stepanova, Natalya (GSFC-580.0)[MCSG Technologies, Inc] <natalya.stepanova at nasa.gov>
Date: Monday, September 29, 2025 at 9:24 AM
To: Kazz, Greg (US 312B) <greg.j.kazz at jpl.nasa.gov>
Subject: Re: 211.0
Touching base on the other document, too: I think we pretty much have no issues with 211.0, I agree with your point that renumbering all the references like the style guide prescribes is a lot of effort that doesn’t really translate into better readability, so I’m going to let it go.

The only thing I am not sure what to do with is Annex B. You wrote below that you would rather go back to what we originally had in B1.1 and B1.2, but then in the document itself you indicated that “ I have no idea where this red lined information came from in B1.1 and B1.2 in particular with a focus on IP datagrams. Not from me and not from the SLP WG. We have a CCSDS Blue Book called, IP over CCSDS, 702.1. It is under the cognizance of the SIS Area. Seems like B1.1 and B1.2 belong there.”



The red lined information is “what we originally had” in the document I received, I merely restructured it into bullets with minor rewriting. Do you mean originally as in previous versions? Not sure if I should return to the version below, return to some even earlier version, or remove them altogether, perhaps? Once I get clear guidance on that, I think we can finalize the document.



[cid:image005.png at 01DC5005.D9409860]


[cid:image006.jpg at 01DC5005.D9409860]

Natalya Stepanova
Technical Writer
Codes 581, 583, 589
Contractor, MCSG Technologies
NASA Goddard Space Flight Center
Building 23 | Room TBD
M: 361.945.5515
natalya.stepanova at nasa.gov<mailto:natalya.stepanova at nasa.gov>
talyana at gmail.com


From: "Kazz, Greg (US 312B)" <greg.j.kazz at jpl.nasa.gov>
Date: Friday, September 26, 2025 at 12:37 PM
To: "Stepanova, Natalya (GSFC-580.0)[MCSG Technologies, Inc]" <natalya.stepanova at nasa.gov>
Subject: Re: 211.0

Hi Natalya,

The security annex is no longer correct with the red lines as indicated in my return comments. I would rather go back to what we originally had in B1.1 and B1.2. The other changes are OK.
Anyway, I answered all your comments with the return email feature.
I am glad that this document should progress much faster than the others.

Also, so far, I heard positively back from Eric Pitts at MSFC on the issue 5  AOS book. I will wait until Monday Sept 29 to see if I get any comments and then we will be able to do any last edits on it, if necessary.

thanks,
Greg

From: Stepanova, Natalya (GSFC-580.0)[MCSG Technologies, Inc] <natalya.stepanova at nasa.gov>
Date: Friday, September 26, 2025 at 6:37 AM
To: Kazz, Greg (US 312B) <greg.j.kazz at jpl.nasa.gov>
Subject: Re: 211.0
Yes, the book looked exceptionally good, I was wondering if Tom had worked on it or if it just changed very little from the previous version. I made a few very inconsequential changes, like acronyms being spelled out on the second use, when it should be on the first, cleaning up the acronym list, etc.
The only substantive error I caught was when we list the sublayers, we say there are 5 of them, but the list has only 4 (I left a comment).
Besides that, I suggested a few rewrites in the security annex B – is that new(er)? And even those changes were more about formatting and redundancy.
Annex D also has a style that is too conversational, but it sounds like we don’t fuss over Annexes as much as over the body of the text, however, I made some suggestions if we do want to make the tone more formal.
The references also need to be updated, but I always hesitate to update everything to the latest version by default, because some of those may not have been out when the book was written, so I wanted to get your “go ahead” before I up and updated them all.
Anyway, here are my comments and edits for your review and approval.
Sincerely,

[cid:image008.jpg at 01DC5005.D9409860]

Natalya Stepanova
Technical Writer
Codes 581, 583, 589
Contractor, MCSG Technologies
NASA Goddard Space Flight Center
Building 23 | Room TBD
M: 361.945.5515
natalya.stepanova at nasa.gov<mailto:natalya.stepanova at nasa.gov>
talyana at gmail.com


From: "Kazz, Greg (US 312B)" <greg.j.kazz at jpl.nasa.gov>
Date: Thursday, September 25, 2025 at 5:22 PM
To: "Stepanova, Natalya (GSFC-580.0)[MCSG Technologies, Inc]" <natalya.stepanova at nasa.gov>
Subject: Re: 211.0

I believe it will be a pink book, because it is an existing blue book, which had parts removed from it to create the Generic Session Control book (235.1).
Tom Gannett did the cutting and extractions.
I am the book captain for it and also 235.1

thanks,
Greg

From: Stepanova, Natalya (GSFC-580.0)[MCSG Technologies, Inc] <natalya.stepanova at nasa.gov>
Date: Thursday, September 25, 2025 at 1:47 PM
To: Kazz, Greg (US 312B) <greg.j.kazz at jpl.nasa.gov>
Subject: 211.0
While I have you, I finished reviewing the 211x0p60 book and have a few questions/suggestions for the authors to look over. Were you the book captain for this book as well or who should I contact for that? And it’s going to be a Red book?

[cid94090*image005.jpg at 01DB7974.AFFCF740]

Natalya Stepanova
Technical Writer
Codes 581, 583, 589
Contractor, MCSG Technologies
NASA Goddard Space Flight Center
Building 23 | Room TBD
M: 361.945.5515
natalya.stepanova at nasa.gov<mailto:natalya.stepanova at nasa.gov>
talyana at gmail.com


From: "Kazz, Greg (US 312B)" <greg.j.kazz at jpl.nasa.gov>
Date: Thursday, June 12, 2025 at 1:55 PM
To: "Kazz, Greg (US 312B) via SLS-SLP" <sls-slp at mailman.ccsds.org>, "Rodriguez, Shannon (GSFC-5670)" <shannon.rodriguez-1 at nasa.gov>, "Stepanova, Natalya (GSFC-580.0)[MCSG Technologies, Inc]" <natalya.stepanova at nasa.gov>, C&S Working Group <sls-cc at mailman.ccsds.org>, "sls-rfm at mailman.ccsds.org" <sls-rfm at mailman.ccsds.org>
Subject: Updated 235.1 Generic Session Control White Book for RED-1

Dear SLP WG,

Attached please find the updated version agreed to at the joint SLP, C&S, and RFM meeting yesterday (June 11, 2025) at the Spring CCSDS meeting at APL. (235.1)

Also attached is the slimmed down Prox-1 SDLP White book, upon which consensus was achieved in the SLP WG meeting on Monday, June 10, 2025 to move it to RED-1 as well. (211.0)

The secretariat should take these documents attached and use them to produce the associated RED-1 versions.

I will speak to this topic at the SLS plenary tomorrow AM.

Regards,
Greg
SLP WG Chair
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/techeditor/attachments/20251107/234a7268/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 19520 bytes
Desc: image001.jpg
URL: <http://mailman.ccsds.org/pipermail/techeditor/attachments/20251107/234a7268/attachment-0005.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 363 bytes
Desc: image002.png
URL: <http://mailman.ccsds.org/pipermail/techeditor/attachments/20251107/234a7268/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 19521 bytes
Desc: image003.jpg
URL: <http://mailman.ccsds.org/pipermail/techeditor/attachments/20251107/234a7268/attachment-0006.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 364 bytes
Desc: image004.png
URL: <http://mailman.ccsds.org/pipermail/techeditor/attachments/20251107/234a7268/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 198706 bytes
Desc: image005.png
URL: <http://mailman.ccsds.org/pipermail/techeditor/attachments/20251107/234a7268/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.jpg
Type: image/jpeg
Size: 19522 bytes
Desc: image006.jpg
URL: <http://mailman.ccsds.org/pipermail/techeditor/attachments/20251107/234a7268/attachment-0007.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 365 bytes
Desc: image007.png
URL: <http://mailman.ccsds.org/pipermail/techeditor/attachments/20251107/234a7268/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.jpg
Type: image/jpeg
Size: 19523 bytes
Desc: image008.jpg
URL: <http://mailman.ccsds.org/pipermail/techeditor/attachments/20251107/234a7268/attachment-0008.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.png
Type: image/png
Size: 366 bytes
Desc: image009.png
URL: <http://mailman.ccsds.org/pipermail/techeditor/attachments/20251107/234a7268/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.jpg
Type: image/jpeg
Size: 19524 bytes
Desc: image010.jpg
URL: <http://mailman.ccsds.org/pipermail/techeditor/attachments/20251107/234a7268/attachment-0009.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image011.png
Type: image/png
Size: 367 bytes
Desc: image011.png
URL: <http://mailman.ccsds.org/pipermail/techeditor/attachments/20251107/234a7268/attachment-0011.png>


More information about the TechEditor mailing list