From greg.j.kazz at jpl.nasa.gov  Wed Aug  7 16:21:51 2013
From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (313B))
Date: Wed, 7 Aug 2013 16:21:51 +0000
Subject: [Sls-slp] FW: PICS annex for proximity-1 dll
In-Reply-To: <afa0ddf7-fc5b-4650-ab1a-8d11f4671ca4@AIAASWMLEXCH010.hq.ad.aiaa.org>
Message-ID: <CE27C08D.2AF08%gkazz@jpl.nasa.gov>

Dear SLP WG,

Attached is the Prox-1 Data Link Layer PICS Proforma annex that Tom
Gannett has formatted for us.
Please review it and make sure that it is complete (we are not missing any
parameters) and that the values and designations (Optional vs Mandatory)
is appropriate. Note that we have previously decided that Half-Duplex
operations are Optional; However the SET DUPLEX parameter is mandatory
since the DULEX variable must be set. I expect some discussion about
whether some of these parameters should be Mandatory or Optional. I would
like us to be able to resolve these issues and provide me with an updated
PICs by Aug. 22.

Please let me know if you have any questions.

Best regards,

Greg
CCSDS SLS-SLP WG Chairman
------------------------------------------------------
Greg Kazz
EEISE Group Supervisor
Systems Engineering Section (Section 313)
Jet Propulsion Laboratory
4800 Oak Grove Drive, Pasadena  CA 91109
MS 301-490
(818) 393-6529 (office)

------------------------------------------------------





On 8/7/13 6:51 AM, "Thomas Gannett" <tomg at aiaa.org> wrote:

>Greg:
>
>The attached PICS annex reflects your changes. I don't really know
>who makes up the review team, so I think you should distribute it. If
>you know of individuals who were involved in the protocol testing it
>would be helpful to include them.
>
>You might also communicate the following PICS general principles to
>the review team:
>
>- A PICS proforma is supposed to be limited to static conformance
>requirements, so any items referencing dynamic protocol behavior
>should be omitted.
>
>- A PICS proforma is supposed to list ALL optional capabilities but
>only MAJOR mandatory capabilities. Reviewers should determine whether
>lists of all-mandatory capabilities subordinate to a higher-level
>mandatory capability can be reduced to show simply the higher-level
>capability.
>
>- Items that reference implementation-internal behavior that does not
>affect interoperability should not be included.
>
>I'm still cross checking to make sure all the changes have been made
>to the specification itself.  I'll send it for WG signoff when I'm done.
>
>Tom
>
>
>
>At 08:19 PM 8/6/2013, Kazz, Greg J (313B) wrote:
>>Hi Tom,
>>
>>I went through the proposed PICS for the Data Link Layer and made some
>>changes some of which we spoke about over the phone and some new ones.
>>Please use this content to send out to the review team. No doubt we will
>>quibble over some Os and Ms, but for the most part, I feel pretty secure
>>about them.
>>
>>Also note:
>>
>>1. Like we talked about, add a note about DLL = Data Link Layer in the
>>item mneumonic
>>
>>2. I found an error in the Prox-1 spec. It is in the MIB annex (now annex
>>C ?). Remote_PCID is Mandatory (it says Optional in the spec, which needs
>>to be corrected.)
>>
>>Thanks!
>>
>>Greg
>>------------------------------------------------------
>>Greg Kazz
>>EEISE Group Supervisor
>>Systems Engineering Section (Section 313)
>>Jet Propulsion Laboratory
>>4800 Oak Grove Drive, Pasadena  CA 91109
>>MS 301-490
>>(818) 393-6529 (office)
>>
>>------------------------------------------------------
>>
>>
>>
>>
>>
>>On 7/31/13 12:31 PM, "Thomas Gannett" <tomg at aiaa.org> wrote:
>>
>> >
>> >
>> >Thomas Gannett
>> >+1 443 472 0805
>>
>>
>
>Thomas Gannett
>+1 443 472 0805 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Proximity-1 DLL PICS annex (working).doc
Type: application/msword
Size: 402432 bytes
Desc: Proximity-1 DLL PICS annex (working).doc
URL: <http://mailman.ccsds.org/pipermail/sls-slp/attachments/20130807/d7d34c50/attachment.doc>

From greg.j.kazz at jpl.nasa.gov  Wed Aug  7 16:23:22 2013
From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (313B))
Date: Wed, 7 Aug 2013 16:23:22 +0000
Subject: [Sls-slp] FW: PICS annex for proximity-1 dll - definitions
In-Reply-To: <20979e5e-0eb0-4d79-8fde-54b52833fbbb@AIAASWMLEXCH010.hq.ad.aiaa.org>
Message-ID: <CE27C241.2AF17%gkazz@jpl.nasa.gov>

Dear SLP WG,

As a follow on to my previous email, please consider these definitions for Mandatory, Optional, Conditional

Thanks!

Greg
------------------------------------------------------
Greg Kazz
EEISE Group Supervisor
Systems Engineering Section (Section 313)
Jet Propulsion Laboratory
4800 Oak Grove Drive, Pasadena  CA 91109
MS 301-490
(818) 393-6529 (office)
------------------------------------------------------

From: Thomas Gannett <tomg at aiaa.org<mailto:tomg at aiaa.org>>
Date: Wednesday, August 7, 2013 8:05 AM
To: "Kazz, Greg J (313B)" <greg.j.kazz at jpl.nasa.gov<mailto:greg.j.kazz at jpl.nasa.gov>>
Subject: Re: PICS annex for proximity-1 dll

Greg:

I'm also working on some generic definitions that you may want to share with the review team (so "M" and "O" mean the same thing to everyone):

optional. Not necessary for interoperability.

Optional capabilities can be excluded from an implementation (and made unavailable to users) without affecting the essential operation of the implementation.

Implementation options should not be confused with user options; i.e., there may be any number of features which a user can elect not to use but which need to be available in an implementation.

Also, whether a capability is optional may depend on whether the implementation is sending, receiving, or acting as a relay. A capability that a transmitter can do without might nevertheless be required at a receiver to accommodate transmitters that implement the capability.

mandatory. Required for interoperability.

Mandatory capabilities are all capabilities that need to be available for use for normal operation of an implementation, regardless of whether a user can elect not to use them.

conditional. Mandatory or optional depending on specified conditions.




At 09:51 AM 8/7/2013, Thomas Gannett wrote:
Greg:

The attached PICS annex reflects your changes. I don't really know who makes up the review team, so I think you should distribute it. If you know of individuals who were involved in the protocol testing it would be helpful to include them.

You might also communicate the following PICS general principles to the review team:

- A PICS proforma is supposed to be limited to static conformance requirements, so any items referencing dynamic protocol behavior should be omitted.

- A PICS proforma is supposed to list ALL optional capabilities but only MAJOR mandatory capabilities. Reviewers should determine whether lists of all-mandatory capabilities subordinate to a higher-level mandatory capability can be reduced to show simply the higher-level capability.

- Items that reference implementation-internal behavior that does not affect interoperability should not be included.

I'm still cross checking to make sure all the changes have been made to the specification itself.  I'll send it for WG signoff when I'm done.

Tom



At 08:19 PM 8/6/2013, Kazz, Greg J (313B) wrote:
Hi Tom,

I went through the proposed PICS for the Data Link Layer and made some
changes some of which we spoke about over the phone and some new ones.
Please use this content to send out to the review team. No doubt we will
quibble over some Os and Ms, but for the most part, I feel pretty secure
about them.

Also note:

1. Like we talked about, add a note about DLL = Data Link Layer in the
item mneumonic

2. I found an error in the Prox-1 spec. It is in the MIB annex (now annex
C ?). Remote_PCID is Mandatory (it says Optional in the spec, which needs
to be corrected.)

Thanks!

Greg
------------------------------------------------------
Greg Kazz
EEISE Group Supervisor
Systems Engineering Section (Section 313)
Jet Propulsion Laboratory
4800 Oak Grove Drive, Pasadena  CA 91109
MS 301-490
(818) 393-6529 (office)

------------------------------------------------------





On 7/31/13 12:31 PM, "Thomas Gannett" <tomg at aiaa.org<mailto:tomg at aiaa.org>> wrote:

>
>
>Thomas Gannett
>+1 443 472 0805

Thomas Gannett
+1 443 472 0805

Thomas Gannett
+1 443 472 0805
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/sls-slp/attachments/20130807/194492bc/attachment.html>

From greg.j.kazz at jpl.nasa.gov  Mon Aug 19 22:13:39 2013
From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (313B))
Date: Mon, 19 Aug 2013 22:13:39 +0000
Subject: [Sls-slp] Proximity-1 Data Link Specification for final SLP WG
	review
Message-ID: <CE37E6A0.2B33E%gkazz@jpl.nasa.gov>

Dear SLP WG members,

Tom Gannett has provided us now with a pre-approval version for the CESG of the Proximity-1 Space Data Link Protocol.

Please review the attached documents and send me and Tom any comments you have (redlines of the clean version would work, if you have the bandwidth to send a 20 Megabyte file !) to me and Tom by Sept. 13.

There are two files in the CWE directory below. One is a red-lined version so that you can see the changes made and also a clean version.

http://tinyurl.com/kzjz38z

Best regards,

Greg
------------------------------------------------------
Greg Kazz
EEISE Group Supervisor
Systems Engineering Section (Section 313)
Jet Propulsion Laboratory
4800 Oak Grove Drive, Pasadena  CA 91109
MS 301-490
(818) 393-6529 (office)
------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/sls-slp/attachments/20130819/67be3c75/attachment.html>

From greg.j.kazz at jpl.nasa.gov  Tue Aug 20 16:52:31 2013
From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (313B))
Date: Tue, 20 Aug 2013 16:52:31 +0000
Subject: [Sls-slp] Next Generation Space Data Link Protocol for Review
Message-ID: <CE38ECD9.2B386%gkazz@jpl.nasa.gov>

Dear SLP WG,

Please go to the URL below to find the latest version of the Next Generation Space Data Link Protocol. This is the protocol with the common format and services that we intend on discussing at the Fall meeting in San Antonio. I would appreciate it, if you would send me your comments regarding the protocol ahead of the meeting, but at least by Sept. 30.

http://tinyurl.com/lo29syj


Best regards,

Greg
------------------------------------------------------
Greg Kazz
EEISE Group Supervisor
Systems Engineering Section (Section 313)
Jet Propulsion Laboratory
4800 Oak Grove Drive, Pasadena  CA 91109
MS 301-490
(818) 393-6529 (office)
------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/sls-slp/attachments/20130820/d15c21bf/attachment.html>